Skip to content

feat: make capability side_effects load-bearing (confirm tier + dependency latch) - #19

Draft
Ian-Tharp wants to merge 1 commit into
developfrom
claude/side-effects-load-bearing-jqn0en
Draft

Ian-Tharp wants to merge 1 commit into
developfrom
claude/side-effects-load-bearing-jqn0en

Conversation

@Ian-Tharp

Copy link
Copy Markdown
Owner

Opened from a finished Claude Code cloud session branch (the session pushed but didn't open a PR).

Commits

feat: make capability side_effects load-bearing (confirm tier + dependency latch)

Confirm tier: the registry's side_effects class is now enforced. A step whose
capability writes (file writes, database calls other than GET / KB search,
anything unclassified), or that the plan marked requires_hitl, is held instead
of dispatched and recorded in COREState.pending_confirmations; its dependents
wait. Evaluation turns retry/revise/finalize into ask_user, routing refuses to
retry or re-plan around a held write, and the response lists what was held and
which capability ids to approve via config["approved_capabilities"].
Orchestration marks write steps requires_hitl. CORE_CONFIRM_WRITES=0 disables.

Dependency latch: a step never runs unless every in-plan dependency succeeded.
Retries now check dependencies against prior results and resume dependents
blocked on the retried step; dependency cycles are blocked instead of run; an
LLM call that errors or returns nothing fails its step instead of passing as
success. Blocks are recorded as BlockedAction(kind, cause_step_id) and listed
in the response.

Fault capture does not count held writes as step failures and records
pending_confirmations. Docs: docs/architecture/action-confirmation.md.

Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_019KQ4Whyic9VvMvB7iAqzyu

🤖 Generated with Claude Code

…dency latch)

Confirm tier: the registry's side_effects class is now enforced. A step whose
capability writes (file writes, database calls other than GET / KB search,
anything unclassified), or that the plan marked requires_hitl, is held instead
of dispatched and recorded in COREState.pending_confirmations; its dependents
wait. Evaluation turns retry/revise/finalize into ask_user, routing refuses to
retry or re-plan around a held write, and the response lists what was held and
which capability ids to approve via config["approved_capabilities"].
Orchestration marks write steps requires_hitl. CORE_CONFIRM_WRITES=0 disables.

Dependency latch: a step never runs unless every in-plan dependency succeeded.
Retries now check dependencies against prior results and resume dependents
blocked on the retried step; dependency cycles are blocked instead of run; an
LLM call that errors or returns nothing fails its step instead of passing as
success. Blocks are recorded as BlockedAction(kind, cause_step_id) and listed
in the response.

Fault capture does not count held writes as step failures and records
pending_confirmations. Docs: docs/architecture/action-confirmation.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019KQ4Whyic9VvMvB7iAqzyu
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants