OSS-first docs
These docs teach the open system first: contracts, generated surfaces, runtimes, governance, and incremental adoption. Studio shows up as the operating layer on top, not as the source of truth.
Domain docs
Lifecycle
Delivery loops, review evidence, release readiness, and managed lifecycle guidance.
Source packages
Start with packages/modules/lifecycle-core, then use the spec and runtime packages as compatibility boundaries.
- packages/libs/lifecycle
Platform stance
Define the domain once. Render web and mobile with platform-native shells after contract, role, tenant, and policy resolution.
Canonical surfaces
- Lifecycle checkpoints
- Release evidence
- Advisor workflows
Implementation notes
- Store review and release evidence as first-class artifacts.
- Let mobile expose status and approvals without hiding risk context.
Context Storage
Implement durable context, memory, provenance, and retrieval boundaries for agents and apps.
Notifications
Implement notification preferences, delivery channels, unread state, and escalation rules.
Why ContractSpec
Keep educational and comparison content reachable without letting it define the primary OSS learning path.