Slice Architecture
Protects the app from structural decay — the gradual loss of boundaries that makes every change risky and every AI prompt unpredictable.
What It Protects
When code is well-structured, a change to the billing flow affects only the billing code. When structure breaks down, a change to billing can break authentication, admin access, or features that seem completely unrelated.
The protection is structural: explicit boundaries between features, bounded complexity per unit, and clear dependency direction. When these rules hold, AI tools can work safely within defined scope.
What Typically Breaks
Coupling grows silently
AI tools import whatever works. They don't track dependency direction or respect feature boundaries. Over time, every part of the codebase depends on every other part.
Files grow beyond AI context
After many prompts, individual files grow to hundreds or thousands of lines. At that point, AI tools lose context — they contradict previous logic and introduce regressions. This is often the point where founders report hitting the "AI wall."
Business logic leaks into infrastructure
Without explicit boundaries, business logic migrates into page files, shared utilities, and component hierarchies. Testing in isolation becomes impractical.
Phase 1 Checks
A slice is ASA's fundamental unit: a self-contained vertical feature with hard boundaries. Slices are designed not to depend on other slices.
Architecture Checks (6)
Structure Checks (2)
These verify structural enforcement readiness — prerequisites for continuous architecture enforcement.
Relationship to AI Chaos Index
AI Chaos Index measures structural risk. Higher score = more structural chaos.
| Score | Risk Band | Meaning |
|---|---|---|
| 0–20 | Minimal | Architecture is clean, regressions unlikely |
| 21–40 | Low | Minor issues, low risk |
| 41–60 | Moderate | Structural problems present, medium regression risk |
| 61–80 | High | AI-generated changes likely cause regressions |
| 81–100 | Critical | Architecture is broken, every change is risky |
AI Chaos Index is a point-in-time structural assessment. It is not a certification or guarantee of maintainability.
What This Layer Does Not Cover
- Authentication, billing, or admin safety (Production Foundation)
- Business flow correctness (Business Logic Protection)
- Runtime performance, memory, or availability
- General code style, formatting, or non-structural quality concerns