CastlesDocs
OverviewDocumentation preview

What is Coven Castles?

Castles is a small, CLI-first operator package. It evaluates whether one existing Daytona sandbox matches the supported profile for a familiar: a purpose-scoped agent. It reports its findings; the canonical owning service retains authorization and lifecycle control.

The current package runs offline preflight evaluation and synthetic fixtures. A live inspection client has not shipped. You can learn the contract and exercise failures today, but Castles cannot currently establish live sandbox readiness.

One explicit target

01 / BindName the exact target

Profile, owner record, sandbox ID and generation.

02 / InspectUse the canonical owner

A constrained read-only seam, pending upstream.

03 / ReportKeep evidence visible

Status, reasons and redacted observations.

A sandbox ID selects a target. It does not grant permission. Failed, missing or ambiguous lookups never fall back to a name, label, first match or replacement.

Start with the contract

Inspection leaves control with the owner

Castles never creates, starts, stops, resizes, archives, resets or deletes a sandbox, and never repairs provider configuration. A stopped sandbox stays stopped. Any separately authorized lifecycle operation belongs to the existing Coven Agents lifecycle owner.

Even read-only provider inspection may count as activity and affect idle timers. Check when needed; do not turn preflight into permanent polling. See the trust boundary for details.

Search only Coven Castles documentation.