Skip to content

[TRACKING] Every claim checkable — execution checklist (#181) #191

Description

@Polichinel

Execution checklist for epic #181 — Every claim checkable: clear the unblocked debt before the views-pipeline-core 3.0.0 bump.

Cross them off in order. S1–S5 are independent and may move in parallel if needed; S6–S8 have real dependencies; S9 closes.

The work

Dependency graph

S1 #182 ─┐
S2 #183 ─┤
S3 #184 ─┼──> S6 #187
S11 #197 ─> S4 #185 ─┤
S5 #186 ─┼──> S7 #188
         └──> S8 #189
S10 #192 ┘
                       all ──> S9 #190

Ritual between every story

/review-diff  →  /register-risk if findings  →  address  →  /ship-it  →  push  →  PR  →  CI green  →  merge to development

The standing checks — run these every story, not just at the end

ruff check .
pytest -q                                        # 5 known pyarrow failures only (C-72); CI authoritative
git diff --stat origin/main -- tests/fixtures/          # MUST be empty — ADR-013 is byte-frozen in this epic
pytest -q tests/test_register_integrity.py tests/test_clone_readiness.py tests/test_wire_fixture.py

By S9 these must also be empty:

grep -rn "PLATFORM-001" --include=*.py .
grep -rn "/home/simon" tests/

What this epic does NOT touch

Recorded here so nobody re-litigates it mid-sprint.

Blocked on views-pipeline-core 3.0.0 — Cluster M, six entries, two Tier 2: C-44, C-58, C-62, C-72, C-73, C-07. One publish clears all six. Not engineering work here.

Owned by another repo: C-13 / C-28 (pipeline-core #248, #347) · C-26 (#366) · C-27 (#367) · C-24 (faoapi #222) · C-43's assignment-correctness half (views-datafactory #387).

Deliberately deferred: C-33 / #97 · C-40's double-inheritance shell · #96 · C-15's pipeline-core-dependent half.

Refused on principle: no shared abstraction over appwrite_env and launch_config. WET before DRY; the named trigger to revisit is a third entry-validation module.

Expected end state

before after
register open 25 15
register resolved 49 59
entries open with their closing condition met 3 0, enforced by test
declared scan roots in tests/ that do not exist 4 0, enforced by test
PLATFORM-001 in .py 4 0, enforced by test
machine-specific paths in tests/ 1 0
gaul_lookup.version() can return "unknown" yes no — the branch is gone
ADR-013 contract_version 1.5 1.5

Activity

  1. added
    epicA large capability spanning multiple stories
    planningInvestigation/spike/decision work
    on Aug 1, 2026
  2. Polichinel commented on Aug 1, 2026

    @Polichinel
    CollaboratorAuthor

    Correction to the standing checks, before any story runs.

    The byte-freeze check was written as git diff --stat main -- tests/fixtures/. Caught during S1: a local main ref can be stale — mine still pointed at adcd5de ("Merge pull request #2"), long predating the 1.0.0 merge, so the command reported 10 changed fixture files on a branch that touched none of them.

    A verification command that produces a false alarm gets ignored after the second time, which would have defeated the point of freezing the wire. Corrected in #181, #186, #190 and above to:

    git fetch origin
    git diff --stat origin/main -- tests/fixtures/     # must be empty
    

    Fitting first finding for an epic about claims that nothing checks.

  3. Polichinel commented on Aug 1, 2026

    @Polichinel
    CollaboratorAuthor
  4. Polichinel commented on Aug 1, 2026

    @Polichinel
    CollaboratorAuthor

    Next up: S3 #184 — and note F4 from S1's review: S3 must be re-read against the tree rather than applied from its issue text, because S1 moved the message it edits into a local err_msg.

  5. Polichinel commented on Aug 2, 2026

    @Polichinel
    CollaboratorAuthor

    Corrections pushed to #187 (S6): the registry is now v1.4.0, not 1.3.0, and b54928f is pinned in two files that must move together.

    Next up: S4 #185.

  6. Polichinel commented on Aug 2, 2026

    @Polichinel
    CollaboratorAuthor

    Pre-S4 issue sweep — one blocker found, one story added.

    S11 #197 — run before S4. Epic #148's story #154 ("correct ADR-012 and the manager CIC to describe what the code is") was closed 2026-08-01 with ADR-012 done and the rest not. 18 references to code deleted by #149/#153 survive across four living docs. tests/test_doc_accuracy.py scans all four but its ban list only knows the ADR-011-era symbols, so it passed.

    Second "closed but undone" story issue after #158; seventh instance of the stale-claim class in three days.

    Ordering is forced, not stylistic: the ban list cannot be extended until all four docs are clean, so it is one atomic story — and 5 of the 18 hits are in the CIC that S4's file list already includes.

    Other open issues reviewed — none blocking:

    issue verdict
    #18 C-03's other half, and stale like #15 was (enrichment_description is gone). S4 handles it — close or narrow, after checking existing coverage. Noted on the issue.
    #90 Collides with S5 #186: both rewrite build_gaul_lookup.py, and #90's parity target ("metadata identical") is what #186 deliberately changes. Noted; re-baseline after #186.
    #89 Stale paths only — unfao/enrichment.py → contract/, _read_version → gaul_lookup.version(). Substance unaffected. Noted.
    #125 Legitimately open, not stale: git merge + tag 1.0.0 done; GitHub release and PyPI deliberately held for the platform signal.
    #123 Genuine open decision (Kosovo / GAUL coding, crosswalk ownership). Operator + platform call, not this epic's.
    #172, #174, #11, #133, #146 Blocked upstream — Cluster M, pipeline-core, faoapi.
    #96, #97, #40, #85/#93 Deferred by design; D-11 and #148 both held that line.
  7. Polichinel commented on Aug 2, 2026

    @Polichinel
    CollaboratorAuthor

    Next up: S4 #185 — and its CIC check is now satisfied, so it can focus on test_validation.py and #18.

  8. Polichinel commented on Aug 2, 2026

    @Polichinel
    CollaboratorAuthor

    Register: 74 concerns, 21 open, 53 resolved.

    Remaining: S5 #186 (largest — rebuilds the committed lookup) · S6 #187 · S7 #188 · S8 #189 · S10 #192 · S9 #190 closeout.

  9. Polichinel commented on Aug 2, 2026

    @Polichinel
    CollaboratorAuthor

    Register: 74 concerns, 20 open, 54 resolved. Cluster K down to C-46 alone.

    Remaining: S6 #187 · S7 #188 (closes Cluster K) · S8 #189 · S10 #192 · S9 #190 closeout.

  10. Polichinel commented on Aug 2, 2026

    @Polichinel
    CollaboratorAuthor

    Register: 74 concerns, 19 open, 55 resolved.

    Remaining: S7 #188 (closes Cluster K; adopts S6's helper and inherits the CI decision) · S8 #189 · S10 #192 · S9 #190 closeout.

  11. Polichinel commented on Aug 2, 2026

    @Polichinel
    CollaboratorAuthor

    Register: 74 concerns, 18 open, 56 resolved.

    Remaining: S8 #189 (correction procedure; carries two operator questions) · S10 #192 (redaction guard) · S9 #190 closeout.

  12. Polichinel commented on Aug 2, 2026

    @Polichinel
    CollaboratorAuthor

    Register: 74 concerns, 17 open, 57 resolved.

    Remaining: S8 #189 (correction procedure — carries two questions only the operator can answer) · S9 #190 closeout.

  13. Polichinel commented on Aug 2, 2026

    @Polichinel
    CollaboratorAuthor

    Register: 74 concerns, 15 open, 59 resolved. Only S9 #190 (closeout) remains.

  14. Polichinel commented on Aug 2, 2026

    @Polichinel
    CollaboratorAuthor

    All eleven stories complete. Register 74 concerns, 15 open, 59 resolved; Clusters K and L closed; ADR-014 written.

    Final state, every line a command:

    ruff check .                                      clean
    pytest -q                                         307 passed, 3 skipped, 41 xfailed, 5 known pyarrow
    git diff --stat origin/main -- tests/fixtures/    empty
    CONTRACT_VERSION                                  "1.5"  (unmoved all epic)
    grep -rn PLATFORM-001 --include=*.py              0
    grep -rn "/home/" tests/ scripts/ pkg/            0
    views_pipeline_core importers                     1
    
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    epicA large capability spanning multiple storiesplanningInvestigation/spike/decision work

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions