You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Project the standardized legal matter bootstrap into ChittyCommand's existing durable intent/executor ladder. Do not create a new workflow service or persistence model.
Runtime findings
ChittyCommand is deployed and owns cc_intents, executor registry, sovereignty, retries/reclaim, Durable Objects, triage queues, legal timeline and litigation routes.
ChittyFlow is not deployed and its repo/runtime drift makes it unsuitable as the current orchestrator.
First slice
Add intent_type legal_matter_bootstrap:
payload requires case_chitty_id
classified privileged + legalink
executor is read-only
executor queries ChittyCounsel GET /case/:chitty_id/bootstrap
response is written only through existing cc_actions_log by dispatcher
no new schema/tables
no evidence/fact mutations
no external transmission
Acceptance
registered in meta/executors/index.ts
payload validated
upstream timeout/error is fail-closed
case id is URL encoded
bootstrap response provenance preserved
unit tests for success, validation failure, and upstream failure
typecheck/tests pass
docs updated only for executor registry/API behavior actually implemented
UUID audit-target boundary defect discovered during recursive review was fixed and regression-tested.
Next safe slice: reconcile service documentation/integration contract, then expose a creation/intake path only if it can be made idempotent using existing primitives. No new schema.
Activity
chitcommit commentedon Oct 13, 2026
Implementation status:
Next safe slice: reconcile service documentation/integration contract, then expose a creation/intake path only if it can be made idempotent using existing primitives. No new schema.