Repository navigation
governance_agent: remove two orphan seal files named after a # comment #6096
Copy link
Copy link
Open
Labels
area/compilerHIR/IR/codegen/optimizerHIR/IR/codegen/optimizer
Description
Original file list
.trinity/seals/agent_GovernanceAgent.json(kept byte-identical; the two files to remove sit beside it, named in the Defect: their names hold spaces, so they cannot be a Boundary token)specs/tri/agent/governance_agent.t27(read only)
Defect
Two seal files are named after a # comment: String # phi, trinity, gematria, evolution, safety.json and its agent_ twin. They were written by a parse of specs/tri/agent/governance_agent.t27 that predates # comments, when the comment text became the module name. The spec's real seal is agent_GovernanceAgent.json. t27c seal --save refreshes the orphans along with the spec (#5971 re-sealed them), so they look current and are never cleaned up.
Original scenarios
- Given the two orphans are removed, When
t27c seal specs/tri/agent/governance_agent.t27 --verifyruns, Then it passes againstagent_GovernanceAgent.json. - Given the two orphans are removed, When
python3 tools/check_seal_coverage.pyruns, Then it reports OK with two fewer seals and the same known-broken count.
Original requirements
- FR-001: The two files MUST be removed with
git rm;agent_GovernanceAgent.jsonMUST stay byte-identical. - FR-002: No other seal file MUST change.
- FR-003: If
check_seal_coverage.pyorseal_baseline.txtnames either file, that line MUST go in the same commit.
Original checks (kept for history; the Queen does not run these)
git ls-files .trinity/seals | grep -c 'String #'prints0.python3 tools/check_seal_coverage.pyprintsOK.python3 tools/check_seal_currency.pyexits 0.
Refs #6092
Queen-runnable restatement (2026-10-05)
Deleting files is allowed under the only-t27 rule, and the bee branch queen-6096 already deletes exactly the two orphan seal files and nothing else. The original checks ran python3, which the Queen's runner does not; the checks below read the tree directly.
Boundary
.trinity/seals/agent_GovernanceAgent.jsonspecs/tri/agent/governance_agent.t27
User Scenarios & Testing
- Given master, where
.trinity/seals/holdsString # phi, trinity, gematria, evolution, safety.jsonand itsagent_twin, when both are deleted, then neither path exists andagent_GovernanceAgent.jsonis unchanged.
Requirements
- FR-001: The two orphan seal files named after the
#comment MUST be deleted;.trinity/seals/agent_GovernanceAgent.jsonMUST stay byte-identical and no other seal file may change. - FR-002: The change MUST NOT add or modify non-t27 hand-written code (specs/policy/own_language.t27).
- FR-003:
specs/tri/agent/governance_agent.t27is read only.
Success Criteria
grep -rl '' .trinity/seals | grep -c 'String # phi, trinity, gematria'prints0test -f .trinity/seals/agent_GovernanceAgent.json && echo keptprintskept
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/compilerHIR/IR/codegen/optimizerHIR/IR/codegen/optimizer
Activity
gHashTag commentedon Oct 4, 2026
Steward check of
queen-6096(aaaa135)The diff deletes the two orphan seal files and nothing else (28 lines removed).
Checked against the Success Criteria:
git ls-files .trinity/seals | grep -c 'String #'prints0on this branch. Holds.check_seal_coverage.pyandcheck_seal_currency.pywere run on the lab run of aaaa1355e. Both are red, but not because of this change. Seals scanned went from 1450 to 1448, and the only failures are the 3 stale seals that are red on master too:runtime-process.json+ its twin, andautomation_automation::kanban_card_chat.json. fix(seals): re-seal runtime/process and kanban-card-chat (Closes #6256) #6257 re-seals all three, and it is green on the lab. Once fix(seals): re-seal runtime/process and kanban-card-chat (Closes #6256) #6257 lands and master is merged into this branch, both checks should pass with no further change here.tri misread: 0 of 35 pairs silent, unchanged.What is still missing: a pull request from
queen-6096. The commit already carriesCloses #6096.Refs #6092
gHashTag commentedon Oct 5, 2026
The branch queen-6096 carries only two deletions of JSON seal files under .trinity/seals/, which the only-t27 rule allows, so it was flagged only because the names have no recognised extension and contain spaces. No t27 code is needed; the issue was restated with checks that read the tree. The branch is not deleted and can land as it is.