ASA — Atomic Slice Architecture
An architecture standard for AI-generated software that stays maintainable. ASA defines how code should be structured when AI generates it — slice isolation, boundary enforcement, and deterministic regeneration.
No vendor. No license. No cost.
Four Core Principles
1. Determinism
Same input, same output, always. Every ASA operation produces identical results — no randomness, no heuristics, no AI inference in the core pipeline.
2. Zero Magic
Explicit over implicit. No hidden behavior, no automatic assumptions, no context-dependent defaults.
3. Boundary Enforcement
Slices are isolated units. They cannot import from other slices. Cross-domain dependencies are forbidden and caught by the linter.
4. Marker-Based Preservation
When a spec changes, the slice regenerates predictably. Custom code between markers is preserved. Structure updates, logic survives.
Documentation
- Manifesto — why ASA exists
- Core Principles — foundational rules
- How It Works — technical deep-dive
- Problems Solved — what ASA addresses
Solutions
Resources
Start Here
ASA is designed for incremental adoption. You don't migrate — you start using it for new features.
- Read the Manifesto (15 min)
- Review your codebase against Core Principles (1 hour)
- Implement one slice using How ASA Works