Repository navigation
chore: close the three unblocked items /falsify found - #177
Merged
Merged
Conversation
#103, #104, #158 — each actionable with no external dependency, each known for days or weeks, each walked past. #103: deleted views_postprocessing/reconciliation/ — stale bytecode left when the module was retired in #62 (2026-06-26). Untracked, so nothing leaves history. It had already misled one in-session inspection into reporting the migration unfinished, which is what register C-47 exists to record. #104: the README's PROD_FORECASTS collection placeholder carried "TODO: verify against live Appwrite". The answer had been sitting in ADR-013 §7(b) since 2026-07-19 — the views-models seat verified the correct values (database file_metadata, collection production_forecasts) after the phantom-collection postmortem. Filled in from our own record. I rewrote that exact README section yesterday and left the TODO standing. #158: PLATFORM-001 is retired platform-wide; the seam contract is now "The Appwrite Seam Contract" at docs/ADRs/platform/appwrite_seam_contract.md. Renamed in this repo's citations — docs/CLONING.md, README.md, ADR-013. The risk register keeps the historical ID where entries describe what was true when written; the contract is referenced by URL at a pinned commit either way, never copied. None of these was blocked on anything. They surfaced because /falsify went looking at the issue list rather than at the state I had touched — which is how the audit disproved "there is nothing more to do". ruff clean; 305 passed, 5 known local pyarrow byte-parity failures (C-72). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Aug 1, 2026
Polichinel
added a commit
that referenced
this pull request
Aug 1, 2026
…e guard cannot catch (#179) Two entries sat under Open with their defects already fixed: - C-63 (the silent config fork) was fixed by #149 on 2026-07-31 — the manager carries zero wire_contract branches and two launch_config asserts — but the entry never moved. - C-47 (the stale reconciliation/ bytecode) was fixed by #177 hours ago. Worth naming precisely: test_register_integrity.py did NOT catch either, and correctly so. It asserts that no entry whose HEADING says RESOLVED sits under Open. Neither heading said so — the code was fixed and the record was not. The guard verifies internal consistency; only reading the tree catches this. C-62's trigger had already fired. It read "when cutting this repo's first release (#125)" — 1.0.0 was tagged on 2026-08-01 and the dependency drag shipped with it. Rewritten to the half that is still ahead: the 3.0.0 bump, plus a re-check before any PyPI publish, which is the point the footprint reaches someone else. Cluster M added: five open concerns, one upstream publish. C-44, C-62, C-72, C-73 and C-07 all resolve on the pipeline-core 3.0.0 pin bump and none can be taken before it. They had been readable as five separate backlog items; they are one blocked action. What this repo owes at the bump is a single verification — confirm the delivery selects the run it expects — recorded in C-73's trigger. Register: 73 concerns, 24 open, 49 resolved. Integrity guard green. Co-authored-by: Claude Fable 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.
/falsifydisproved "there is nothing more to do in this repo". These are the three items that were actionable with no external dependency — each known for days or weeks, each walked past.#103 — deleted
views_postprocessing/reconciliation/, stale bytecode left when the module was retired in #62 on 2026-06-26. It had already misled one in-session inspection into reporting the migration unfinished, which is exactly what register C-47 records.#104 — the README's
PROD_FORECASTS_COLLECTION_IDcarried "TODO: verify against live Appwrite". The answer had been in ADR-013 §7(b) since 2026-07-19 — the views-models seat verified it after the phantom-collection postmortem (databasefile_metadata, collectionproduction_forecasts). Filled in from our own record. I rewrote that exact section yesterday and left the TODO standing.#158 —
PLATFORM-001is retired platform-wide; the seam contract is now The Appwrite Seam Contract. Renamed in this repo's citations. The register keeps the historical ID where entries describe what was true when written.None was blocked. They surfaced because the audit went looking at the issue list rather than at the state I had touched — which is precisely how it disproved the claim.
ruffclean · 305 passed · 5 known pyarrow byte-parity failures (C-72).🤖 Generated with Claude Code