This repository contains the canonical Vertical Slice Architecture guidelines used by this workspace. The authoritative specification lives in VSA.md, which defines the solo-agent operating model, slice boundaries, shared-kernel constraints, data sovereignty rules, observability requirements, and refactoring triggers.
Vertical Slice Architecture organizes code around business capabilities rather than technical layers. The goal is to keep each slice self-contained so that ownership, change isolation, and boundary enforcement stay explicit.
- Slice terminology and responsibility boundaries
- Mandatory slice anatomy: entry point, input model, validator, handler, and
CONTEXT.md - File naming rules for slices, shared kernel concepts, and tests
- Validation, error handling, and result-flow expectations
- Data ownership, cross-slice read/write boundaries, and integration events
- Structured observability and error-envelope requirements
- Refactoring triggers and hard gates for autonomous execution
- Context-scaling guidance for small, medium, and large slice counts
- VSA.md: Canonical guidelines and rule set
- Archive/: Historical XML and Markdown exports kept for reference
- LICENSE: GNU license
- Start with VSA.md when you need the current rules.
- Use Archive/ only for historical comparison or version recovery.
- Treat VSA.md as the source of truth when reviewing or generating slice code.
This repository is released under the GNU License. See LICENSE for details.