LOOK obligations: per-section PROOF-OF-LOOK freshness (#155), final-look proof/stamp/due-stage, no LOOK row kind (#68)

[MendixMau]

#155 (remainder): each PROOF-OF-LOOK line is checked against its own section's VALID AT

Problem. Master already reads the newest VALID AT anywhere in the file. That newest stamp meant the last one in the file (tail -1). _ob_look_proof_broken then compared every PROOF-OF-LOOK: screenshot with that one stamp. A review file kept as a headline plus dated addenda therefore FAULTed: the first section's honest shots read "older than VALID AT". An addendum written above the original stamp also went STALE.

Choice: section-aware, not "one report per pass". The field report in #155 shows people keep one file with addenda. The warn-on-multiple-stamps option would also need a module-review.md sentence, and that file is owned by another PR. Section-aware fits how reports are actually written and needs no skill text. A stale shot inside any section still FAULTs.

Fix (bin/lib/obligation-check.sh).

• Stamps and citations are read in file order, as one token stream, so one-line HTML works too.
• Each citation belongs to the nearest stamp above it. A citation above every stamp belongs to the first (headline) stamp.
• _ob_stale uses the stamp with the newest commit time. If any stamp does not resolve (squash, rebase, shallow clone), it falls back to master's last-in-file stamp, which is then unmeasured, so the result is never a false STALE.

Fixture. test-obligation-valid-at.sh:

• T3b: an unresolvable stamp falls back to the last stamp in the file. It fails on the PR's first head.
• T4: sectioned report → PASS.
• T5: stale shot in section 1 → FAULT (control).
• T6: addendum shot older than the addendum's stamp → FAULT.
• T7: one-line HTML → PASS.
• T8: addendum written above the original stamp → not STALE.

On master T4, T7 and T8 fail. With the fix, 9/9 pass.

Not done. Per-page staleness (a page is stale only when its own latest proof predates its own last model change). The checker has no page→file mapping, and the Stage 5 look-ledger already tracks pages one by one.

Review of merged #303: final-look

1. NOT YET DUE applies to final-look only, and only when ## Current stage is gate-check's own derived readout (the line contains "(derived by gate-check"). A hand-written or scaffold line counts as unreadable, so the row stays owed. Every other obligation keeps master's verdict exactly. (From the review of this PR: hand-written lines disagree with the gates in 8 of 12 field projects, the scaffold line often never advances, and an early stale FAIL holds the derived readout back.)
2. _ob_look_proof_broken now runs for look|final-look, as module-review.md § "The final LOOK" requires.
3. A final-look report without VALID AT is FAULT ("NO VALID AT"). Without a stamp it could never go stale.

Fixture. test-obligation-final-look.sh:

• T4/T5 now carry a real proof line.
• T6: no proof → FAULT.
• T7: no stamp → FAULT.
• T8: derived Stage 5 readout → NOT YET DUE.
• T9: derived Stage 6, all gates passed, or an unreadable line → owed.
• T10: hand-written lines → owed.
• T11: scaffold line with a module open → owed. Every other obligation line is identical with and without the register, and skeleton is still owed under a derived Stage 3 readout.

On master 3 fail. On the PR's first head 5 fail. Now 17/17 pass.

#68 (+ #188 item 6): no LOOK row kind

Decision: not needed. Whether a look happened is already recorded, and gate-check counts it:

• the look obligation (report, denominator, VALID AT, PROOF-OF-LOOK per page);
• the fidelity obligation;
• the Stage 5 look-ledger.

A LOOK kind with a hand-settable State cell would be a second record of the same fact, which is the risk #68 itself names. The rationale paragraph sits next to the Kind list in skills/brd-to-build-plan.md, which is on-demand (0 baseline words added). I propose closing #68. Note: that skill is stage-mapped, so projects get a stale-protocol-ack notice.

Checks run

• Fixtures: valid-at 9/9, final-look 17/17, obligation-fidelity 6/6, look-ledger 11/11, bug03-gates 31/31, design-reaches-app 43/43, retest-obligation-newest-report PASS.
• check-scripts, check-pr-discipline, check-portability, check-no-private-citations, leak guard, render-routing --check (79,997 baseline words, unchanged): all clean.
• Denylist grep over added lines: 0 hits.

Field run

Still owed. The checker is proven by fixtures only. #155's field report (a requirements-driven build, 2026-09-26) is the motivation, but that report is private, so no captured real report was available. The fixtures rebuild the shapes it describes by hand.

Closes #155
Refs #68 #188

🤖 Generated with Claude Code

https://claude.ai/code/session_01VJgWP5vEoAsNsJYqCDMGNw

[MendixMau]

Landed on master as part of the integration squash #329 (commit 31e90ae), after independent review — its Review: line is in that commit message. Closing as superseded.

---

Generated by Claude Code