Core concepts
The product model: Organization → Project → Goal → Department → Seat → Human/Agent → Provider/Model → Capability → Tool → Authority → Work → Approval → Execution → Evidence → Outcome → Audit.
Documentation
Every documented capability carries one of three statuses.
Available 25 Designed 5 Planned 4
Available — implemented and exercised in the development environment (route, module or test cited). Designed — specified in a controlled document, not implemented. Planned — intended, not yet designed in detail. Nothing here is production-verified.
Organizations
An organization owns projects, memberships, policies, integrations and evidence.
Projects
Projects hold source truth, goals, requirements, work and evidence.
Authority and approvals
Authority attaches to principal, seat, organization/project, capability and scope — never to a role label alone.
Agents, models and tools
Providers are adapters behind stable contracts; tools carry trust level, scopes and side-effect class.
Operations
Work, runs, incidents and operational posture.
Governance
Requirements, evidence, audit and controlled change.
Developers, API and MCP
Typed, tenant-scoped APIs and a governed MCP surface.
Administrators
Provisioning, secrets and platform administration.
Security
Tenant isolation, fail-closed privileged effects, credential isolation and resilience.
Reference
State machines and vocabularies.
Release notes
Each entry names the exact source commit and known gaps.