GPT Direction — Pack 2 Readiness Next Step

Date: 2026-05-04 Context: Pack 1 CLOSED — PASS. User requested larger work packages, less copy/paste overhead.

Direction to Opus

Move in larger packages. Next deliverable is a single Pack 2 Readiness + Scope Decision Pack, not multiple small prompts.

Inputs to read

1. knowledge/dev/laws/dieu44-trien-khai/reviews/iu0-pack1-closure-pack2-readiness-2026-05-04.md
2. knowledge/dev/laws/dieu44-trien-khai/reports/iu0-pack1-execution-report.md
3. knowledge/dev/laws/dieu44-trien-khai/design/09a-iu0-pack1-vocab-schema-ddl-design.md
4. knowledge/dev/laws/dieu44-trien-khai/design/09-iu0-minimal-implementation-planning-pack.md

Output

Create and upload: knowledge/dev/laws/dieu44-trien-khai/design/10-iu0-pack2-readiness-and-scope-decision-pack.md

Required sections:

1. Pack 1 final state: live objects, triggers, test data = 0, hard stop remains active.
2. Follow-up F1–F3: trigger governance, 09a doc sync with runtime dot_config key/value/updated_at, collection_registry readiness.
3. Pack 2 scope options:
   • A: Governance cleanup only.
   • B: Minimal CRUD/API for information_unit, no vector.
   • C: Outbox/vector prep, no Qdrant collection.
4. Recommendation: do Option A first, then decide Option B. Do not jump into vector/outbox.
5. Decision request: User/GPT selects A/B/C or defer.

Optional allowed patch

Opus may patch 09a once to align dot_config column names with runtime (key, value, updated_at). Documentation only; no DDL.

Prohibitions

No Claude Code dispatch. No DDL. No outbox. No Qdrant collection. No production units. No Directus/collection_registry execution. No Pack 2 execution.