← E2T System V1 portal

14 — ISSUE-LINK

Connect content and repeated furniture across pages without turning a plausible continuation into accepted fact.

ACTIVE Built and verified

1 tool file copied and hash-verified against the original.

Deterministic Content graph 1 archived step 14 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

Joins the accepted page graphs across the issue: article continuation onto later pages, repeated header and footer identity, continuation links and permanent article identity — with an explicit unbound state where evidence is insufficient.

This role is allowed to

How it works

fed by 13 ORDER
Inputs
Page graphsIssue page orderRepeated-furniture and continuation evidence
Deterministic Deterministic graph adapter; structured AI may propose edges.

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

Must pass
  • Acyclic graph
  • At most one accepted incoming/outgoing continuation where policy requires
  • Ambiguity stays HOLD
passes →
Outputs
Cross-page continuation graphRepeated header/footer identityPermanent issue-local article IDsContinuation HOLDs
hands off to TAG · DGTL · ARCH · ASSEMBLE
fails →
HOLD
LINK_AMBIGUOUSLINK_CYCLELINK_MULTIPLE_PARENTLINK_MISSING_ENDPOINT

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 all PAGE-ORDER graphs for the issue.
Previous step
13 PAGE-ORDER / ORDER
Next step
15 TAG
Hands off to
TAG, DGTL, ARCH, ASSEMBLE

Exact inputs

Exact outputs

Performer and AI/ML boundary

Performer
Deterministic graph adapter; structured AI may propose edges.
Class
Deterministic
AI boundary
Proposal-only.

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

TAG, DGTL, ARCH, ASSEMBLE

Active tool

Status
Active tool
Run / inspect
continuation emitted by MAP-AI as field `b`: C = continuation, O = open, U = unbound, with `lg`/`rg` neighbour group ids
Input
accepted page graphs + issue manifest
Output
detail-response field `b`

Dependencies

Why this is the active version

Cross-page continuation is a first-class typed field with an explicit unbound state, and it was exercised as a dedicated run (V96 FLEX_MAP_CONTINUATION) inside the SUCCESS_001 lineage. The issue-4547 review package preserved 9 cross-page groups through V001 to V003 — direct evidence the mechanism works end to end.

Copied files — source receipt

FileOriginal SHA-256BytesCopy
schemas/detail-response.schema.json 4b73e8c39581ca16… 2,721 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

Archived versionWhy supersededRetained valueBytes
MARSOOM_REV6_PHASE1_ISSUE_4547_GEMINI_3_8_FLEX_MAP_CONTINUATION_APPEND_ONLY_V96_2026-09-03 Run package, folded into the V114 contract The successful continuation run and its accepted responses referenced

1 archived version(s). Historical packages are never deleted or mutated; large ones are referenced with verified paths rather than copied, because the source archive is 11 GB.

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
ISSUE-LINK
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.