110000x · 09 — Short Runbook

No macro-length prompt per file. These five lines are the entire operator UX.

The five short commands

MARK file <source_ref> theo quy trình operational-cut-workflow, lưu vào No-Vector Staging Zone
VERIFY MARK staging_id <id>
CUT staging_id <id>, output IU corpus, verify reconstruct + Axis A/B/C
VERIFY CUT run_id <id>
CLEANUP STAGING dry-run older_than 15d

That is the full operator surface. Agent does the rest.

Worked example 1 — KB document path

MARK file knowledge/dev/laws/dieu37-governance-organization-law.md theo quy trình operational-cut-workflow, lưu vào No-Vector Staging Zone

Agent → fetches via mcp__claude_ai_Incomex_KB__get_document_for_rewrite → authors pieces per 80000x doctrine → calls fn_iu_op_mark_file(...) → returns:

sid = 7a9f…
manifest_digest = e3a1…b76c
source_hash = c4d2…9f81
source_bytes = 20482
lifecycle = pending_review
destination = No-Vector Staging Zone (iu_core.iu_staging_*)

Then:

VERIFY MARK staging_id 7a9f…

Agent → fn_iu_op_verify_mark(sid, true, '<approval_doc_id>', '<approver>', '<actor>') → returns:

verdict = approved
lifecycle = approved

Then:

CUT staging_id 7a9f…, output IU corpus, verify reconstruct + Axis A/B/C

Agent → opens composer → fn_iu_op_cut(sid, true, '<actor>', true) → fn_iu_op_verify_cut(run_id, '<actor>') → closes composer → returns:

applied = true
pieces_created_count = 13
run_id = 4b88…
verify-cut verdict = verified
axes A/B/C = ok
no_vector_ok = true

Then:

VERIFY CUT run_id 4b88…

Idempotent re-verification → same verified verdict.

Worked example 2 — URL

MARK file https://example.com/law-draft.md theo quy trình operational-cut-workflow, lưu vào No-Vector Staging Zone

Agent → WebFetch(url) → markdown body → pieces → fn_iu_op_mark_file(source_text=fetched, source_ref=url, ...).

Worked example 3 — Local file

MARK file /Users/operator/draft/dieu99-draft.md theo quy trình operational-cut-workflow, lưu vào No-Vector Staging Zone

Agent → Read('/Users/operator/draft/dieu99-draft.md') → text → pieces → alias call.

Worked example 4 — Inline text

MARK inline "# Mini law\n\nĐiều 1. Định nghĩa\n..." theo quy trình operational-cut-workflow, lưu vào No-Vector Staging Zone

Agent → uses operator-provided text directly → fn_iu_op_mark_file(source_text=<inline>, source_ref='inline-<timestamp>', ...).

Cleanup

CLEANUP STAGING dry-run older_than 15d

Agent → fn_iu_op_cleanup_dry_run(15, '<actor>') → returns list of eligible staging rows (no mutation).

To actually clean, operator must explicitly run:

SELECT * FROM fn_iu_staging_cleanup(true, '<actor>');

(No alias for apply-mode cleanup — conscious operator action required.)

Operator pre-flight (one-time)

ssh contabo
docker exec -i postgres psql -U workflow_admin -d directus -c "SELECT proname FROM pg_proc p JOIN pg_namespace n ON n.oid=p.pronamespace WHERE n.nspname='public' AND p.proname LIKE 'fn_iu_op_%' ORDER BY proname;"
# Expect 5 rows: fn_iu_op_cleanup_dry_run, fn_iu_op_cut, fn_iu_op_mark_file, fn_iu_op_verify_cut, fn_iu_op_verify_mark

If the 5 functions are missing → apply 042R_iu_core_operator_aliases.sql first (see report 02).

Composer gate discipline

• fn_iu_op_cut(..., p_open_composer:=true) opens the gate in-TX. For durable cuts, the gate stays open after COMMIT — operator must immediately close it:

UPDATE dot_config SET value='false' WHERE key='iu_core.composer_enabled';

• For BEGIN/ROLLBACK proofs, ROLLBACK auto-restores false.

What this runbook does NOT permit

• Uploading any pending MARK payload to KB. (Use the alias; staging rows stay in NVSZ.)
• Calling fn_iu_staging_cleanup(true, …) from within any alias.
• Bypassing VERIFY-MARK or VERIFY-CUT.
• Calling fn_iu_cut_from_manifest with a fabricated source_hash.
• Touching production_documents, Qdrant, Nuxt deployment, or retention global enable.