What works today, and what remains gated
Offline evaluation is available. Running and recovering real sandbox work requires capabilities and evidence that Castles does not yet have.
Current implementation
| Capability | Standing at this source revision |
|---|---|
| Binding and preflight evaluation | Implemented and tested offline with synthetic fixtures. No live inspection client. |
| Report-task fixture and MVP harness | Implemented offline. The smoke script refuses unavailable live prerequisites; it is not a successful live task run. |
| Bootstrap and authorized task run | Blocked on canonical capabilities and accepted contracts. No Castles runtime path is delivered. |
| Observe, export, cancel and reuse | Not live-qualified. Containment, durable recovery and safe reuse remain gated. |
Read the acceptance notes for the full case matrix and retained limits. Their historical evidence refers to exact revisions; it must not be generalized to every later candidate.
Read evidence precisely
| Evidence | What it establishes |
|---|---|
| Fixture | A synthetic input produced a result offline. No claim about a real provider or authenticated owner. |
| Static | Source, type or documentation checks. No behavioral evidence. |
| Real daemon | A real canonical service exercised under an explicitly defined scope. No such Castles qualification is claimed here. |
| Live provider | Authorized reads or runs against the named real sandbox, with retained receipts at an exact revision. Not available from the current Castles client. |
Keep local checks, hosted checks, review, acceptance, merge and live qualification separate. A fixture-only result is never marked verified live.
Remaining gates
- Accepted read-only inspection through the canonical owner, tracked in coven-agents #296.
- Reviewed runtime and admission contracts for Castles #3, including exact target binding before task or credential effects.
- Durable results, reconnection, qualified cancellation containment and non-destructive reuse for Castles #4.
- A separately authorized named live window and measured end-to-end qualification for Castles #5.
Issue state is a coordination signal, not evidence that a capability is accepted. Consult linked contracts, reviewed revisions and receipts before opening a gate.
Contribute with an explicit handoff
The outcome issues are the specification: #1 and children #2–#5. Read the agent guide, path ownership and coordination rules before claiming work.
Use a unique worker ID, one isolated worktree and the issue handoff block. Preserve other workers' claims. Changes to shared files need a linked request and explicit steward handoff. Maintainer acceptance is required before closure.
These docs have a separate bounded task in #15. Website deployment does not authorize sandbox operations, credential changes or qualification claims.