← E2T System V1 portal

11 — TABLE-PHYSICAL

Measure only table structure physically supported by page pixels.

NO TOOL Nothing implements this step

A table/not-table flag is not table geometry. No cell boundaries exist, so the QA gate strict physical-cell F1 at least 0.95 cannot be evaluated and no table can be faithfully reconstructed.

Why it is held: Never implemented as physical measurement. An earlier inventory pass over-credited the boolean flag as a partial implementation; direct inspection of the schema shows it is not.

Deterministic Page model 0 archived step 11 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

Intended to measure real table geometry from the pixels — bbox, rules, intersections, rows, columns, cell boundaries, border widths and fills — accepting only physically supported cells and holding ambiguous ones.

This role is allowed to

How it works

fed by 04 MAP-REFINE
Inputs
Original pixelsMAP table candidatesSTYLE rule/fill evidence
Deterministic Deterministic grid/rule detector; table-layout ML may nominate only.

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 accepted boundary has physical support
  • Topology is internally consistent
passes →
Outputs
Table bbox, rulings and intersectionsRows, columns, cells, borders, fills and support evidence
hands off to TABLE-ASSIGN · PROTECTION · PDF · DGTL
fails →
HOLD
TABLE_UNSUPPORTEDTABLE_TOPOLOGY_CONFLICTTABLE_BOUNDARY_AMBIGUOUS

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 MAP table envelopes.
Previous step
10 PIC
Next step
12 TABLE-ASSIGN
Hands off to
TABLE-ASSIGN, PROTECTION, PDF, DGTL

Exact inputs

Exact outputs

Performer and AI/ML boundary

Performer
Deterministic grid/rule detector; table-layout ML may nominate only.
Class
Deterministic
AI boundary
Proposal-only if used.

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

TABLE-ASSIGN, PROTECTION, PDF, DGTL

Active tool

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

Actual performer today
None. The MAP-AI detail schema carries only a boolean `x` marking a group as table or not-table.
Missing implementation
A deterministic grid detector measuring table bbox, rows, columns, cell boundaries, intersections, border widths and fills from original pixels.
Consequence
A table/not-table flag is not table geometry. No cell boundaries exist, so the QA gate strict physical-cell F1 at least 0.95 cannot be evaluated and no table can be faithfully reconstructed.
Why it is on HOLD
Never implemented as physical measurement. An earlier inventory pass over-credited the boolean flag as a partial implementation; direct inspection of the schema shows it is not.

Recorded in tool/TOOL_STATUS.json.

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
TABLE-PHYSICAL
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.