Control-plane contracts

Architecture Docs

Canonical architecture references surfaced from `.agent/specs` through control-plane-core.

Capability Parity Contract

Canonical ownership and consumer-surface rules for shared agent capabilities.

/workspace/.agent/specs/capability-parity-contract.json

Persona Parity Registry

Live persona catalog and Laierd control-plane consumer boundary.

/workspace/.agent/specs/persona-parity.json

Workflow Bundle Parity Registry

Canonical workflow bundle registry and generated consumer bindings.

/workspace/.agent/specs/workflow-bundle-parity.json

Plan Interop Contract

Shared planning lane contract for Codex execution and Cowork orchestration.

/workspace/.agent/specs/plan-interop.md

Provider Access Parity Registry

Canonical provider access surfaces for browser-backed and server-side routing.

/workspace/.agent/specs/provider-access-parity.json

Provider routing profiles

Canonical routing summaries

Profile selection stays inside `control-plane-core`. Laierd only reflects the canonical primary, fallback, and tool-selection policy that authored registries declare.

Provider access surfaces

Server and browser access contracts

Access surfaces are authored in `.agent/specs/provider-access-parity.json` and audited before they can support live routing.

authenticated_browser_fleet

Google Billing and Firebase Cost Surfaces

google-billing-browser

Status: live

authenticated_browser_fleet

Google Calendar

google-calendar-browser

Status: live

authenticated_browser_fleet

Google Cloud Logging

google-cloud-logging-browser

Status: live

server_credentials

Google Gemini API

google-gemini-api

Status: planned

authenticated_browser_fleet

Google Gmail

google-gmail-browser

Status: live

server_credentials

OpenAI API

openai-api

Status: planned

server_credentials

Vertex AI

vertex-ai-server

Status: planned

Knowledge context

Recent architecture decisions and patterns

Durable context from `.beads/knowledge` is surfaced here so operator reviews reflect prior decisions, gotchas, and implementation patterns instead of relying on page-local summaries alone.