From 4bc1d7719cc85323538e8124b65907c121e20414 Mon Sep 17 00:00:00 2001 From: Claude Date: Sun, 10 May 2026 04:40:40 +0000 Subject: [PATCH 1/2] canon: rename audit-gates Tier-1 to spawned-agent-sessions + new substrate-options method MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The audit-gates constraint's vendor-named URI ('audit-gates-are-managed-agents') leaked Anthropic Managed Agents into a Tier-1 governance commitment that should have been substrate-agnostic. This PR treats the original as a delayed-review correction, not as supersession with old-URI preserved. Changes: - Rename canon/constraints/audit-gates-are-managed-agents.md to canon/constraints/audit-gates-are-spawned-agent-sessions.md (with content rewrite to reframe substrate as a deployment decision rather than constraint commitment). - New canon/methods/spawned-agent-session-substrate-options.md catalogues substrate options (Managed Agents, CF Sandboxes, Daytona, local Docker) with cost-and-tradeoff analysis. Names the Subscription Inclusion Lever (Claude Code via Max plan auth for headless CI ~70% cost reduction at 100-audits/day volume). Cross-references in writings/ and ledger/ kept as historical record; canon/ active references updated to the new URI in the rewritten doc. Sibling 'governance-validation-via-agents' has the same vendor-naming smell and is flagged as a follow-up rename — out of scope for this PR. Journal entry committed alongside. --- .../2026-05-10-substrate-rename-and-substrate-options.tsv | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 journal/2026-05-10-substrate-rename-and-substrate-options.tsv diff --git a/journal/2026-05-10-substrate-rename-and-substrate-options.tsv b/journal/2026-05-10-substrate-rename-and-substrate-options.tsv new file mode 100644 index 0000000..9c9339c --- /dev/null +++ b/journal/2026-05-10-substrate-rename-and-substrate-options.tsv @@ -0,0 +1,5 @@ +type typeName facet quality_score quality_max quality_level title content +D Decision 5 5 strong Tier-1 audit-gates-are-managed-agents renamed to audit-gates-are-spawned-agent-sessions The original constraint name leaked vendor identity (Anthropic Managed Agents) into a Tier-1 governance commitment that should have been substrate-agnostic. Rename treats the original as a delayed-review correction, not as supersession with old-URI preserved. Cross-references in writings/ and ledger/ kept as historical record; canon/ active references updated to the new URI. The constraint's substantive content stays the same: governance validation requires a spawned clean agent session that operates as fresh context against the artifact under review. What changes is the URI, the name, and the body's framing — substrate is now a runtime-deployment decision, not a constraint commitment. +D Decision 5 5 strong New Tier-1 method doc spawned-agent-session-substrate-options codifies substrate choice Catalogues the substrate options for hosting a spawned agent session: Anthropic Managed Agents, Cloudflare Sandboxes, Daytona, local Docker, etc. Each option's tradeoffs documented across cost, integration complexity, vendor coupling, security posture, and ergonomics. Explicitly notes the Subscription Inclusion Lever — Claude Code authenticated against an Anthropic Max plan via 'claude setup-token' produces CLAUDE_CODE_OAUTH_TOKEN for headless CI use, allowing inference axis to collapse under subscription. Headline arithmetic: 100 audits/day on Max 20x = $223/mo total vs ~$711/mo on Managed Agents (~70% reduction at this volume). Substrate stays vodka-architecture; opinions live in callers. +C Constraint 5 5 strong Vendor names do not appear in Tier-1 canon URIs Operator-as-validator catch from prior session: vendor naming smell in 'audit-gates-are-managed-agents' was not surfaced by tooled validation. Sibling 'governance-validation-via-agents' has the same shape and is flagged as a follow-up rename in scope of this PR or its successor. Tier-1 commitments name what is required structurally; vendor mappings live in method-level catalogues that explicitly enumerate options. +H Handoff 5 5 strong PR A scope: substrate rename + substrate-options method + journal klappy.dev branch claude/substrate-rename-and-options-8f57. Two file changes: (1) rename canon/constraints/audit-gates-are-managed-agents.md to canon/constraints/audit-gates-are-spawned-agent-sessions.md with content rewrite, (2) new canon/methods/spawned-agent-session-substrate-options.md cataloguing substrate options. Journal entry committed alongside. AMS adoption pointer (PR B scope at klappy/agent-messaging-service) depends on this PR's klappy:// URIs landing first. Once PR A merges, PR B for AMS becomes ready to open. From 80f15ddb443b40ab082b2be2ceda962817652af7 Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Sun, 10 May 2026 04:47:09 +0000 Subject: [PATCH 2/2] Fix extra tab in journal TSV causing column misalignment --- .../2026-05-10-substrate-rename-and-substrate-options.tsv | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/journal/2026-05-10-substrate-rename-and-substrate-options.tsv b/journal/2026-05-10-substrate-rename-and-substrate-options.tsv index 9c9339c..b03b28a 100644 --- a/journal/2026-05-10-substrate-rename-and-substrate-options.tsv +++ b/journal/2026-05-10-substrate-rename-and-substrate-options.tsv @@ -1,5 +1,5 @@ type typeName facet quality_score quality_max quality_level title content -D Decision 5 5 strong Tier-1 audit-gates-are-managed-agents renamed to audit-gates-are-spawned-agent-sessions The original constraint name leaked vendor identity (Anthropic Managed Agents) into a Tier-1 governance commitment that should have been substrate-agnostic. Rename treats the original as a delayed-review correction, not as supersession with old-URI preserved. Cross-references in writings/ and ledger/ kept as historical record; canon/ active references updated to the new URI. The constraint's substantive content stays the same: governance validation requires a spawned clean agent session that operates as fresh context against the artifact under review. What changes is the URI, the name, and the body's framing — substrate is now a runtime-deployment decision, not a constraint commitment. -D Decision 5 5 strong New Tier-1 method doc spawned-agent-session-substrate-options codifies substrate choice Catalogues the substrate options for hosting a spawned agent session: Anthropic Managed Agents, Cloudflare Sandboxes, Daytona, local Docker, etc. Each option's tradeoffs documented across cost, integration complexity, vendor coupling, security posture, and ergonomics. Explicitly notes the Subscription Inclusion Lever — Claude Code authenticated against an Anthropic Max plan via 'claude setup-token' produces CLAUDE_CODE_OAUTH_TOKEN for headless CI use, allowing inference axis to collapse under subscription. Headline arithmetic: 100 audits/day on Max 20x = $223/mo total vs ~$711/mo on Managed Agents (~70% reduction at this volume). Substrate stays vodka-architecture; opinions live in callers. -C Constraint 5 5 strong Vendor names do not appear in Tier-1 canon URIs Operator-as-validator catch from prior session: vendor naming smell in 'audit-gates-are-managed-agents' was not surfaced by tooled validation. Sibling 'governance-validation-via-agents' has the same shape and is flagged as a follow-up rename in scope of this PR or its successor. Tier-1 commitments name what is required structurally; vendor mappings live in method-level catalogues that explicitly enumerate options. -H Handoff 5 5 strong PR A scope: substrate rename + substrate-options method + journal klappy.dev branch claude/substrate-rename-and-options-8f57. Two file changes: (1) rename canon/constraints/audit-gates-are-managed-agents.md to canon/constraints/audit-gates-are-spawned-agent-sessions.md with content rewrite, (2) new canon/methods/spawned-agent-session-substrate-options.md cataloguing substrate options. Journal entry committed alongside. AMS adoption pointer (PR B scope at klappy/agent-messaging-service) depends on this PR's klappy:// URIs landing first. Once PR A merges, PR B for AMS becomes ready to open. +D Decision 5 5 strong Tier-1 audit-gates-are-managed-agents renamed to audit-gates-are-spawned-agent-sessions The original constraint name leaked vendor identity (Anthropic Managed Agents) into a Tier-1 governance commitment that should have been substrate-agnostic. Rename treats the original as a delayed-review correction, not as supersession with old-URI preserved. Cross-references in writings/ and ledger/ kept as historical record; canon/ active references updated to the new URI. The constraint's substantive content stays the same: governance validation requires a spawned clean agent session that operates as fresh context against the artifact under review. What changes is the URI, the name, and the body's framing — substrate is now a runtime-deployment decision, not a constraint commitment. +D Decision 5 5 strong New Tier-1 method doc spawned-agent-session-substrate-options codifies substrate choice Catalogues the substrate options for hosting a spawned agent session: Anthropic Managed Agents, Cloudflare Sandboxes, Daytona, local Docker, etc. Each option's tradeoffs documented across cost, integration complexity, vendor coupling, security posture, and ergonomics. Explicitly notes the Subscription Inclusion Lever — Claude Code authenticated against an Anthropic Max plan via 'claude setup-token' produces CLAUDE_CODE_OAUTH_TOKEN for headless CI use, allowing inference axis to collapse under subscription. Headline arithmetic: 100 audits/day on Max 20x = $223/mo total vs ~$711/mo on Managed Agents (~70% reduction at this volume). Substrate stays vodka-architecture; opinions live in callers. +C Constraint 5 5 strong Vendor names do not appear in Tier-1 canon URIs Operator-as-validator catch from prior session: vendor naming smell in 'audit-gates-are-managed-agents' was not surfaced by tooled validation. Sibling 'governance-validation-via-agents' has the same shape and is flagged as a follow-up rename in scope of this PR or its successor. Tier-1 commitments name what is required structurally; vendor mappings live in method-level catalogues that explicitly enumerate options. +H Handoff 5 5 strong PR A scope: substrate rename + substrate-options method + journal klappy.dev branch claude/substrate-rename-and-options-8f57. Two file changes: (1) rename canon/constraints/audit-gates-are-managed-agents.md to canon/constraints/audit-gates-are-spawned-agent-sessions.md with content rewrite, (2) new canon/methods/spawned-agent-session-substrate-options.md cataloguing substrate options. Journal entry committed alongside. AMS adoption pointer (PR B scope at klappy/agent-messaging-service) depends on this PR's klappy:// URIs landing first. Once PR A merges, PR B for AMS becomes ready to open.