Repository navigation
Adapt the template to a document-only shape - #1
Merged
Merged
Conversation
Instantiated from visgraf/math-ai-method at 81a638e. This repository holds one technical report, its markdown draft, and the pass that verifies its claims. There is no library, no experiment and no Python. Deleted, each with a foreclosure recording why and what reopening costs: experiments/exp000_example/, src/research/, tests/test_scaffold.py (fc-003), spikes/ (fc-004), pyproject.toml (fc-002), .github/workflows/ci.yml (fc-001). report.yml is now the only workflow and the whole automated surface. Kept, against the obvious call, and this is where the reasoning is: - docs/state.yaml (fc-005). The ledger's argument never depended on there being experiments; it exists so a later session can tell "we decided against this" from "nobody thought of it", and editorial decisions have that property. The adaptation itself generated six foreclosures, five open decisions and a stopping rule before any report work began. - docs/inherited-measurements.yaml (fc-006). A report about another project, in which every figure is inherited, is this file's ideal case rather than a category error: a count in a repository at a pinned SHA is exactly recheckable. Seeded with the four sources, two carried methods and the pair below. Found while deciding fc-006, and recorded as mn-001/mn-002: the instance's verification tally is stated as "22 claims, 10 confirmed" in claims-verified.md and as "eighteen load-bearing claims, seven stood" in draft.md, agreeing exactly on 3 corrected and 8 under-qualified. Reconcilable if "load-bearing" names a subset (met-002), which neither passage says. Neither sentence is edited; resolving them at source is od-002, blocked on gap-001. CLAUDE.md's two marked blanks are filled, including Domain invariants, where the template's "declare it at the function that returns the value" rule is inert: nothing here produces a value, so that section is the only place conventions can live. Committed direct to main at the maintainer's instruction, which overrides the branch rule in CLAUDE.md's working agreement for this commit only. Co-Authored-By: Claude Opus 5 (1M context) <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.
Instantiated from
visgraf/math-ai-methodat81a638e. This repository holds one technical report, its markdown draft, and the pass that verifies its claims. No library, no experiments, no Python.Deleted
experiments/exp000_example/,src/research/,tests/test_scaffold.py(fc-003);spikes/(fc-004);pyproject.toml(fc-002);.github/workflows/ci.yml(fc-001).report.ymlis now the only workflow and the entire automated surface.One correction to the premise.
test_scaffold.pywas described as having one job (thespikes/import ban). It had four, and the.reference/guard protects a convention this repository actively depends on — the pinned checkouts are how every claim gets verified. It was deleted anyway because its precondition is that executable code exists to scan, and there is none: it would have passed by scanning an empty set. The convention now rests on a comment in.gitignore. Recorded infc-003rather than absorbed.Kept, against the obvious call
docs/state.yaml(fc-005) — the ledger's argument never depended on there being experiments. It exists so a later session can tell we decided against this from nobody thought of it, and a deleted directory leaves no trace at all. The evidence is empirical: this adaptation generated six foreclosures, five open decisions and a stopping rule before any report work began. What did not transfer is marked, not tidied —falsifier_verdictsandconstraintsare empty and may stay so.docs/inherited-measurements.yaml(fc-006) — a report in which every figure is inherited is this file's ideal case, not a category error: a count in a repository at a pinned SHA is exactly recheckable.claims-verified.mdcites ledger ids as its Source field, so deleting the ledger breaks the retained instrument.Found while deciding
fc-006The instance's verification tally appears twice and disagrees with itself:
report/claims-verified.mdreport/draft.mdThey agree exactly on 3 corrected and 8 under-qualified, and differ on the total and the confirmed count — reconcilable if "load-bearing" names a subset, which neither passage says. That is an UNDER-QUALIFIED defect in the two documents that define the category. Neither sentence is edited. They are
mn-001/mn-002; resolving them at source isod-002, blocked ongap-001.Also
CLAUDE.md's two marked blanks are filled. In Domain invariants the template's "declare it at the function that returns the value" rule is inert — nothing here produces a value — so that section becomes the only place conventions can live.Verified:
make -C reportbuilds clean fromdistclean(exit 0, no LaTeX errors), both ledgers parse as YAML, and no reference to a deleted path dangles.🤖 Generated with Claude Code