Incomex AI Portal
KB-44B8 rev 3

Prompt to Opus — Cross-check Information Unit / Text-as-Code Resume Context — 2026-05-14

10 min read Revision 3
opuscrosscheckinformation-unittext-as-codephase5c2resumecontext2026-05-14

Prompt to Opus — Cross-check Information Unit / Text-as-Code Resume Context — 2026-05-14

Mission

Cross-check the current context before GPT resumes coordination of the Information Unit / Text-as-Code workstream.

The user’s goal is to complete the “miếng thông tin” foundation according to the best Text-as-Code standard, but also according to Incomex’s own approved architecture. We must not resume from a stale roadmap or execute old prompts blindly.

Role split

  • User: strategic owner; decides questions that GPT/Opus cannot decide.
  • GPT / Hội đồng AI: coordinator and final authorization gate.
  • Opus: independent constitutional/design reviewer; cross-checks status, conflicts, laws, and risks.
  • Claude Code CLI xhigh / Agent: drafts technical designs from live PG + live code evidence; executes only when separately authorized.

Read first

Current handoff after Birth System completion

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

Information Unit / Text-as-Code status

  1. knowledge/dev/laws/dieu44-trien-khai/reports/iu0-pilot-round1-closure-decision-pack.md
  2. knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-iu0-pack1-execution-report-2026-05-04.md
  3. knowledge/dev/laws/dieu44-trien-khai/design/19-iu0-pack2b-pilot-crud-and-birth-fire-execution-pack.md
  4. knowledge/dev/laws/dieu44-trien-khai/roadmaps/p3d-information-unit-text-as-code-roadmap-nom-na-2026-05-10.md
  5. knowledge/dev/laws/dieu44-trien-khai/design/p3d-pack1-iu-canonical-contract-and-tac-iu-reconciliation-design.md
  6. knowledge/dev/laws/dieu44-trien-khai/design/p3d-pack1-phase5-tac-to-iu-migration-design.md
  7. knowledge/dev/laws/dieu44-trien-khai/design/p3d-phase5c2-impact-addendum-after-multidimensional-design.md

Laws / principles

  1. knowledge/dev/laws/constitution.md
  2. knowledge/dev/laws/dieu44-trien-khai/principles/p3d-terminology-and-multidimensional-entity-db-principle-2026-05-12.md

Context to verify

Important: do not dismiss or truncate the user's roadmap. Treat it as the full target roadmap for Information Unit / Text-as-Code. Some items in that roadmap may already be completed; Opus must reconcile the roadmap against KB reports/designs rather than assume all steps are pending.

The user provided the older pause handoff for the exact moment Phase 5C2 stopped and Birth System Completion became mainline. That pause handoff must be treated as the historical starting point:

5C2 migration Đ35 PAUSED.
Reason: complete Birth System / khai sinh before continuing TAC→IU.
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 self-contained prompt exists but is reference-only, not active execution target.
Birth completion artifacts to read first:
1. design/p3d-birth-system-completion-architecture-design.md
2. prompts/p3d-birth-system-completion-readonly-inventory-prompt-DRAFT.md
3. design/p3d-birth-system-completion-roadmap.md
4. reports/p3d-birth-system-completion-design-and-inventory-prompt-report.md
phase5c2_migration_allowed=false
ui_cutover_allowed=false
agent_dispatch_allowed=false except GPT/User-approved read-only inventory
birth_system_completion_mainline=true

Then verify the subsequent timeline from KB. Current KB evidence appears to show:

  • The four Birth System Completion artifacts existed and were reviewed.
  • Birth inventory, B2/B3, ELD, scheduler/full-scan, B2 Contract Rev3, and final reviews later completed.
  • G-Pilot-1 simulation appears completed.
  • G-Pilot-2 tracking appears completed.
  • G-Pilot-3 and G-Pilot-4 writable slice edits appear PASS.
  • G-Pilot-5 closure says Round 1 COMPLETE.
  • Pack 1 minimum IU schema foundation appears executed and GPT-reviewed PASS.
  • Birth System completion later became a blocker-clearing infrastructure milestone.

Opus must verify whether this interpretation is correct, identify any stale handoff/roadmap assumptions, and state the exact safe resume point.

Vector/search efficiency warning check

User instruction: if there is any sign that vector/search is inefficient or unreliable, report immediately.

