08 — Next Macro Prompts (8, paste-ready, open-goal) (2026-05-28)
08 — Next Macro Prompts (8, paste-ready, open-goal)
Each prompt is self-contained after a context clear. Host = contabo VPS; read via query_pg role context_pack_readonly db directus; apply (if safe) via SSH docker exec -i postgres psql -U workflow_admin -d directus. All carry Hard Gate 0, forbidden lists, and completion pressure. They do not over-prescribe method.
Prompt 1 — IU_LIMITED_PRODUCTION_PILOT_OPERATING_PROTOCOL_ADOPTION_300000X
Adopt and exercise the IU limited-production pilot operating protocol (…/iu-limited-pilot-cr-kg-design-recon-authority-megabundle-2026-05-28/01-iu-limited-production-pilot-operating-protocol.md). Run Hard Gate 0 (confirm directus/postgres/172.19.0.3/role; fn_iu_gate_verify_closed() all_safe=true; snapshot IU counts). Then execute a small number of fully-governed create→edit→enact→split→merge→retire cycles on test-tagged, non-load-bearing IUs only, using fn_iu_test_review_decision_create and the §5 bounded gate protocol. Produce a session evidence package (gate verify before/after, counts before/after, exact SQL, review_decision_id, watchdog result) and a pilot health report. Objective: prove the protocol is operable and safe end-to-end. Forbidden: never-flip flips, production review_decision self-mint, P-pub block_all, Qdrant/Directus/Nuxt writes, hard-delete cleanup. PASS only if cycles complete, zero unexplained drift, DLQ stays 0, all gated ops used the protocol. You own completion.
Prompt 2 — IU_CANDIDATE_REGISTRY_BUILD_DESIGN_400000X
Design (design-first, no implementation) the 6 absent Candidate Registries for the 4 Mothers: field_registry, input_form_registry, output_table_registry, dot_function_registry, task_template_registry, tier_registry (all confirmed ABSENT 2026-05-28). For each: owner law (Đ28/35/36/37/7), exact column design, the existing substrate it must EXTEND not duplicate (collection_registry 168, collection_field_standards, table_registry 21, dot_iu_command_catalog 52, workflows/workflow_steps, governance_registry, birth_registry), reuse-vs-create per field, and the MOIT/MOUT/MOT/MOW mapping. Explicitly recommend promoting dot_iu_command_catalog to satisfy dot_function_registry rather than a parallel SoT. Objective: a buildable, no-duplication CR design. Forbidden: creating tables, 4 Mothers implementation, duplicating existing registries. Acceptance: each registry has owner law + column design + reuse decision + Mother mapping. You own completion.
Prompt 3 — IU_KG_RELATIONSHIP_ENRICHMENT_LIVE_APPLY_OR_DESIGN_PATCH_250000X
Advance IU KG enrichment per …/03-iu-kg-relationship-enrichment-readiness.md. Live truth: iu_relation (60, UUID, all contains) lacks provenance/confidence/evidence/assertion_mode/negative_knowledge/override/explanation/feedback; universal_edges (2199, integer-keyed) HAS provenance/confidence/valid_time but excludes UUID IU. Either (a) design+safely apply the additive nullable enrichment columns to iu_relation (Phase 1) with DRY-RUN rollback + durability proof in a fresh connection, OR (b) produce the full design patch if apply is judged unsafe. Add the relation_type vocab toward the 8 information-atom rules (IDENTITY, BELONGS_TO, CONTAINS, DEPENDS_ON, USED_BY, TRANSITIVE, PEERS, SIMILAR). Forbidden: migrating IU into universal_edges, any UUID↔integer mapping store, vector_sync_enabled=true, hidden 2nd graph SoT, retro-blocking the 60 legacy rows. Acceptance: enrich-in-place + read-only projection design, no hidden SoT. You own completion.
Prompt 4 — MASTER_DESIGN_LIVE_INVENTORY_RECONCILIATION_PATCH_200000X
Apply the doc-only reconciliation patches from …/04-master-design-rev5-live-inventory-reconciliation.md to the design dir knowledge/dev/design/v0.6-iu-4mothers-event-foundation-rev2/ (docs 00,03,04,07,10). Use patch_document (exact old_str→new_str replay; serialize same-doc patches). Focus on the correctness-hazard deltas R7 (KG two-graph reality), R8 (P-pub warn-only), R9 (CR is paper, reuse map), R10 (factories not registered, human-org-role missing). Do NOT over-claim production readiness. Forbidden: code/schema change, claiming P-pub/CR/factories done. Acceptance: each R-row patched or explicitly deferred with reason; design no longer says "KG paper / P-pub enforced / CR planned". You own completion.
Prompt 5 — IU_PPUB_BIRTH_GATE_STAGED_PROMOTION_300000X
Execute the next safe P-pub stage per …/05-ppub-promotion-authority-refinement.md. Live: 133/219 IUs lack an authority publication; mode key iu_create.ppub.enforcement_mode does not exist; vocab auth=1/type=2; fn_iu_create has no authority_ref param. Create the iu_create.ppub.enforcement_mode config (default warn), extend vocab as council-approved, then advance to block_new ONLY (legacy 133 untouched) with an in-tx BEGIN..ROLLBACK test proving new-without-authority blocks and legacy-edit still works. Do NOT reach block_all. Require a council approval_id for the stage change. Forbidden: block_all before backfill=0, direct UPDATE information_unit for backfill, silent vocab expansion, breaking legacy. Acceptance: mode=block_new committed safely OR precise blocker; legacy unbroken; rollback documented. You own completion.
Prompt 6 — IU_PRODUCTION_REVIEW_DECISION_GOVERNANCE_PATH_300000X
Design (and only if obviously safe, additively build) the production cutter_governance.review_decision builder per …/06-production-review-decision-governance-authority.md. Re-introspect cutter_governance as workflow_admin (privilege-walled from the RO role). The production builder must require a named human/council/sovereign principal, a real manifest_envelope+manifest_unit_block binding, a constrained verdict vocab, and cross-sign (≥2 authorities) for high-risk verdicts. Keep the agent path test-only (fn_iu_test_review_decision_create). Forbidden: agent self-mint of production decisions, cross_signed=true without 2 authorities, synthetic manifests in production, allow_no_review_decision=true. Acceptance: production builder contract specified (and safely built or precisely deferred); test/prod boundary enforced. You own completion.
Prompt 7 — HUMAN_ORG_ROLE_PERMISSION_LAW_BRIEF_OR_DRAFT_250000X
Draft the human-org-role / permission law per …/07-human-org-role-permission-law-brief.md. Define human role subjects (staff, department_lead, super_admin) with specialty/company/domain scoping and a rights-×-scope matrix (view/edit/approve/delegate/escalate), explicitly orthogonal to the Đ37 agency/factory model. Specify the law-role → Directus-policy mapping and the tie to Đ32 approval (a dept_lead as in-scope production reviewer) and Đ28 templates (who sees which surface). Forbidden: enacting the law, creating human rows in governance_registry, Directus/Nuxt change. Acceptance: law/draft with subjects + rights matrix + Directus/Đ32/Đ28 bindings + blocking analysis (blocks MOW UI, not IU pilot). You own completion.
Prompt 8 — FOUR_MOTHERS_ENTRY_GATE_DECISION_PACK_300000X
Produce the 4 Mothers entry-gate decision pack. Re-verify the four blockers live: (1) Candidate Registry built (6 tables — currently ABSENT), (2) P-pub at block_new + backfill complete (currently warn, 133 unauthorized), (3) production review_decision path live (currently test-only), (4) human-org-role law enacted (currently absent), plus factory registration in governance_registry (currently 0 factory rows). For each blocker: current state, exact exit criteria, owning macro prompt, dependency order. Decide GO/NO-GO for 4 Mothers entry and, if NO-GO, the critical path. Forbidden: any 4 Mothers implementation, mutation. Acceptance: per-blocker exit criteria + dependency-ordered critical path + explicit GO/NO-GO. You own completion.
Recommended next sequence
Parallel now: Prompt 1 (adopt pilot) ∥ Prompt 2 (CR design). Then Prompt 5 (P-pub block_new) ∥ Prompt 3 (KG enrich) ∥ Prompt 4 (design patch). Then Prompt 6 (prod review_decision) ∥ Prompt 7 (human-org-role law). Finally Prompt 8 (4 Mothers entry gate) once 1–7 land.