Docs · Status

What is proven, what is conditional, what is next.

Switchyard has moved well beyond the original CP13 prototype: the Git-host product layer, profiles/organisations, Warden-style editor workbench, Pull Requests, settings and read-only demo model now exist. This page distinguishes implemented capability from the remaining live/release certification work.

Implemented product surface

Area	Status	Evidence/meaning
Git hosting UX	Implemented	owner/repo identity, Code clone menu, source viewer, README, branches/tags, commit history/compare, PRs and repo settings.
Human task model	Implemented	Work is a human-first issue/task model with body, assignee, status and comments; Attempts are optional.
Editor	Implemented	Warden-inspired Files/Search/Source workbench, tabs, syntax highlighting, draft CAS, diff/findings and interactive Agent-to-draft proposals.
Identity	Implemented	User/org profiles, large avatars, profile READMEs, pinned repos, invitations, teams and settings surfaces.
Agent-native coordination	Implemented	Attempts, durable workflows, structured findings, Integration Queue, semantic contracts, Needs Attention and provenance.
Public demo model	Implemented contract	Anonymous browsing is restricted to public canonical repos/identities; mutation remains authenticated.

Core engineering gates already proven

PASS

Deterministic loop

Work → Attempt → execution → PR → review → preview → Integration Queue → canonical, including Switchyard-on-Switchyard dogfood.

PASS

Durable workflows

True process-death replay: completed steps replay recorded results and external effects are not duplicated.

PASS

Editor concurrency

Draft revision CAS, Agent-vs-human stale protection and external branch movement detection.

PASS

Conflict honesty

Textual merge conflicts and deterministic repair plus semantic conflicts where Git merges cleanly but a repository contract fails.

Still conditional

Real provider-backed coding AgentThe runner abstraction and coding-agent adapter path exist, but the original campaign did not execute a real provider-backed coding Agent on the control-plane host. The deterministic adapter certified the substrate. Closing this condition requires a suitable CLI/provider credential and one meaningful end-to-end Agent task.

Cloudflare pushed-event source legThe Queue→Switchyard→Trestle→SSE fast path is implemented and tested, and CP0 previously proved Artifacts event delivery. During later certification the upstream Artifacts event-subscription→Queue delivery stopped flowing account-wide, so reconciliation remains the correctness safety net until that source leg is re-certified.

Release/hardening work

Area	Remaining work
Live PX certification	Run the full Go 1.26 + live Trestle/Artifacts + fresh Chromium/Firefox matrix against the integrated PX0–PX25 product.
Security	Full authorization matrix, CSRF/session review, prompt/tool boundaries, path traversal, capability escalation and credential leak scan.
Git hardening	Protected-ref enforcement breadth, tag/delete/force movement edge cases, queue crash immediately around canonical merge.
Performance	Benchmark cached bare mirror/worktrees against the measured scratch-clone baseline.
Operations	Schema migration strategy, service lifecycle, backup/restore automation, structured metrics/logging and disaster recovery.
Public staging	Deploy behind a reverse proxy/TLS and certify anonymous demo boundaries against direct API calls.

Status principleImplemented does not mean release-certified. The product surface is broad; CP14 remains the deliberate hardening/certification phase.