Opus must specifically inspect and classify vector/search evidence, including at minimum:

  • knowledge/dev/laws/dieu38-trien-khai/reports/legacy-vector-stabilization-outline-v3.md
  • knowledge/current-state/reports/qdrant-full-audit
  • knowledge/dev/laws/dieu44-trien-khai/reports/20a-20b-p0-search-vector-hygiene-inspection-report.md
  • knowledge/dev/laws/dieu44-trien-khai/design/p3d-vector-search-unified-contract-ssot.md
  • knowledge/dev/laws/dieu44-trien-khai/reports/p3d-vector-search-hybrid-path-title-boost-design-report.md
  • knowledge/dev/laws/dieu44-trien-khai/reviews/gpt-review-p3d-vector-search-freshness-audit-and-stop-pack1-2026-05-11.md
  • knowledge/dev/laws/dieu44-trien-khai/reports/p3d-vector-search-reliability-hardening-implementation-report.md

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

Do not propose vector mutation unless separately reviewed. If ALERT, recommend a read-only verification/audit first.

Things to confirm or refute

Return evidence-based answers for each item:

  1. Is the user’s roadmap step 1 still pending, or already completed by 08d + simulation report?
  2. Is IU Pilot Round 1 truly complete? If yes, summarize gates G-Pilot-1 through G-Pilot-5.
  3. Is IU Pack 1 truly complete? If yes, summarize what was created and what explicitly was not created.
  4. What is the first unfinished IU/Text-as-Code step now?
  5. Is 19-iu0-pack2b-pilot-crud-and-birth-fire-execution-pack.md still the correct next design reference, or has a newer Pack 2/readiness/handoff superseded it?
  6. How does the newly completed Birth System affect IU Pack 2 / TAC→IU / Phase 5C2?
  7. Does Phase 5C2 resume need to wait for IU Pack 2 CRUD/birth pilot, or should Phase 5C2 resume plan proceed in parallel as design-only?
  8. Is TAC→UI baseline still preserved and UI cutover still forbidden?
  9. Which old docs/prompts are reference-only and must not be executed blindly?
  10. Which exact next artifact should Claude Code CLI xhigh / Agent draft from live PG evidence?

Constitutional/design checks

Check against:

  • Constitution NT9: if not certainly right, stop and verify.
  • NT13: PG First · PG Native · PG Driven.
  • NT15: design before implementation.
  • Birth System B2 Contract Rev3: birth ≠ enrichment ≠ health.
  • P3D multidimensional principle: no hardcoded species/lớp/count gates; preserve Entity Living DB hooks.
  • Text-as-Code target: unitization, identity, versioning, registry, schema validation, graph/dependencies, health checks, tooling, governance, then diff/merge/PR/test/build/release/semantic lint/vector.

Hard boundaries for this Opus task

  • Review/cross-check only.
  • No execution.
  • No PG mutation.
  • No schema mutation.
  • No Claude Code dispatch.
  • No bulk migration.
  • No UI cutover.
  • No blind execution of old 08d/09b/19/5C2 prompts.
  • No vector/outbox work unless only classified as future planning.

Required output

Return exactly this structure:

opus_context_crosscheck_status=PASS|PARTIAL|BLOCKED
stale_roadmap_detected=true|false
user_roadmap_step1_status=PENDING|COMPLETED|CONFLICTING|UNKNOWN
iu_round1_complete_confirmed=true|false
iu_pack1_complete_confirmed=true|false
birth_system_complete_confirmed=true|false
phase5c2_resume_allowed_confirmed=true|false
phase5c2_execution_allowed=false
bulk_migration_allowed=false
ui_cutover_allowed=false
next_unfinished_workstream=<one clear name>
recommended_agent_task=<one clear task for Claude Code CLI xhigh / Agent>
parallel_tracks_allowed=<yes/no + explanation>
conflicts_or_stale_assumptions=<list>
required_user_decisions=<list>
recommended_next_action=<one clear action for GPT>

Also provide a concise rationale with document paths cited inside the response.

Expected likely answer, to verify not assume

Likely, but Opus must verify:

  • The roadmap provided by user is partly stale through at least Round 1 and Pack 1.
  • Current next step is not G-Pilot-1; it is a resume/readiness design step after Birth completion, likely one of:
    • Pack 2B live-schema CRUD + birth-fire read-only/preflight plan, or
    • Phase 5C2 TAC→information_unit resume plan from live PG evidence, depending on whether these tracks are sequential or can proceed in parallel.
  • No execution is allowed until GPT/User review the new resume/readiness plan.
Back to Knowledge Hub knowledge/dev/laws/dieu44-trien-khai/prompts/opus-crosscheck-information-unit-text-as-code-resume-context-2026-05-14.md