P3D — B3-F1c-f dot-dot-health Hardcode & Auto-scale Audit Design Note

Date: 2026-05-13 Author: Opus

Context

B3-F1c-e probe found REUSE_WITH_WRAPPER_FUNCTION viable. But before implementing wrapper + system_health_checks row, GPT requires audit of 3 potential blockers found in probe:

1. Cron --local flag mismatch — if script doesn't parse --local, cron 03:00 might be silently failing → adding row = useless
2. Jurisdiction hardcoded — NRM-LAW-35-V5P2 in script → adding Law 44 check requires either (a) accepting governance mismatch or (b) patching script
3. Registry drift — dot_tools row has wrong file_path (.ts), empty cron_schedule → fragile foundation

Opus opinion on scope

Audit should focus on 3 blocking questions that determine next action:

• Cron works? → if NO, fix cron first
• Jurisdiction blocks us? → if YES, patch script first
• Drift blocks dispatch? → if YES, clean registry first

Legacy debt (duplicate DOT namespaces, stale metadata) should be DOCUMENTED but NOT block B3-F1c wrapper path unless it directly affects dispatch.

Decision tree

Q1: Cron works?
  NO → REPAIR_DOT_DOT_HEALTH_SCHEDULER_FIRST
  YES/UNKNOWN → continue

Q2: Can add under Law 35 jurisdiction?
  YES (acceptable debt) → WRAPPER_AND_ROW_SAFE_NOW_WITH_KNOWN_DEBT
  NO (must parameterize) → PATCH_DOT_DOT_HEALTH_FIRST
  
Q3: Drift blocks wrapper?
  YES → PATCH_DOT_REGISTRY_FIRST
  NO → proceed with wrapper

B3-F1c-f Design Note | Opus | 2026-05-13