06 · Residual Hardening v4 (Phase E)

Method

Took the 8 AWAITING_OWNER_RECONCILE members from v_workflow_residual_evidence_hardening_v3 and read each object's live script header via ssh. Built v_workflow_residual_evidence_hardening_v4 (additive view over v3) reclassifying on evidence.

Before → After

AWAITING_OWNER_RECONCILE: 8 → 2.

object_key	header evidence	v3	v4
apply_composition_fixes.sh	one-shot driver over 3 deterministic composition mismatches (PIV-001/016/021)	reconcile	RESOLVED_NOT_PROCESS_ONE_SHOT
dot-cron-matrix-setup	one-shot installer — adds matrix refresh cron (installer, not the process)	reconcile	RESOLVED_NOT_PROCESS_ONE_SHOT
dot-dieu43-fs-init.sh	Phase-2 Đ43 Block-1 Bootstrap fs init — one-shot	reconcile	RESOLVED_NOT_PROCESS_ONE_SHOT
dot-dieu43-fs-verify.sh	Bootstrap fs verify — one-shot	reconcile	RESOLVED_NOT_PROCESS_ONE_SHOT
dot-search-canary	"P3D search reliability canary" — recurring probe	reconcile	RESOLVED_COMPONENT_HEALTH_MON
dot-context-pack-retention-cleanup	recurring 7-day retention cleanup	reconcile	RESOLVED_COMPONENT_MAINTENANCE
dot-pivot-update	governed UPDATE DOT tool (composition_level/species)	reconcile	AWAITING_OWNER_RECONCILE (genuine register decision)
host_crontab 4c12473…	content not resolvable from header	reconcile	AWAITING_OWNER_RECONCILE

Full v4 distribution (23 member rows)

• RESOLVED_ALREADY_MANAGED 9
• RESOLVED_NOT_PROCESS_ONE_SHOT 4
• RESOLVED_COMPONENT 4
• RESOLVED_NOT_PROCESS 2
• RESOLVED_COMPONENT_HEALTH_MON 1
• RESOLVED_COMPONENT_MAINTENANCE 1
• AWAITING_OWNER_RECONCILE 2

Why the 2 remain

• dot-pivot-update is a real governed mutation tool that should be registered in dot_tools — but registering = an owner decision (and dot_tools insert is a birth trigger). Correctly owner-gated.
• The unresolved crontab hash needs its decoded command line, which the header grep did not surface — flagged for owner reconcile (register-or-quarantine).

Evidence-not-faked note

dot_tools was searched live for all 8 names → 0 matches, confirming none are already managed; the reclassifications above are based on script purpose (one-shot vs recurring vs governed tool), not on a fabricated dot_tools link.

Blocker

2 owner reconcile decisions. No engineering blocker.