GPT Review — B3-F1c-e Probe PASS: Reuse with Wrapper, Hardcode Audit Required — 2026-05-13

Scope reviewed

Reviewed Agent probe report:

• knowledge/dev/laws/dieu44-trien-khai/reports/p3d-birth-system-b3f1c-e-dot-dot-health-reuse-viability-probe-report.md

Verdict

Status: PASS_ACCEPTED_AS_EVIDENCE__REUSE_WITH_WRAPPER_IS_CANDIDATE__HARDCODE_AUDIT_REQUIRED

The probe is valid and accepted. It proves that dot-dot-health is the correct existing infrastructure to investigate/reuse before building a new Agent Data bridge, Directus Flow, Nuxt endpoint, or new DOT.

However, implementation is not approved yet. The probe also revealed existing hardcode/drift issues in dot-dot-health and its DOT registry/scheduler metadata. Before designing wrapper + system_health_checks INSERT, a read-only hardcode/auto-scale audit is required.

Accepted probe findings

• dot-dot-health exists at a single path and is a working generic executor.
• executor_type='function' dispatch path exists.
• Function dispatcher uses RW path, so write-capable full-scan execution is technically viable.
• Existing scheduling exists via cron at 03:00 daily.
• No equivalent birth onboarding full-scan health check exists in system_health_checks.
• No existing DOT directly dispatches fn_birth_onboarding_full_scan().
• Current direct reuse is blocked by signature mismatch:
  • executor expects public.<executor_ref>(jsonb) RETURNS boolean / boolean text-cast;
  • current function is public.fn_birth_onboarding_full_scan() RETURNS jsonb.
• Candidate path is REUSE_WITH_WRAPPER_FUNCTION.

Critical caveats revealed by probe

1. Hardcoded jurisdiction

dot-dot-health has:

JURISDICTION="NRM-LAW-35-V5P2"
readonly JURISDICTION

This is a constitutional concern. If B3-F1c inserts a Law 44 check under Law 35 jurisdiction only to fit a hardcoded executor, that may be governance debt. We must determine whether this is acceptable as DOT health jurisdiction, or whether the executor should be parameterized / registry-driven.

2. Function dispatcher has hardcoded assumptions

Dispatcher assumes:

• schema public;
• function identified by proname only;
• a single jsonb argument;
• boolean return interpreted by text equality;
• threshold logic delegated to wrapper, not registry.

These may be acceptable as current executor contract, but they are not automatically self-expanding for future function-return shapes.

3. Cron has likely invalid flag

Cron calls:

dot-dot-health --local

Probe says --local is not accepted by current parse_args. If true, the existing scheduled automation may not actually run successfully. This must be verified before relying on the cron as automatic coverage.

4. Registry drift

Observed:

• dot_tools.DOT-HEALTH-DOT.file_path = bin/dot/dot-dot-health.ts, but actual executable is Bash /opt/incomex/dot/bin/dot-dot-health.
• dot_tools.DOT-HEALTH-DOT.cron_schedule is empty despite cron being installed.
• Duplicate DOT namespaces exist: DOT-NNN and DOT_BIRTH_* variants.

These are not cosmetic: they affect discoverability, DOT governance, and auto-scale.

Required next step

Before wrapper design or INSERT, run a new read-only hardcode/auto-scale audit:

B3-F1c-f dot-dot-health Hardcode & Auto-scale Audit

The audit must not mutate anything and must not invoke fn_birth_onboarding_full_scan().

Audit objectives

1. Identify all hardcoded values in /opt/incomex/dot/bin/dot-dot-health.
2. Classify each hardcode:
   • SAFE_REVIEWED_CONSTANT
   • CURRENT_CONTRACT
   • HARDCODE_RISK
   • HARD_CODE_VIOLATION
   • SCALE_BREAK_RISK
3. Identify all concrete values stored in current DB registry rows (system_health_checks, dot_tools, cron) related to dot-dot-health.
4. Determine whether dot-dot-health is truly automatic today, given the --local anomaly.
5. Determine whether B3-F1c should:
   • add a wrapper + row only;
   • first patch/parameterize dot-dot-health;
   • patch DOT registry drift first;
   • repair scheduling first;
   • or continue Agent Data bridge.

Required probe areas

• Script constants: jurisdiction, schema, env paths, PG helpers, function signature, return parsing, whitelists, KB paths, log paths.
• Argument parsing: accepted flags vs cron flags.
• Cron/systemd/Directus schedule records.
• dot_tools registry row(s) for dot-dot-health.
• system_health_checks jurisdiction and executor-type distribution.
• Existing function dispatcher contract and extension points.
• All birth-related duplicate DOT rows and whether any should be merged/reused.

Governance status

b3f1c_e_probe_review_status=PASS_ACCEPTED_AS_EVIDENCE__HARDCODE_AUDIT_REQUIRED
candidate_viability=REUSE_WITH_WRAPPER_FUNCTION
wrapper_design_allowed=false_until_hardcode_audit
system_health_checks_insert_allowed=false
new_dot_creation_allowed=false
agent_data_bridge_paused=true
scheduler_execution_allowed=false
b3f_complete_allowed=false
phase5c2_migration_allowed=false
next_recommended_action=OPUS_DRAFT_B3F1C_F_DOT_DOT_HEALTH_HARDCODE_AUTOSCALE_AUDIT_PROMPT