Handbook
Platform architecture
Forge Platform is a governed delivery control plane with pluggable agent workcells — not a single agent-orchestration product. Read architecture as strata with multiple components; products are instruments inside those…
Hub · Updated
Operating strata
Evidence spineContinuous proof across every stratum — recorded as work moves, not bolted on at the end.5 elements
- Run lifecycle
ForgeRun
Typed runs, handoffs, and inspectable outcomes across products.
Learn more - Decisions
ADRs
Accepted boundaries and integration choices for architects.
Learn more - Delivery proof
Sprint evidence
Charters, assays, and promotion gates per milestone.
Learn more - Release
Artifacts
What shipped, with what evidence and review trail.
Learn more - Contract
EvidencePacket
Cross-product proof object tying runs to human review.
Learn more
Conceptual stratumShared meaning before any service or agent runs.4 elements
- Methodology
ForgeSDLC
Ceremonies, roles, and delivery intent for human + agent teams.
Learn more - Practice knowledge
Blueprints
Executable policy, Versonas, and SDLC playbooks.
Learn more - Charter
Platform charter
Scope, boundaries, and roadmap for the operating architecture.
Learn more - Contracts
Schemas & glossary
Machine-readable IDs for workcells, runs, and integrations.
Learn more
Instrumental stratumParallel services — sense, reason, and execute inside boundaries.6 elements
- Sensing
Lenses
Workspace truth and ForgeRun control plane before deep automation.
Learn more - Reasoning
LCDL
Schema-aware, reviewable LLM tasks and operators in Python.
Learn more - Execution
Fleet
Bounded template jobs on infrastructure you own.
Learn more - Design system
Kitchensink
Shared UX, micro-packs, and deterministic harness glue.
Learn more - Runners
forge-workcells
Private workcell runners (local LLM worker and future executors).
Learn more - Surfaces
CDP manager
Browser and SharePoint lease registry for governed automation.
Learn more
Interaction stratumGoverned teaming — what agents may do and what humans must decide.8 elements
Agent permissions
- Envelope
Workcells
Bounded units of agent work with typed request and result.
Learn more - Contract
Schemas & runners
WorkcellRequest, WorkcellResult, and campaign phases.
Learn more - Channels
forge-agents
Long-lived Matrix and bridge agents — not batch workcells.
Learn more - Alpha path
Local runner
Approve-and-run bounded checks without Fleet when appropriate.
Learn more
Human obligations
- Gates
Governed workflows
Approvals, DecisionPack, and conditional campaign rules.
Learn more - Maturity
Autonomy ladder
L0–L8 readiness bars and evidence requirements.
Learn more - Cadence
Operating model
How teams run delivery milestones and human checkpoints.
Learn more - Ownership
Intersection map
Who owns each product boundary and primary contract.
Learn more
Text fallback: Evidence spine (continuous) → Conceptual → Instrumental (parallel) → Interaction (agent permissions | human obligations). Expand each stratum above for the full element catalog.
Core architecture
- For architects — reading path — persona-ordered evaluation path with page contracts
- Platform reference architecture — flowcharts per element and integration paths
- Intersection map — where products meet and who owns what
- Ecosystem reference — repos, workcells, submodule rules
Workcells and agents
- Agents and workcells hub — Forge Agent, runners, catalog, workflows, campaign
- Workcell model — roles and request/result envelope
- Governed workflows and rules — approval gates and campaign phases
- Contracts — schema pointers and samples
Autonomy and readiness
- Autonomy levels hub — L0–L8 ladder with gates
- PoC to platform — maturity transitions
Architecture decisions (ADRs)
- ADR index — accepted boundaries for MVP foundation and beyond
Promoted standout themes
Curated architecture essays (promoted from hydration packs):