Method · Code & architecture
The Seven Ownership Architecture
Map who owns each responsibility in a system and separate its identity, current state and next ideas.
Repository: CinvanaAI/seven-ownership-architecture
Worked design example. A worked design method and examples.
See the idea in action.
A worked ownership map and separate identity, current-state and future-direction records.
A small CSV importer with responsibilities mixed into its interface.
# CSV importer: current structure Audit snapshot: **designed scenario**, not observed external software. Confidence applies only to the stated example. Evidence anchor: the callback described in README.md. The button callback performs external reading, rule decisions, orchestration, persistence and rendering. No separate headless entrypoint exists in the scenario. Files are not yet separated into the proposed owners. Pressure signal: a command-line import would duplicate column validation. Strength: strong within this scenario. Risk: the desktop and command-line paths could accept different schemas while both say “valid.” Correctly placed: selecting a file and rendering user feedback belong to the interface. Fused responsibility: choosing the rules and persisting the accepted rows do not need to depend on that interface. Open question for a real audit: is a separate import runner already present elsewhere? Inspect the call path before claiming it is missing.
Follow the worked example.
Open the worked CSV import scenario. Follow how each responsibility owns a decision, its evidence, and its handoff; no installation is needed.
Open the source and walkthrough ↗The interesting part.
Keeping identity, current implementation and future intent separate prevents architectural documents from claiming planned behavior already exists.
Where it came from.
Ownership architecture developed during Skeleton rebuilding.
Preserves normative laws and dated application audits, with a worked example.
The method and historical audit claims are separate from the current executable Skeleton implementation.
Follow the family: Skeleton and the ownership rebuild