OSS-Singularity/zcode-dispatch-observatory
OSS-Singularity/zcode-dispatch-observatory
Watch
1
0
Fork
You've already forked zcode-dispatch-observatory
 0
Code Issues Pull requests Projects Releases 137 Packages Wiki Activity Actions

Pinky SSSS: the attribution-honesty fix — the RRRR reject honored (v1.102.0) #137

Merged
ClaudiuSchuster merged 2 commits from oss-oo/pinky-ssss-attrfix into main 2026-10-17 04:33:38 +00:00
Conversation 0 Commits 2 Files changed 13 +443 -88
ClaudiuSchuster commented 2026-10-17 04:32:47 +00:00
Owner

The RRRR validator rejected v1.101.0's attribution chain on one MAJOR + one MINOR. This round fixes exactly those, ships v1.102.0, and re-measures everything else green (untouched).

F1 (MAJOR) — the false-attribution cure: _attr_scan_hits (formerly _attr_scan_source) now scans only tool parts created AT-OR-BEFORE the send stamp — a post precedes the send it causes, and a read-back check AFTER the send is not a post. The validator rig's P4c quoter (the fleet's standard transcript-grep delivery check, 30 s after send) can never be named again.

F2 (MINOR) — per-delivery binding: each delivered message correlates against its OWN send-stamp window; the delivery binds the EARLIEST suitable posting act, and one act carries exactly ONE delivery — same-body siblings consume their acts in send order (album actMs/bodySha carries the consumption across renders). A byte-identical double-steer now names each delivery's own carrier. A photo-finish between two free acts stays 'user' with the album recording the ambiguity reason.

Trust gate: RRRR-era scan findings (recorded under the rejected window+binding, no v2 markers) are dropped at album load — a false attribution never renders again after the upgrade; machine sources stay vintage-proof (by construction).

F3: all four machine callers (guardian, starvation watch, throttle, turn-retry) named on every claim surface.

Regression evidence: the validator rig's P4b/P4c shapes ported as suite legs, plus window/ambiguity/warm-render/legacy-album legs — 8 new legs, 1741 total, 5 skips. Red proof: 7/8 new legs fail on pristine RRRR code (c74a0b5), both mandated shapes red; all green here. Super-Linter six lanes exit 0 (the R0904 catch on the first run proves the lanes ran).

The RRRR validator rejected v1.101.0's attribution chain on one MAJOR + one MINOR. This round fixes exactly those, ships v1.102.0, and re-measures everything else green (untouched). **F1 (MAJOR) — the false-attribution cure**: `_attr_scan_hits` (formerly `_attr_scan_source`) now scans only tool parts created AT-OR-BEFORE the send stamp — a post precedes the send it causes, and a read-back check AFTER the send is not a post. The validator rig's P4c quoter (the fleet's standard transcript-grep delivery check, 30 s after send) can never be named again. **F2 (MINOR) — per-delivery binding**: each delivered message correlates against its OWN send-stamp window; the delivery binds the EARLIEST suitable posting act, and one act carries exactly ONE delivery — same-body siblings consume their acts in send order (album actMs/bodySha carries the consumption across renders). A byte-identical double-steer now names each delivery's own carrier. A photo-finish between two free acts stays 'user' with the album recording the ambiguity reason. **Trust gate**: RRRR-era scan findings (recorded under the rejected window+binding, no v2 markers) are dropped at album load — a false attribution never renders again after the upgrade; machine sources stay vintage-proof (by construction). **F3**: all four machine callers (guardian, starvation watch, throttle, turn-retry) named on every claim surface. **Regression evidence**: the validator rig's P4b/P4c shapes ported as suite legs, plus window/ambiguity/warm-render/legacy-album legs — 8 new legs, 1741 total, 5 skips. Red proof: 7/8 new legs fail on pristine RRRR code (c74a0b5), both mandated shapes red; all green here. Super-Linter six lanes exit 0 (the R0904 catch on the first run proves the lanes ran).
Pinky SSSS: the attribution-honesty fix — the RRRR reject honored (v1.102.0)
Some checks failed
Checks / Functional checks (pull_request) Has been cancelled
Details Explain this check
8a2e9e533b 
F1 (MAJOR): the posting-act scan ends AT the send stamp — a post
precedes the send it causes, so a non-posting checker's read-back
after the send (the fleet's daily transcript-grep delivery check)
never enters the window and can never steal the attribution.

F2 (MINOR): per-delivery binding — each delivered message correlates
against its OWN send-stamp window; the earliest suitable posting act
carries the delivery, and one act carries exactly ONE delivery
(same-body siblings consume their acts in send order via the album's
actMs/bodySha seam, across renders). A photo-finish between two free
acts stays 'user' with the album recording the ambiguity reason.

Trust gate: RRRR-era scan findings (recorded under the rejected
window+binding, no v2 markers) never render again; machine sources
stay vintage-proof.

F3: all four machine callers (guardian, starvation watch, throttle,
turn-retry) named on every claim surface.

Regression legs: the validator rig's P4b/P4c shapes ported (both red
on RRRR code, green here) + window/ambiguity/warm-render/legacy-album
legs — 8 new suite legs (1741 total).
SSSS: README timeline PR number (#137)
All checks were successful
Checks / Functional checks (pull_request) Successful in 19s
Details Explain this check
3ab0fedffc
ClaudiuSchuster deleted branch oss-oo/pinky-ssss-attrfix 2026-10-17 04:33:38 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
OSS-Singularity/zcode-dispatch-observatory!137
No description provided.