Prompt to Opus — Confirm Information Unit Current Position + Next Work — 2026-05-14

Mission

Confirm precisely where we are standing in the Information Unit / “miếng thông tin” / Text-as-Code workstream, what has already been completed, what remains, and what the next safe work item should be.

GPT’s current assessment is included below as a hypothesis. Opus must verify, correct, or reject it using KB evidence across sessions. Do not assume GPT is right. Do not assume the user’s roadmap is fully pending. Treat the user’s roadmap as the full target roadmap, then reconcile each bucket against reports/designs/handoffs.

Roles

User: strategic owner; decides unresolved or high-risk choices.
GPT / Hội đồng AI: coordinator and final authorization gate.
Opus: independent cross-session reviewer with broader context; confirms or rejects GPT’s assessment.
Claude Code CLI xhigh / Agent: drafts technical design from live PG/live code evidence or executes only after separate approval.

Hard boundaries for this Opus task

Review / confirmation only.
No execution.
No PG mutation.
No schema mutation.
No code/Nuxt change.
No vector/Qdrant mutation.
No Claude Code dispatch.
No TAC→IU migration.
No bulk migration.
No UI cutover.
No blind execution of old prompts.

Read first — pause and resume chain

A. Birth pause handoff / old stop point

Read or reconstruct from KB the pause context:

5C2 migration Đ35 was PAUSED because Birth System / khai sinh was not complete enough.
TAC→UI baseline PASS; UI reads TAC, not IU; UI cutover forbidden.
IU species/lớp existed: information_unit_atom / SPE-IUA / atom.
Authority vocab incomex_council seeded.
5C2 rev4 prompt existed but became reference-only.
Birth System Completion became mainline.

Core artifacts from that stop point:

knowledge/dev/laws/dieu44-trien-khai/design/p3d-birth-system-completion-architecture-design.md
knowledge/dev/laws/dieu44-trien-khai/prompts/p3d-birth-system-completion-readonly-inventory-prompt-DRAFT.md
knowledge/dev/laws/dieu44-trien-khai/design/p3d-birth-system-completion-roadmap.md
knowledge/dev/laws/dieu44-trien-khai/reports/p3d-birth-system-completion-design-and-inventory-prompt-report.md

B. Birth completion / current resume point

knowledge/dev/laws/dieu44-trien-khai/handoffs/handoff-p3d-pack1-return-to-phase5c2-after-birth-complete-2026-05-14.md
knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-final-review-birth-system-complete-authorize-phase5c2-resume-2026-05-14.md
knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-session-start-confirmation-phase5c2-resume-handoff-read-2026-05-14.md

Read second — Information Unit / Text-as-Code status docs

Read these before answering:

knowledge/dev/laws/dieu44-trien-khai/ssot/p3d-iu-text-as-code-completed-state-and-remaining-work-2026-05-10.md
knowledge/dev/laws/dieu44-trien-khai/handoffs/handoff-p3d-information-unit-text-as-code-resume-after-nuxt-notification-2026-05-10.md
knowledge/dev/laws/dieu44-trien-khai/requirements/p3d-information-unit-text-as-code-requirements-spec.md
knowledge/dev/laws/dieu44-trien-khai/reviews/iu0-pack1-closure-pack2-readiness-2026-05-04.md
knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-iu0-pack2-readiness-and-session-resume-2026-05-04.md
knowledge/dev/laws/dieu44-trien-khai/reviews/handoff-opus-new-session-iu0-pack2a-core-pass-next-2026-05-04.md
knowledge/dev/laws/dieu44-trien-khai/design/19-iu0-pack2b-pilot-crud-and-birth-fire-execution-pack.md
knowledge/dev/laws/dieu44-trien-khai/handoffs/handoff-p3d-pack1-return-to-phase5c2-after-birth-complete-2026-05-14.md

Also search KB for newer documents superseding any of these, especially:

Pack 2A closure
QT-003R
F6 birth path
Pack 2B
IU CRUD birth fire
information_unit event_domain
text-as-code completed state
vector search reliability

User roadmap to reconcile

Do not discard this roadmap. Treat it as the full macro-plan to make “miếng thông tin” usable, then mark each item as DONE / PARTIAL / PENDING / SUPERSEDED / NEEDS_REVIEW.

1. Run G-Pilot-1 READ-ONLY simulation using prompt 08d.
2. Read simulation report; decide boundary slice, MUP gaps, token saving.
3. If PASS: write G-Pilot-2 Decision Pack for minimal writable pilot.
4. User/GPT approve small writable pilot.
5. Choose 1–2 first docs: IU-0 and P38-XC.
6. Decide temporary unit_kind, e.g. design_doc_section.
7. Decide MUP pilot: real vs placeholder/warn fields.
8. Create pilot data for initial slices, not scale whole system.
9. Test CRUD hot path via PG, no vector yet.
10. Test versioning: edit slice creates new version, no full file rewrite.
11. Test canonical address resolution: IU-0.§x, P38-XC.§x.
12. Test profile JSONB required fields, no invented fields.
13. Test minimal edges: document contains slice / slice belongs_to document.
14. Test slice edit workflow: Agent reads 1 slice, edits 1 slice, returns diff.
15. Measure token/time saving vs full-file edit.
16. Review drift: slice edit must not break cross-reference.
17. If pilot PASS: expand to 3–5 docs in agreed scope.
18. Design/prepare vector outbox for IU, still no legacy vector mutation.
19. Create IU vector collection when approved.
20. Test delayed vector 120s on IU-only collection.
21. Test duplicate KB draft + IU final precedence by freshness matrix.
22. Decide search adapter Phase 2 for KB + IU search.
23. Write pilot postmortem.
24. Update IU-0 docs from pilot findings.
25. Define minimum production-use rule: which work may use IU, which not yet.
26. Begin tiny real workflow use with rollback.
27. After stable: return to Đ38/TAC pipeline and use IU as foundation.

