12 — TABLE-ASSIGN

Bind exact CAP tokens to accepted table cells.

NO TOOL Nothing implements this step

Blocked upstream: token-to-cell assignment is undefined while step 11 produces no cells. The QA gate token-cell assignment at least 0.99 with zero neighbour concatenation cannot be evaluated.

Why it is held: Blocked by step 11 NO_ACTIVE_TOOL.

Deterministic Page model 0 archived step 12 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 attach CAP tokens to frozen physical cells using overlap evidence only, holding anything ambiguous, and never concatenating neighbouring cells.

This role is allowed to

Use bounded overlap and containment
Preserve token order inside cells

How it works

fed by 11 TABLE-PHYSICAL

Inputs

Frozen table geometryExact CAP token polygons

Deterministic Deterministic geometry assignment.

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

Must pass

Each table token has exactly one cell/HOLD owner
Cell and table ownership reconcile with the content unit

passes →

Outputs

Token-to-cell relationsOverlap/containment evidenceUnassigned or ambiguous HOLDs

hands off to ORDER · CRITICAL · PDF · DGTL

fails →

HOLD

TABLE_TOKEN_ORPHANTABLE_TOKEN_DUPLICATETABLE_CELL_AMBIGUOUSTABLE_OWNER_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

Creating cells
Neighbour concatenation
Deciding which article owns the table

Explicitly forbidden

Concatenate neighboring cells
Duplicate a token across cells
Assign text to unsupported cells

Dependencies and position

Starts: After TABLE-PHYSICAL and CAP-RAW.
Previous step: 11 TABLE-PHYSICAL
Next step: 13 PAGE-ORDER / ORDER
Hands off to: ORDER, CRITICAL, PDF, DGTL

Exact inputs

Frozen table geometry
Exact CAP token polygons

Exact outputs

Token-to-cell relations
Overlap/containment evidence
Unassigned or ambiguous HOLDs

Performer and AI/ML boundary

Performer: Deterministic geometry assignment.
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

Each table token has exactly one cell/HOLD owner
Cell and table ownership reconcile with the content unit

HOLD and failure behaviour

Failure codes this step may emit:

TABLE_TOKEN_ORPHAN
TABLE_TOKEN_DUPLICATE
TABLE_CELL_AMBIGUOUS
TABLE_OWNER_CONFLICT

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

ORDER, CRITICAL, PDF, DGTL

Active tool

NO ACTIVE TOOL — HOLD. No implementation was invented to fill this gap.

Actual performer today: None.
Missing implementation: Deterministic assignment of CAP tokens to frozen physical cells with overlap evidence, or HOLD.
Consequence: Blocked upstream: token-to-cell assignment is undefined while step 11 produces no cells. The QA gate token-cell assignment at least 0.99 with zero neighbour concatenation cannot be evaluated.
Why it is on HOLD: Blocked by step 11 NO_ACTIVE_TOOL.

Recorded in tool/TOOL_STATUS.json.

Archived versions

No superseded versions recorded for this role.

Known limitations

No active tool, and blocked upstream: there are no cells to assign tokens to while step 11 is unimplemented.

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: TABLE-ASSIGN
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.