You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Algorithm rule 5: a fetched corpus is a prerequisite, and its fidelity to the source is probed before fan-out #2839
Problem. Rule 5 probes external prerequisites (tokens, logins, deploy targets) and treats MISSING and UNKNOWN in defined ways. A fetched corpus that several agents will read is a prerequisite too, but no rule probes it. When a fetch silently cuts or drops content, every agent reasons over the broken copy, and "not found" becomes a false finding.
Evidence. One install, two reflections on 2026-11-14: (1) a fetch cut each document at 8000 characters, which produced a false claim that three quotes had no source; (2) an HTML extraction lost client-rendered blocks and cut posts at an < entity, which was found only after ten author agents had reported.
Proposed change. Extend rule 5's list: "…deploy targets, and any fetched corpus a fan-out will read: a sample proves the fetched text matches its source before agents are sent. A copy that is cut or missing content is MISSING." Add the two failure shapes to rule 5's gotchas (a fetch limit that truncates without an error; client-rendered content missing from server HTML).
Related, not duplicates: #1952 (contract probe before build) and #1001 (probe before build for prerequisites), both closed, cover services and contracts, not input data.
🤖 Klaudia (AI assistant) responding on behalf of Grzegorz
Correction: this is already covered. Verification.md rule 8 (contract probe before build, from #1952) names "a file format" and "a shipped consumer's input" and asks for one probe of the actual file, and § Evidence coverage asks for one rendered instance per member type of a corpus. Both cases here were misses in applying those rules, not a gap in rule 5; rule 8 itself keeps prerequisites (rule 5) apart from the shape behind them. Closing as already covered.
Activity
gjaworski86 commentedon Nov 16, 2026
Note
🤖 Klaudia (AI assistant) responding on behalf of Grzegorz
Correction: this is already covered. Verification.md rule 8 (contract probe before build, from #1952) names "a file format" and "a shipped consumer's input" and asks for one probe of the actual file, and § Evidence coverage asks for one rendered instance per member type of a corpus. Both cases here were misses in applying those rules, not a gap in rule 5; rule 8 itself keeps prerequisites (rule 5) apart from the shape behind them. Closing as already covered.