← E2T System V1 portal

13 — PAGE-ORDER / ORDER

Build complete within-page content units and explicit reading relationships—not merely sort boxes.

PARTIAL Partly built

Unique ownership is proven, but the typed link set is not: title-to-article and body-to-article exist, while picture and caption links cannot exist at all while step 10 has no tool.

Deterministic Content graph 0 archived step 13 of 26

Where this output sits

Source evidenceCandidate evidenceHuman decisionAudit acceptanceReleaseProduction

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

Builds the within-page graph: right-to-left line and paragraph sequence, furniture exclusion, containment, and the links that turn boxes into complete content units — title to article, body to article, caption to picture, table token to cell.

This role is allowed to

How it works

Inputs
Exact CAP aliasesValidated regions and structural rolesPIC and TABLE geometry
Deterministic Constrained structured AI may propose; deterministic graph validator accepts.

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

Must pass
  • Every CAP token exactly once
  • Graph acyclic with resolved endpoints
  • No orphan, duplicate, or cross-boundary ownership
passes →
Outputs
RTL line and paragraph orderToken/line → paragraph → article ownershipTitle/body, picture/caption and table/article linksFurniture exclusion and HOLD nodes
hands off to ISSUE-LINK · TAG · CRITICAL · ASSEMBLE
fails →
HOLD
ORDER_ORPHANORDER_DUPLICATEORDER_CYCLEORDER_EDGE_AMBIGUOUSARTICLE_BOUNDARY_CONFLICT

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

Explicitly forbidden

Dependencies and position

Starts
After CAP and page-model roles are available.
Previous step
12 TABLE-ASSIGN
Next step
14 ISSUE-LINK
Hands off to
ISSUE-LINK, TAG, CRITICAL, ASSEMBLE

Exact inputs

Exact outputs

Performer and AI/ML boundary

Performer
Constrained structured AI may propose; deterministic graph validator accepts.
Class
Deterministic
AI boundary
May share the MAP-AI/TITLE/TAG request.

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

HOLD and failure behaviour

Failure codes this step may emit:

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

ISSUE-LINK, TAG, CRITICAL, ASSEMBLE

Active tool

Status
Partial
Run / inspect
sequence emitted by MAP-AI as field `s` (array of p/a/v); unique ownership verified by analyze_duplicate_aliases.py
Input
frozen MAP/ROLE/CAP
Output
detail-response field `s` + duplicate-ownership report

Dependencies

Why this is the active version

Unique-anchor ownership is genuinely proven — the SUCCESS_001 trial recorded 13,815 source anchors each owned exactly once, with zero missing, zero duplicate and zero overlap conflicts. That is the every-token-exactly-once half of the contract. The typed link set the contract demands (title to article, body paragraphs to article, picture to article, caption to picture) is only partly present, and picture/caption links cannot exist at all while step 10 has no tool. Hence PARTIAL.

Copied files — source receipt

FileOriginal SHA-256BytesCopy
schemas/detail-response.schema.json 4b73e8c39581ca16… 2,721 verified
analyze_duplicate_aliases.py 81feb09a0310d425… 3,802 verified

2 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

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
ORDER
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.

SourceEvents
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.