# AGENT-PROMPT-v5-P1-1b — Piece D mapping amendment: Option A approval

**Date:** 2026-08-07
**Follows:** `docs/AGENT-PROMPT-v5-P1-1b-piece-d-mapping-approval.md`,
`docs/p1-1b-status.md` ("2026-08-07 Piece D ordered instruction 3 — measured mapping
collision, clean stop, Miguel decision required"), and `docs/PROJECT-STATE.md`
**Authority:** Miguel
**Stage:** governed records only

## Decision: Option A approved; D-M1 closed

Miguel's exact approval sentence, recorded verbatim:

> Aprovo a opção A e o mapping Piece D revisto

This explicitly selects **Option A** exactly as published in the governing stop and clarified by
Miguel. It amends only the Piece D item-2/item-3 mapping collision and closes D-M1. The binding
amended contract is:

1. Physical `ordinal_position` / PostgreSQL `pg_attribute.attnum` remains dynamically captured,
   deterministic, and reported as a separate diagnostic artifact.
2. Physical ordinal/`attnum` is excluded **only** from the S1/S3 logical-equality tuple.
3. Every other governed logical catalog property remains in the complete, dynamically enumerated
   equality oracle. Curated table, function, or role lists and lossy count substitution remain
   forbidden.
4. S0/S2 remains the exact P1-1a restoration proof, including physical metadata where applicable.
   S1/S3 compares complete logical state. Physical diagnostics for both S1 and S3 are emitted, and
   any physical drift remains visible rather than being normalized away.
5. The measured S1=`30` / S3=`32` `DOCFLG.ImportEvidenceRowId` `attnum` result remains historical
   empirical evidence. It is not a required universal allocator constant unless the test observes
   it fresh in that run.
6. Item 2's determinism test must prove both the logical snapshot and the physical diagnostic are
   deterministic at a fixed state before either artifact is trusted by item 3.

All other Piece D mapping items remain exactly as previously approved. This amendment authorizes no
migration, DDL, `src/`, Designer, ModelSnapshot, baseline, pin, O8, O9, O10, item 5, Scope 1, or O5
decision change. In particular, item 5's real-population proof remains deferred to Scope 1 exactly
as previously approved, and Scope 1 remains unauthorized until Piece D receives a fresh independent
**Accept**.

## Ordered execution authority

Ordered instruction 3 is re-authorized **only after** the records commit containing exactly this
approval document, `docs/p1-1b-status.md`, and `docs/PROJECT-STATE.md` is independently reviewed,
committed, and pushed. TDD must then start fresh from that pushed tip and implement only the amended
mapping above together with the otherwise-unchanged approved Piece D mapping.

This records stage does not itself authorize starting TDD, running a database, build, or test, or
touching any implementation path. It does not authorize ordered instruction 4 separately; after a
candidate is produced under ordered instruction 3, the existing requirement for a fresh independent
integration-focused Accept/Reject review remains in force.

## Records instruction

Record this approval by prepending the explicit amendment to `docs/p1-1b-status.md` while preserving
the published stop record intact as historical evidence, and update every current-facing Piece D
location in `docs/PROJECT-STATE.md` in the same records commit. The exact versioned path set is:

1. `docs/AGENT-PROMPT-v5-P1-1b-piece-d-mapping-amendment-a-approval.md`
2. `docs/p1-1b-status.md`
3. `docs/PROJECT-STATE.md`

No other versioned path belongs to this records stage.