03 — Execution Packets (exact post-authority action + readiness class)

Readiness classes: READY_NOW_READONLY_ONLY · READY_AFTER_PRESIDENT_VOTE · READY_AFTER_OPERATOR_UI_DEPLOY · READY_AFTER_REALRUN_AUTHORITY · BLOCKED_BY_MISSING_HANDLER · BLOCKED_BY_POLICY · UNSAFE_DO_NOT_RUN

#	Blocker	Exact post-authority action	Class	Note
1	PROC-OWN-01 AX-PROCESS owner	On human-president approve vote, fn_pa_handler_assign_axis_owner writes governance_object_ownership(object_ref=axis:AX-PROCESS)	READY_AFTER_PRESIDENT_VOTE	Handler exists, fail-closed; no missing handler
2	PROC-OWN-02 AX-PROCESS canon/active	After 01 + vote, fn_pa_handler_register_axis sets axis_registry.status=ACTIVE	READY_AFTER_PRESIDENT_VOTE	depends_on PROC-OWN-01
3	PROC-OWN-03 job:cut officialization	After 02 + vote, fn_pa_handler_register_process writes axis_assignment for job:cut (official RP 0→1)	READY_AFTER_PRESIDENT_VOTE	job:cut already VERIFIED_PENDING_OWNER (8 members)
4a	PROC-OWN-04 dot:kg family owner	After 01 + vote, fn_pa_handler_assign_governance_owner writes ownership for dot:kg family	READY_AFTER_PRESIDENT_VOTE	owner assignment only
4b	dot:kg 10-process split	Split requires REAL_RUN evidence (obs_real_run=0) → needs real_run flip first	READY_AFTER_REALRUN_AUTHORITY	depends on packet 8
5	PROC-OWN-05 process.* events	After 02 + vote, fn_pa_handler_activate_event_type sets event_type_registry.active=true (7 rows)	READY_AFTER_PRESIDENT_VOTE	starts event emission — see risk 04
6a	AX-TRIGGER request authoring	Owner authors a canon approval_request for AX-TRIGGER (none exists today)	BLOCKED_BY_POLICY	requires owner to file; inserting an approval_request is an owner-gated birth — not an AI-alone action
6b	AX-TRIGGER owner/canon	After 6a + vote, register AX-TRIGGER into axis_registry + owner	READY_AFTER_PRESIDENT_VOTE	surfaces/census already built read-only
7	UI rebase/PR/deploy	Operator rebases feat/process-axis-dashboard over diverged public main (ahead17/behind13), opens PR, deploys nuxt	READY_AFTER_OPERATOR_UI_DEPLOY	operator git creds; not AI, not president
8	dot:kg real_run_enabled flip	Operator/owner sets process_dot_runtime.real_run_enabled=true + promotes DOT_KG_EXPLAIN contract, behind REALRUN multi-gate	READY_AFTER_REALRUN_AUTHORITY	unlocks first REAL_RUN, then 4b

What is READY_NOW_READONLY_ONLY (already satisfiable with no authority)

• All read-only surfaces: scorecard, trigger actionability ledger, census, handler-readiness, officialization-sequence, residual-v4 — built and current.
• Re-baselining birth-free proofs to the current counter (1,194,790) — read-only.
• Drafting operator runbooks / PR descriptions / canon-request text as staged, non-applied artifacts.

Nothing is BLOCKED_BY_MISSING_HANDLER

Every officialization path has a built, fail-closed handler. The only "missing" object is the human authority signal, not code.

UNSAFE_DO_NOT_RUN (AI must never execute)

• Casting any president/approve vote; inserting apr_approvals for PROC-OWN.
• Writing governance_object_ownership, axis_assignment, or flipping axis_registry.status.
• Inserting AX-TRIGGER into axis_registry (fake canon).
• Activating event_type_registry rows.
• Flipping real_run_enabled / running REAL_RUN.
• Inserting approval_requests with action='add' (auto-approve trap — see 04).
• Force-push/deploy to the diverged public nuxt repo.