Forge Platform
The operating architecture for human + agent delivery. Forge Platform is not another AI tool — it is how conceptual intent, instrumental services, governed interaction, and continuous evidence fit together without…
Explore the architecture · Start reading
Why Platform
AI tools create speed, but teams still need clear intent, review gates, and evidence. When meaning, services, agent authority, and human accountability live in separate tools, agents inherit fragmentation. Platform defines operating strata — each with multiple components — so humans stay accountable and agents stay bounded.
Operating strata
How it works
- Frame
Conceptual stratum sets intent and policy.
- Sense
Lenses makes workspace structure visible.
- Reason & execute
LCDL and Fleet run inside explicit limits.
- Delegate
Agents receive workcells — not open authority.
- Gate
Humans approve, escalate, or stop.
- Record
Evidence spine captures every run for review.
Trust and boundaries
Strata, not products
Products are instruments inside strata — never the architecture itself.
Interaction is dual
Agent permissions and human obligations are two faces of one surface.
Instrumental is parallel
Sensing, reasoning, and execution are separate capabilities with separate failure modes.
Evidence is continuous
ForgeRun, ADRs, and sprint proof wrap the whole stack — not a final checkbox.
Choose your path
Platform glue
Schemas, intersection maps, and integration contracts tie the strata together — see the architecture hub and ecosystem reference. Products listed above are instruments, not layer names.
For maintainers
Canonical Markdown lives in autowww/forge-platform. Published HTML is built by forge-platform-website (python3 generator/build-site.py). See Operating cadence for hydration, quality gates, and promotion rules — not the homepage story.