docs(architecture): refresh current-system architecture to main@d3462a5 - #176
Merged
Merged
Conversation
Bounded one-file refresh under explicit implementation authority, from exact base d3462a5. Five frozen section replacements, derived from a read-only repository census: - Status and Verification Basis: re-pin from 1c2d624 (2026-08-01) to d3462a5 (2026-08-12). Records that main advanced 86 commits, most of it governance/documentation work, and names the architecture-relevant runtime/config changes as CR-DD-014 model binding (including the [capability] block now in triagecore.toml), CR-DD-017 blocked-route evidence parity, and CR-DD-018 specialist-offload evidence. CR-DD-016 is recorded as documentation/CLI-help only, not a topology change. - tc run Integration Status row: adds explicit local model binding, the ProjectSteward sensitive-context boundary, and route/worker evidence persistence to the stated sequence. Kept architectural; event-schema detail stays in lower-level docs and tests. - Key Separation Rule 2: capability resolution now also resolves an explicit route-to-model binding. Scoped to the governed tc run path, since a direct TriageClient caller passing capability=None still selects route_decision["model"]. - Authoritative Sources Verified: adds routers.py, routing/route_events.py, project_steward.py + the policy YAML, run_plan.py, model_for_route, and six focused test files. - Limitations and Drift: records SVG drift and governed_run_flow.md's older 6d58526 pin as descriptive facts. Regenerating the SVG, re-verifying governed_run_flow.md, and any Progressive Zoom addition remain separate, unauthorized work; neither file is touched here. Claim Supported, other Integration Status rows, Authority and Persistence, Key Separation Rules 1/3/4/5/6, Progressive Zoom, and Non-Claims are byte-identical to the base. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
✅ Deploy Preview for poetic-quokka-0fd859 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bounded one-file refresh of
docs/architecture/current_system_architecture.md, from exact based3462a578b8bdf15d012a8aa1d4e1962520e7c3f, applying five frozen section replacements derived from a read-only repository census. The page's own stated rule is to re-verify when its pin changes; it had been pinned to1c2d6242(2026-08-01) whilemainadvanced 86 commits.The five sections:
d3462a5(2026-08-12). Records the 86-commit advance, notes most of it was governance/documentation work not bearing on topology, and names the architecture-relevant runtime/config changes: CR-DD-014 explicit local route-to-model binding (incl. the[capability]block now intriagecore.toml), CR-DD-017 blocked-route evidence parity, CR-DD-018 specialist-offload evidence. CR-DD-016 is explicitly recorded as documentation/CLI-help only — verified against its commit, whose sole runtime-file change is argparse help text.tc runIntegration Status row — adds explicit local model binding, theProjectStewardsensitive-context boundary, and route/worker evidence persistence. Kept architectural; event-type and schema detail stays in Authoritative Sources and lower-level docs rather than the table.tc runpath:client.py:135-139still selectsroute_decision["model"]when a directTriageClientcaller passescapability=None, and the fail-closed gate atclient.py:307is guarded bycapability is not None.routers.py,routing/route_events.py,project_steward.py+policies/cybernetic_ecology_boundary.yaml,run_plan.py,CapabilityResolution.model_for_route, and six focused test files includingtest_tc_run_cli.py(assertscapability_route_binding_issuesonrunner_selected) andtest_tc_run_plan_cli.py(asserts therun_planmodel-binding forecast).governed_run_flow.md's older6d585268pin as descriptive facts only.Deliberately out of scope: regenerating
current_system_architecture.svg, re-verifyinggoverned_run_flow.md, and any Progressive Zoom addition. None of those files are touched.Test plan
docs/architecture/current_system_architecture.md.## Progressive Zoomand## Non-Claimssections IDENTICAL.governed_run_flow.md,README.md,AGENTS.md,triagecore.toml,triage_core/client.py,docs/current_backlog.md,docs/change/change_log.md.d3462a5in both the header and Limitations; the sole remaining1c2d6242mention is the intentional "replacing the prior pin" historical reference.git diff --checkclean (exit 0) — no whitespace or formatting churn.No test-suite run — documentation-only change; no runtime, config, or test file touched.
🤖 Generated with Claude Code