Session Handoff — Miếng thông tin core roadmap and next macro

Date: 2026-05-21

Executive summary

The main objective is no longer to keep expanding readiness packages for the cutter. The main objective is to complete the information-unit system as quickly as possible.

The auto-cut pipeline is technically close to approval-ready. Remaining blockers are mostly sovereign/operator: SG approval, execution_enabled flip authority, BACKUP_GPG_FPR, and first production run authorization. Further readiness packaging for O8/O9/O10/O11 should stop unless it directly enables a production run.

The correct roadmap now shifts to the core information-unit foundation:

1. PG-native IU relation and two-way trigger model.
2. Parent-child multi-level IU structure.
3. Add/split/merge/delete structure operations.
4. Text-as-code tooling after the core structure is in place.

Key lesson from the session

The user repeatedly corrected the orchestration style:

• Main priority: finish the information-unit system quickly.
• Time target is secondary.
• The previous orchestration was too fragmented and caused overhead.
• Tasks should be open-goal macro tasks, not small step-by-step packages.
• Use live survey before action.
• State the target outcome clearly.
• State PASS/BLOCKED conditions clearly.
• State forbidden actions clearly.
• Give enough SSOT context.
• Allow the agent to self-fix technical issues within scope.
• Gate only for production DB writes, CUT execution, VERIFY execution, deploy/restart, merge/push/tag, source/schema mutation.

State of auto-cut / orchestrator

Completed:

• Constitution was cut into 60 ICX-CONST IUs and enacted.
• Governance recording and write verify done.
• v0.6 orchestrator exists and was deployed on VPS.
• Mode.LIVE write wiring implemented.
• Real DB rollback-only proof passed.
• Generic target/small-document dry-run path added.
• Agent sandbox scaffold exists.

Remaining blockers for first automated production run:

• SG approval for first orchestrator-managed production run.
• Authority to flip execution_enabled for approved run.
• BACKUP_GPG_FPR key/operator provisioning.

Conclusion: auto-cut should be held until approval/operator prerequisites are ready. Do not spend more cycles on readiness packages unless they directly lead to the approved run.

Current roadmap status

Based on the roadmap file and session analysis:

• Auto-cut production: 90–95%, waiting on sovereign/operator blockers.
• PG-native IU relation and trigger model: design/brief ready, implementation not done.
• Parent-child multi-level: brief ready, implementation not done.
• Add/split/merge/delete: not implemented.
• Text-as-code tooling: planning only, not implemented.

Parallel agent assessment

• Claude Code: main/core implementation, production-gated work, complex source changes.
• Codex: good for code/test/survey/technical drafting; can do non-production implementation and tests.
• Gemini CLI: usable only as reviewer/critic for long documents; no KB/DB/code authority.
• Antigravity: paused; not reliable enough for KB/SSOT or core planning.

Next recommended macro

Name: IU_CORE_PG_NATIVE_PARENT_CHILD_STRUCTURE_OPS_AUTHORING

Effort: xhigh

Required start host: MacBook/dev host because source repo work, DDL files, tests, and commit are expected.

VPS role: read-only live schema survey and optional non-mutating proof only.

Goal: move the information-unit core forward, not the cutter readiness packages.

Scope:

1. Live schema survey: information_unit, unit_version, iu_lifecycle_log, universal_edges, event_outbox/event_pending if present, cutter_governance, dot_config.
2. Read Codex briefs:
   • v0.6-iu-pg-native-trigger-model-survey-design
   • v0.6-iu-pg-native-ddl-authoring-brief
   • v0.6-iu-parent-child-split-merge-brief
3. Author DDL migration package and rollback package for:
   • iu_sql_link
   • iu_sql_event_route
   • iu_outbound_route
   • parent-child constraints/indexes/checks
   • structure operation / lineage tables if needed
4. Author parent-child multi-level model.
5. Author add/split/merge/delete operation contract.
6. Author PG-native two-way trigger model.
7. Add tests/static validation.
8. Commit if tests pass.
9. Produce production execution readiness package for later approval.

Forbidden:

• No production DB write.
• No production DDL execution.
• No deploy/restart.
• No execution_enabled flip.
• No hard delete default.
• No secret logging.
• No active VPS runtime source mutation.
• Do not treat proposals as approved.
• No fake PASS.

Expected result:

A. IU_CORE_STRUCTURE_OPS_AUTHORING_PASS B. BLOCKED_WITH_EXACT_IU_CORE_GAP C. PARTIAL_WITH_ROLLBACK_OR_CLEANUP_REQUIRED

Suggested prompt for next session

Use the prompt already drafted in the chat under “Prompt điều hành tiếp theo” for IU_CORE_PG_NATIVE_PARENT_CHILD_STRUCTURE_OPS_AUTHORING. It begins with:

“Đây là phiên Claude Code/Codex mới. Effort: xhigh. HOST BẮT BUỘC: Bắt đầu trên MacBook/dev host...”

Final instruction for next assistant

Do not continue assigning small O8/O9/O10/O11 readiness tasks. The next main action should be the IU core implementation macro, unless the user explicitly wants to perform the first automated production run approval/operator steps first.