GPT current assessment — Opus must verify or correct

GPT’s current hypothesis:

A. The user roadmap is valid as a macro-roadmap, but some items are already complete.
B. G-Pilot-1 through G-Pilot-5 appear complete.
C. IU Pack 1 minimal PG schema foundation appears complete and GPT-reviewed PASS.
D. Pack 2 readiness appears PASS.
E. Pack 2A governance registration appears core PASS.
F. The current historical point before the Birth detour may have been: after Pack 2A core PASS, before Pack 2B, with F6 birth path for IU data rows blocking Pack 2B.
G. Later, Birth System Completion was completed and GPT authorized Phase 5C2 resume, but execution remains gated.
H. Therefore, the next safe action is probably not to rerun G-Pilot-1. It is to produce a fresh current-position/readiness decision after Birth completion, then ask Claude Code CLI xhigh / Agent for a live PG evidence-based design for the next unfinished IU step.
I. Candidate next unfinished step may be one of:
   1. F6 / Pack 2B birth path + minimal CRUD/birth-fire readiness for real IU data rows; or
   2. Phase 5C2 TAC→information_unit resume plan; or
   3. a combined coordination plan sequencing both without execution.
J. No vector implementation should start now; vector remains deferred unless a read-only audit finds an urgent issue.

Opus must explicitly say which of A–J are correct, wrong, incomplete, or stale.

Required checks

1. Completed work confirmation

For each item, confirm with evidence path:

IU-0 baseline 07/07b/07c.
G-Pilot-1 simulation.
G-Pilot-2 decision/tracking.
G-Pilot-3/G-Pilot-4 writable slice tests.
G-Pilot-5 closure/postmortem status.
Pack 1 schema foundation.
Pack 2 readiness.
Pack 2A governance registration.
Pack 2A closure/QT-003R status.
F6 birth path status.
Pack 2B CRUD/birth-fire status.
Text-as-Code requirements/spec status.
TAC→UI baseline preservation.
Birth System completion.
Phase 5C2 resume authorization and gates.

2. Remaining work classification

Classify remaining work into:

MUST_BEFORE_IU_DATA_ROWS
MUST_BEFORE_PACK2B
MUST_BEFORE_PHASE5C2_EXECUTION
CAN_RUN_IN_PARALLEL_AS_DESIGN_ONLY
DEFER_UNTIL_AFTER_MINIMAL_CRUD
DEFER_UNTIL_AFTER_IU_EVENTS
DEFER_VECTOR

3. Vector/search alert check

User asked to be informed immediately if vector seems inefficient.

Check existing reports/designs and classify:

vector_efficiency_alert=NONE|WATCH|ALERT
vector_issue_type=ranking|freshness|orphan_ghost|duplication|latency|payload_schema|unknown|none
legacy_vector_safe_to_leave_untouched=true|false|unknown
iu_vector_should_remain_deferred=true|false
must_notify_user_now=true|false

If ALERT, recommend read-only audit first; no vector mutation.

4. Exact next Agent/Claude Code task

Recommend one and only one next Agent/Claude Code CLI xhigh task.

It should be design/read-only unless Opus proves a reviewed execution gate already exists and is still valid after Birth completion.

Candidate wording to evaluate:

Draft Current Position + Next-Work Decision Pack for Information Unit/Text-as-Code after Birth completion, using live PG/read-only evidence. Reconcile IU Pack 2B/F6 and Phase 5C2 resume; no execution, no vector, no UI cutover, no bulk migration.

If Opus recommends a different next task, explain why.

Required output format

Return exactly:

opus_iu_position_crosscheck_status=PASS|PARTIAL|BLOCKED
roadmap_reconciled=true|false
gpt_assessment_A_to_J=<correct/wrong/incomplete per letter>
current_position=<one sentence>
last_confirmed_completed_gate=<gate/doc>
first_unfinished_gate=<gate/doc>
pack2b_allowed=false|true|unknown
phase5c2_resume_allowed=true|false|unknown
phase5c2_execution_allowed=false
bulk_migration_allowed=false
ui_cutover_allowed=false
vector_efficiency_alert=NONE|WATCH|ALERT
must_notify_user_now=true|false
next_agent_task=<one clear task>
parallel_design_tracks_allowed=yes|no|unknown
required_user_decisions=<list>
conflicts_or_stale_assumptions=<list>
recommended_next_action_for_GPT=<one clear action>

Then provide a concise rationale with evidence paths.

Important style

Be strict. If KB evidence conflicts, mark PARTIAL and list conflict. If a report is missing or superseded, say so. Do not fill gaps from memory. If not certainly right, classify as UNKNOWN and recommend read-only verification.