docs(cybernetic-ecology): add boundary policy narrative page and README pointer - #175
Merged
Merged
Conversation
…ME pointer Two-path documentation slice, based on current main (938e9f2), under explicit implementation authority scoped to exactly these paths. Adds docs/operations/cybernetic-ecology-boundary.md, an explanatory narrative page covering purpose/source of truth, current integration (tc run, run_plan preview, the Worker Council escalation-packet consumer), fallback semantics (the hardcoded floor is narrower than the YAML, not a duplicate of it), decision semantics (human_only/codex are recommendations, not automatic actions; steward-triggered handoff_required is not generalized to every human_review_required field), non-claims (explicitly including that this policy carries no tribal endorsement, consultation, or representation), and verification pointers to the real test file and policy YAML. Adds one discoverability bullet to README's existing Safety Invariants list, linking to the new page. Makes the existing, already-implemented and already-tested boundary policy discoverable; does not redesign, rename, or alter any of its runtime behavior. project_steward.py, orchestration.py, client.py, run_plan.py, triagecore.toml, the YAML policy, tests, AGENTS.md, current_system_architecture.md, and backlog/change-log records are all untouched. Co-Authored-By: Claude Sonnet 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
main(938e9f26f917b4b829a64689be3117e791208f0c, the invariant-checklist citation fix), under explicit implementation authority scoped to exactly these paths.docs/operations/cybernetic-ecology-boundary.md: an explanatory narrative page for TriageCore's Cybernetic Ecology boundary policy. Covers purpose/source of truth (policies/cybernetic_ecology_boundary.yaml, configured viatriagecore.toml), current integration (the governedtc runpath,run_plan's coarseconfigured_or_hardcodedpreview field, and the Worker Council's escalation-packet consumer), fallback semantics (the hardcoded floor is narrower than the YAML — tribal/cultural terms plus onlywater intake/sewer lift, missing the YAML's regulatory and coordinate-regex rules), decision semantics (human_only/codexare recommendations, not automatic actions; the steward-specifichandoff_requiredbehavior is explicitly not generalized to everyhuman_review_requiredfield elsewhere), non-claims (explicitly stating this policy carries no tribal endorsement, consultation, or representation unless separately established), and verification pointers to the real test file and policy YAML.### Safety Invariantslist, linking to the new page.docs/backlog.mdStory 11.3), tested, and currently active — this slice documents existing behavior, it does not redesign, rename, or alter any of it.Test plan
docs/operations/cybernetic-ecology-boundary.md(new) andREADME.md(one bullet).triage_core/project_steward.py,triage_core/orchestration.py,triage_core/client.py,triage_core/run_plan.py,triagecore.toml,policies/cybernetic_ecology_boundary.yaml,AGENTS.md,docs/architecture/current_system_architecture.md,docs/current_backlog.md,docs/change/change_log.md,tests/test_project_steward_firewall.py.../../tests/test_project_steward_firewall.pyand../../policies/cybernetic_ecology_boundary.yamlin the file source.codex/agents-governance-separationcheckout remains in its original pre-existing dirty state throughout.main, verified unchanged immediately before branching.git diff --checkclean (exit 0).No test-suite run — documentation-only change, no code/config/policy touched.
🤖 Generated with Claude Code