In development
Platform
The architecture of an outcome.
Every request in BIRTH follows the same path — from what you intend to a result that has been authorized, observed and verified.
From intent to outcome
- Intent + contextThe request, and the situation it was made in.
- ReasoningA plan, with assumptions stated.
- CapabilityThe skill and tool chosen for each step.
- AuthorityThe owner approves, narrows or refuses.
- ExecutionAn authority acts inside the approved limits.
- ObservationBIRTH reads what actually changed.
- VerificationThe result is checked against the plan.
- OutcomeDone, with a receipt — or stopped, with a reason.
01Layers
Applications on top. Shared systems underneath.
Applications do not each reinvent knowledge, permissions or verification. They share them — which is what makes the computer feel like one thing.
- ApplicationsFiles, Knowledge, Work, Browser, Music, Settings and the rest.
- Shared BIRTH systemsKnowledge, context, authority, observation, verification and receipts.
- CapabilitiesReason, read, search, write, analyse, automate — what the computer can do.
- ImplementationsModels, providers, host integrations and devices, all replaceable.
02Principles
Four decisions the architecture is built on.
Capabilities, not components
The system is described by what it can do. How each capability is implemented can change without changing the product.
Implementations are replaceable
Models and providers sit below the capability line, so a better one can be adopted without rebuilding what depends on it.
Authority is structural
The boundary between reasoning and action is part of the architecture, not a setting a component can bypass.
Every step leaves evidence
Observation and verification are stages of the path, so a result is only “done” when it has been checked.