Architecture and contributing

Architecture

Studio, WebMCP, and MCP converge on one planner command boundary. Shared contracts generate every public agent surface; deterministic Validation, authorization, ledger integrity, persistence, and exports remain separate deep modules.

First contributor change

1Read the source map and choose the command, Constraint, migration, or documentation path.

2Change the authoritative runtime source and its focused tests.

3Regenerate contracts, docs, examples, and skills.

4Run the complete local verification gate.

bash

npm ci
npm run verify:local

Extend commands and Constraints

Commands begin in src/contracts/venue-contracts.ts and execute only through VenuePlanner.execute.

Agent-facing commands receive one shared tool contract and authorization mapping.

Constraints enter the versioned evaluator registry and return deterministic stable-ID evidence.

Contract tests bind runtime required fields, errors, outputs, docs, examples, WebMCP, and MCP.

DOCS

Architecture

Architecture overview and diagrams Persistence and recovery diagram Optimistic concurrency Database operations

First contributor change

1Read the source map and choose the command, Constraint, migration, or documentation path.
2Change the authoritative runtime source and its focused tests.
3Regenerate contracts, docs, examples, and skills.
4Run the complete local verification gate.

bash

npm ci
npm run verify:local

Contributor entry point Local development Testing by layer Local verification

Extend commands and Constraints

Commands begin in src/contracts/venue-contracts.ts and execute only through VenuePlanner.execute.
Agent-facing commands receive one shared tool contract and authorization mapping.
Constraints enter the versioned evaluator registry and return deterministic stable-ID evidence.
Contract tests bind runtime required fields, errors, outputs, docs, examples, WebMCP, and MCP.

Add a command or Constraint Shared runtime contracts ADR Constraint registry ADR

Migrations, release, and recovery

TypeScript SDK Adapter authoring SDK API reference Schema migration guide Database operations Real-time collaboration Sharing and notifications Registration and ticketing Operational resources Threat model Resource limits Release process Release checklist Production hosting Failure recovery runbook Security reporting policy Published guide manifest

Architecture decisions

Canonical spatial frame Human Roles and Agent Grants Shared runtime contracts Constraint registry Ledger integrity and replay Server-owned tenancy Hashed bearer sharing Operational Resource Snapshots Public SDK boundary