05 — VISIBLE-CONTENT COMPLETENESS

Account for all significant visible ink, including evidence missed by either CAP or MAP.

PARTIAL Partly built

Only partly implemented. The existing gates check anchor ownership, dangling references and overlap conflicts within CAP output.

Deterministic Page model 0 archived step 05 of 26

Where this output sits

Source evidence›Candidate evidence›Human decision›Audit acceptance›Release›Production

Source evidence, candidate evidence, human decision, audit acceptance, release and production are six separate things. This step produces the highlighted one and nothing further.

Scope

Intended to give every significant piece of source ink exactly one disposition — CAP_TOKEN, STRUCTURE, MEDIA, ORNAMENT, BACKGROUND_NOISE or HOLD — so that nothing visible on the page is silently unaccounted for.

This role is allowed to

Measure coverage and accounting
Escalate unmatched evidence

How it works

fed by 04 MAP-REFINE 01 CAP

Inputs

Source-ink componentsCAP-RAWMAP-GEO / MAP-REFINE

Deterministic Deterministic component matcher.

No internal sequence is documented for this step — only the contract above and below it. Nothing was invented to fill the gap.

Must pass

Unique component IDs
Zero unexplained significant ink
Non-empty reason for each HOLD

passes →

Outputs

One disposition per component: CAP_TOKEN, STRUCTURE, MEDIA, ORNAMENT, BACKGROUND_NOISE or HOLDExplicit CAP-without-region and region-without-CAP ledgers

hands off to PROTECTION · ASSEMBLE · QA

fails →

HOLD

UNACCOUNTED_INKCAP_WITHOUT_REGIONREGION_WITHOUT_CAPCAP_MISSING

Nothing continues on a failed gate. Uncertainty becomes an explicit HOLD, and no later step may read an unanswered item as an accepted one.

Non-scope — what this role does NOT own

Inferring missing text
Claiming accounting equals accuracy
Discarding small but significant components

Explicitly forbidden

Infer missing text
Call accounting accuracy
Discard small but significant components

Dependencies and position

Starts: After CAP-RAW and current MAP geometry are frozen.
Previous step: 04 MAP-REFINE
Next step: 06 STYLE
Hands off to: PROTECTION, ASSEMBLE, QA

Exact inputs

Source-ink components
CAP-RAW
MAP-GEO / MAP-REFINE

Exact outputs

One disposition per component: CAP_TOKEN, STRUCTURE, MEDIA, ORNAMENT, BACKGROUND_NOISE or HOLD
Explicit CAP-without-region and region-without-CAP ledgers

Performer and AI/ML boundary

Performer: Deterministic component matcher.
Class: Deterministic
AI boundary: None for production evidence.

Training information

Not a trained component. No model, no weights, no training corpus. Behaviour is fixed by code and configuration, and identical inputs must produce identical outputs.

Deterministic validation and acceptance gates

Unique component IDs
Zero unexplained significant ink
Non-empty reason for each HOLD

HOLD and failure behaviour

Failure codes this step may emit:

UNACCOUNTED_INK
CAP_WITHOUT_REGION
REGION_WITHOUT_CAP
CAP_MISSING

Uncertainty becomes an explicit HOLD. Omission never converts uncertainty into acceptance, and no downstream step may treat an unanswered item as an accepted one.

Downstream handoff

PROTECTION, ASSEMBLE, QA

Active tool

Status: Partial
Run / inspect: inspect READY.json gates: dangling_references, overlap_conflicts, missing_ownership
Input: review_data.json
Output: READY.json gate block

Dependencies

Built by BUILDER_STAGE_A.py / BUILDER_STAGE_B.py — see step 18

Why this is the active version

Completeness currently exists only as gates inside the review-package builder (dangling_references, overlap_conflicts and missing_ownership all required to be zero), not as a standalone tool. Those gates account for CAP-anchor ownership but NOT for source-ink components that have no CAP token at all. The V8 dispositions CAP_TOKEN, STRUCTURE, MEDIA, ORNAMENT, BACKGROUND_NOISE and HOLD are not produced by any implementation.

Copied files — source receipt

File	Original SHA-256	Bytes	Copy
`READY.json`	492579508714c8d7…	2,881	verified

1 file(s), all hash-verified against the original. Full detail in tool/SOURCE_RECEIPT.json. Copy-only: the historical source is never modified.

Archived versions

No superseded versions recorded for this role.

Known limitations

Only partly implemented. The existing gates check anchor ownership, dangling references and overlap conflicts within CAP output.
They do NOT detect visible text-like ink that CAP never captured, which is precisely the failure this role exists to catch.
'Every CAP token exactly once' proves the provider's output was preserved. It does not prove every printed word was captured. That distinction is the whole point of this step and it is currently unenforced.

Security and privacy

Operates on frozen local artifacts. No credentials required. No data leaves the machine.

Cost behaviour

No provider calls. No metered cost. Compute is local.

Copying a tool into this repository does not authorise running it, retraining it, calling a model, or processing a new issue. No paid call may be made without the owner's explicit authorisation and a hard cost cap.

Provenance

Registry: registry/roles.json (schema marsoom.e2t.roles.v1)
Derivation: 28 legacy roles - VER - HUMAN + REV = 27 active steps
Legacy role id: COMPLETENESS
Legacy source SHA-256: 6f5d5d7ed8869e45307424c2193f95ffab84abc44a6a188f5c7f98c2a48ec64d
Generated: 2026-09-04T22:13:12.433Z

Feedback and decisions

Feedback is recorded per source and never merged into an invented consensus. Where sources disagree, both positions stand and the owner decides.

Source	Events
Naser / owner Final authority. Overrides every other source.	none recorded
Codex / orchestrator Architecture and sequencing.	none recorded
Builder / designer Implementation reality and constraints.	none recorded
Independent reviewer Adversarial review of claims.	none recorded
Auditor Evidence verification against artifacts.	none recorded
Human REV reviewer Page-level truth from the review site.	none recorded

Recorded events

No feedback events recorded yet. The ledger exists and is append-only: feedback/FEEDBACK_LEDGER.jsonl.

Editing feedback is not possible: a change is a new event whose supersedes names the one it replaces, and the original stays exactly as written.

Generated from registry/roles.json by tools/build-reports.mjs. Do not hand-edit — edit the registry and rebuild.
Original page pixels are the visual authority. CAP owns the exact captured text.