project-modelinglisted

Build one canonical project model — entities, boundaries, owners, lifecycle state, and end-to-end traces — and record its authoritative names in `00-control/terminology-and-ownership.md` (`TM-####`), then project that single model into every audience view without ever forking it. Use when starting Phase 2, when the project type is ambiguous, or when two documents describe the same component differently. This skill MUST be consulted because multiple independent mental models produce documents that contradict each other under diligence, and audience-specific rewriting is the single most common source of drift in a documentation package.
synaptiai/synapti-marketplace · ★ 6 · AI & Automation · score 77

Install: claude install-skill synaptiai/synapti-marketplace

# Project Modeling Phase 2. Builds the one model that all 23 documents are views over, and the vocabulary they all use. ## Iron Law **ONE MODEL, MANY VIEWS. If a view needs a new fact, the fact goes in the model first.** The moment a document invents a component name, an owner, or a boundary that the model does not carry, the package has two models. It will not notice, and the contradiction surfaces during diligence rather than during drafting. ## What the model contains | Element | Captures | Where it surfaces | |---|---|---| | Product intent vs implemented behaviour | What it is for, and what it actually does — separately | `01-project/` | | Actors, journeys, roles, permissions | Who does what, and what they may do | `01-project/`, `02-architecture/` | | Components and deployment units | Purpose, owner, runtime, interfaces, state, criticality | `02-architecture/components-and-codebase.md` | | Interfaces and contracts | Producers, consumers, transport, versioning | `02-architecture/interfaces-and-integrations.md` | | Data and its lifecycle | Stores, classes, residency, retention, deletion | `02-architecture/data-and-ai.md` | | Infrastructure and environments | Topology, promotion path, differences between environments | `02-architecture/infrastructure-and-deployment.md` | | Boundaries | Control, data, trust, failure, tenancy | Everywhere. The most load-bearing element | | Owners and decision rights | Who owns, who decides, who escalates | `00-control/terminology-and-ow