Repository navigation
t27b vacuous: delete 22 empty generated spec stubs (Closes #8052) - #8054
Merged
Merged
Conversation
The 22 specs carry only comments, `module X;`, `use base::types;` and `use math::constants;` -- no const, fn, struct, enum, test, invariant or bench. Lab run 7a07828 counts each as a reference pass that t27b passes with 0 runtime asserts (pass_vacuous). Nothing imports or generates from them. Also removed: their 50 seals (matched by spec_path) and their 22 rows in docs/reports/t27b_expectations.json. Expected on the next lab run: vacuous 142 -> 120, reference denominator 1213 -> 1191. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gHashTag
enabled auto-merge (squash)
October 9, 2026 07:19
This was referenced Oct 9, 2026
Merged
Merged
This was referenced Oct 9, 2026
Merged
Contributor
This was referenced Oct 9, 2026
gHashTag
disabled auto-merge
October 9, 2026 08:12
Owner
Author
|
Auto-merge is off; this PR is held for the owner's decision. The 22 files are empty stubs: |
This was referenced Oct 9, 2026
This was referenced Oct 9, 2026
Merged
Contributor
PR DashboardGenerated at: 2026-10-09 11:37:25 UTC
Summary
Seal Status
|
This was referenced Oct 9, 2026
This was referenced Oct 9, 2026
Merged
Closed
Merged
gHashTag
pushed a commit
that referenced
this pull request
Oct 9, 2026
… (Refs #8222, Closes #7370) test-ratchet was red on this PR (and on master): #8054 deleted 22 empty spec stubs, but proofs/lean4/Trinity/IcarusLowerable/Completeness.lean still modelled them, so corpus_classifier_matches_lean_completeness found 26 envs without specs. #8223 fixes it; this is its two files, byte-identical to its head ad0b510, so it no-ops once #8223 lands. cargo test -p t27c --test icarus_lowerable corpus_classifier_matches_lean_completeness: ok. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ScHVrGSr6zZUdwkdC8DR9k
gHashTag
added a commit
that referenced
this pull request
Oct 9, 2026
#8222) (#8223) Since #8054, test-ratchet has been red on every PR. The cause is corpus_classifier_matches_lean_completeness, which reported 26 envs without matching specs where it expects 4. The other 22 were the env, module and theorem triples of the empty generated stubs that #8054 deleted. Completeness.lean loses those 66 definitions (418 lines). Nothing else referenced them, and none was in lean_completeness_mismatches.json. The test's anti-vacuity floor moves from 245 to 223. That is exactly the 22 deleted theorems: deletion, not a theorem going quiet. The four Lean-only witnesses stay as they are. Local check: cargo test --release -p t27c --test icarus_lowerable gives 359 passed. The test failed on master with the same message CI shows. Co-authored-by: Claude <claude@anthropic.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 10, 2026
dmitrii-f-t27
added a commit
to gHashTag/trinity-fpga
that referenced
this pull request
Oct 11, 2026
…agents.json after gHashTag/t27#8054 (#909) Carries #872's commit 7cf4429 unchanged (the #510 debt), plus agents.json in AGENTS.md and CLAUDE.md as a format name rather than a path, after gHashTag/t27#8054 deleted the unrelated t27 seal it matched by basename. No checker code and no baseline entry for agents.json change. Closes #908 Co-authored-by: Dmitrii Vasilev <admin@t27.ai>
This was referenced Oct 11, 2026
gHashTag
added a commit
that referenced
this pull request
Oct 11, 2026
…/string, tri/utils/error, sandbox/modules, physics/lqg_entropy (Closes #8908) (#8912) The last five pass_vacuous rows of the t27b ledger are stubs with nothing to assert (see #8766): a TODO with an empty main(), a module line with two `use` lines, a broken struct skeleton, a registry holding one `use`, and a prose file whose tests assert `true`. git grep finds no `use` of any of the five modules. They go as #8054's 22 stubs went: - the five specs, their 11 seals (spec_path matches) and their 5 ledger rows; pass_vacuous rows do not count toward max_not_pass, so it stays; - the Lean lowerability models of the three that had one (physics_lqg_entropy, tri_utils_error, tri_utils_string), and the floor of corpus_classifier_matches_lean_completeness 223 -> 220, deletion and not a theorem going quiet, as #8223 did for #8054 (hand-written lines +3 -3); none was in lean_completeness_mismatches.json; - their three lines in tools/oracle/baseline.tsv, pass 189 -> 186; - the dangling `sandbox.modules` dep of sandbox.health in architecture/graph.tri (no such node; health.t27 does not use it). lqg_entropy's prose was already section 5 of docs/nona-02-organism/physics-kepler/KEPLER-NEWTON-CHERN-SIMONS.md. Its one missing point, the two origins of gamma with its references, moves there, and the note's spec list points at specs/physics/lqg_cs_bridge.t27, which defines and tests every quantity the stub named. Lab (master 39d5af3): cargo test --release -p t27c --test icarus_lowerable, 359 passed, "220 theorems compared, 78 disagree (ledger holds 78)" (base: 223); t27b corpus before and after: the five files leave, pass_vacuous 6 -> 1 (the one left, eternal_monitor.t27, has no ledger row: the reference does not pass it). Co-authored-by: Claude <claude@anthropic.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Closes #8052
Refs #6063
Lab run 7a07828 (master, https://t27b-lab-production.up.railway.app/runs/7a07828fc8d65c9626f76018c0884a8f01e87ab7.json) has 142 specs the reference passes and t27b passes with 0 runtime asserts (
pass_vacuous). This PR deletes the 22 of them that are empty generated stubs.Deleted specs, each with the proof it was empty
Every file below was checked with the same rule: after removing blank lines and
///;comments, the only lines left aremodule <Name>;,use base::types;anduse math::constants;-- no const, fn, struct, enum, test, invariant or bench. Each had 0 tests, 0 invariants and 0 asserts in run 7a07828.specs/ml/activation/silu_swish_vbt_activation.t27SiluSwishVbtspecs/sacred/cosmology.t27TriCosmologyspecs/sacred/dark_matter.t27DarkMatterspecs/sacred/gravity.t27TriGravityspecs/sacred/monopoles.t27TriMonopolesspecs/sacred/quantum.t27TriQuantumspecs/sacred/quantum_gravity.t27QuantumGravityspecs/sacred/superconductivity.t27TriSuperconductivityspecs/tri/agent/agent_run.t27AgentRunspecs/tri/agent/agents.t27Agentsspecs/tri/agent/autonomous_universe.t27AutonomousUniversespecs/tri/agent/experience_hooks.t27ExperienceHooksspecs/tri/agent/memory.t27AgentMemoryspecs/tri/collections/context.t27TriContextspecs/tri/net/cloud.t27TriCloudspecs/tri/pipeline/cloud_orchestrator.t27CloudOrchestratorspecs/tri/pipeline/pipeline.t27TriPipelinespecs/tri/pipeline/spec_parser.t27TriSpecParserspecs/tri/pipeline/workflow_executor.t27WorkflowExecutorspecs/tri/pipeline/workflow_parser.t27WorkflowParserspecs/tri/utils/arrow_time.t27ArrowTimespecs/tri/utils/colors.t27TriColorsAlso removed
.trinity/seals/whosespec_pathis one of the 22 specs (seals are keyed byspec_path;tools/check_seal_coverage.pyfails on a seal whose spec is gone). None of them is intools/seal_baseline.txt.docs/reports/t27b_expectations.json: master's ledger minus exactly those rows (allpass_vacuous, somax_not_passdoes not move; no duplicate paths).Why nothing depends on them
git grepof each path and module name over specs/, tools/, scripts/, .github/, bootstrap/, cli/, docs/: nouseof them, no generated file under gen/, no row insuite_expectations.json, no open PR touching them (checked the file lists of all open PRs).docs/reports/WAVE_LOOP_*,CORPUS-CENSUS-W737.tsv,data/W569/W600lists) andtools/oracle/baseline.tsv. The oracle's ratchet compares only the pass count against its 189 floor (the 2026-10-08 nightly passed 1105 of 1600), and the oracle job iscontinue-on-error, so the baseline is left as its own tool wrote it.#7828(graph memory epic) already saysspecs/tri/agent/memory.t27"MUST be removed or replaced".Check with the repo's tool
python3 scripts/tri_loop/t27b.py ratchet(=tri t27b ratchet):UNEXPECTED FAILURE 11, UNEXPECTED PASS 2, UNLISTED 80, STALE 3, MOVED 3So the PR adds no ratchet finding; master's ledger is already red for other reasons (another bless is in flight).
Not in this PR
Three more specs are empty in the same way but an open issue names them in its scope and criteria, so they stay:
specs/tri/math/math.t27(#7746),specs/tri/math/measurement.t27(#2101),specs/tri/utils/string.t27(#8013, #6654, #2665, #2433, #2526).Expected effect
Next lab run at master: vacuous 142 -> 120, reference denominator 1213 -> 1191, t27b checked passes unchanged (899 of 1213 -> 899 of 1191).
Files: 22
.t27deletions, 50 seal deletions (tool-written), 1 ledger edit (tool-written data), 1 NOW entry. No hand-written code.🤖 Generated with Claude Code