← E2T System V1 portal

04 — MAP-REFINE

Apply accepted refinement requests by re-measuring the original pixels.

ACTIVE Built and verified

4 tool files copied and hash-verified against the original.

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

Takes accepted refinement requests and re-measures the original pixels to produce revised regions, keeping the superseded proposals as lineage. Repair cycles are bounded so the loop cannot run away.

This role is allowed to

How it works

fed by 03 MAP-AI
Inputs
Accepted refinement requestOriginal pixels and MAP-GEO evidence
Deterministic Deterministic geometry/component tool.
  1. Recompute the duplicate-ownership report from the current state
  2. Select only the ranges still in conflict
  3. Re-call those ranges with the ownership-repair prompt
  4. Re-measure against the original pixels; keep superseded proposals as lineage
  5. Stop at the cycle limit — REFINE_LIMIT_REACHED rather than an unbounded loop
Must pass
  • Bounded refinement cycles
  • Every revised coordinate has pixel evidence
passes →
Outputs
Revised measured regionsParent/child lineage to replaced proposalsRemaining HOLDs
hands off to COMPLETENESS · ROLE · PIC · TABLE-PHYSICAL · ORDER
fails →
HOLD
REFINE_LIMIT_REACHEDREFINE_UNSUPPORTEDREFINE_STILL_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-AI requests or deterministic MAP conflicts.
Previous step
03 MAP-AI
Next step
05 VISIBLE-CONTENT COMPLETENESS
Hands off to
COMPLETENESS, ROLE, PIC, TABLE-PHYSICAL, ORDER

Exact inputs

Exact outputs

Performer and AI/ML boundary

Performer
Deterministic geometry/component tool.
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

COMPLETENESS, ROLE, PIC, TABLE-PHYSICAL, ORDER

Active tool

Status
Active tool
Run / inspect
python tools/repair_selected_ranges.py --ranges <list>
Input
accepted refinement request + duplicate report
Output
revised measured regions with parent/child lineage

Dependencies

Why this is the active version

The V114 README states this generation mechanically binds each rejected parsed candidate to a freshly recomputed duplicate report — the fix that closes the repair loop. Latest of the V105, V108, V111, V112, V113, V114 repair chain.

Copied files — source receipt

FileOriginal SHA-256BytesCopy
repair_selected_ranges.py ebd81650ba29dd94… 19,139 verified
resume_selected_repair.py f067020bcd9fe6d1… 13,271 verified
analyze_duplicate_aliases.py 81feb09a0310d425… 3,802 verified
prompts/detail_ownership_repair.txt 5229d8752a88a149… 1,263 verified

4 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
MAP-REFINE
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.