← E2T System V1 portal

26 — ARCH

Create stable issue-level discovery, indexing, and permanent identity independently of rendering.

PARTIAL Partly built

Only a table-of-contents group overlay exists, inside the viewer bundle.

Deterministic Products 0 archived step 26 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 table of contents, archive and tag and date indexes, search records, permanent article identifiers and permanent URLs — keeping a native article date and an inherited issue date strictly distinct.

This role is allowed to

How it works

fed by 25 DGTL
Inputs
Issue metadata and article IDsVerified TAG labelsIssue date, native article dates and source links
Deterministic Deterministic archive/index service.

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

Must pass
  • Stable IDs and source links
  • Every indexed field has provenance
  • DGTL rendering and ARCH indexing remain distinct artifacts
passes →
Outputs
One issue TOCArchive, tag, date and search indexesPermanent article URLs and continuation-aware records
hands off to Search/navigation · Authorized public archive
fails →
HOLD
ARCH_UNSTABLE_IDARCH_DATE_UNPROVENARCH_FURNITURE_LEAKARCH_INDEX_MISMATCH

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 permanent article IDs, verified tags and date provenance exist.
Previous step
25 DGTL
Next step
none — terminal step
Hands off to
Search/navigation, Authorized public archive

Exact inputs

Exact outputs

Performer and AI/ML boundary

Performer
Deterministic archive/index service.
Class
Deterministic
AI boundary
None.

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

Search/navigation, Authorized public archive

Active tool

Status
Partial
Run / inspect
TOC groups are embedded in the viewer data by build_viewer.py
Input
issue metadata + article IDs + verified tags
Output
TOC group overlay data only

Dependencies

Why this is the active version

A TOC and group index exists inside the viewer bundle. The rest of the ARCH contract does not: no archive index, no tag or date index, no search records, no permanent article IDs and no permanent URLs. The native-versus-inherited date distinction that the gate requires is not implemented anywhere.

Copied files — source receipt

FileOriginal SHA-256BytesCopy
issue_viewer/review_data.js 55f2d1c92940d9c6… 12,004,965 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

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