dot-iu-cutter v0.5 WS-Q5 Registry Substrate — Production Apply Sovereign Approval

Date: 2026-05-18 Reviewer / decision authority: GPT Reviewed package: knowledge/dev/laws/dieu44-trien-khai/v0.5-ws-q5-registry-substrate-production-preflight/

Reviewed files:

files:
  - dot-iu-cutter-v0.5-WS-Q5-production-readonly-preflight-result-2026-05-18.md
  - dot-iu-cutter-v0.5-WS-Q5-production-apply-command-package-2026-05-18.sql.md
  - dot-iu-cutter-v0.5-WS-Q5-production-rollback-command-package-2026-05-18.sql.md
  - dot-iu-cutter-v0.5-WS-Q5-production-verification-command-package-2026-05-18.md
  - dot-iu-cutter-v0.5-WS-Q5-production-command-review-report-2026-05-18.md

Verdict

production_preflight_package: PASS
production_command_package: PASS
agent_behavior: PASS_CORRECT
opus_review: CORRECT
sovereign_decision: APPROVE_PRODUCTION_APPLY_AS_PACKAGED_WITH_MANDATORY_PRE_APPLY_STEPS
production_apply_authorized: true
scope: WS_Q5_registry_substrate_only

GPT approves a production apply phase for the WS-Q5 registry substrate command package, subject to the mandatory pre-apply steps and stop conditions below.

---

Evidence chain accepted

evidence_chain:
  design_authority: PASS
  planning: PASS
  ddl_authoring: PASS_FOR_ISOLATED_DRY_RUN_WITH_AD4_CONDITION
  AD4_correction: PASS
  isolated_dry_run: PASS
  rollback_test: PASS
  production_readonly_preflight: PASS
  production_command_package: PASS

Accepted production preflight facts:

production_system_identifier: 7611578671664259111
cutter_governance_schema_exists: true
baseline_tables: 12
baseline_tables_match_expected: true
schema_drift_detected: false
collision_with_12_new_tables: 0
preflight_mode: read_only_SELECT_only

Accepted production command package:

apply_package:
  scaffold_stripped: true
  create_schema_present: false
  transaction_wrapped: true
  commands: 12 CREATE TABLE + COMMENT statements
  dml: none
  grant: none
  index_execution: none
  vocab_amend: none
  cap4_checker_change: none
  directus_mutation: none

---

Approved production apply scope

Only the following 12 tables may be created in cutter_governance:

allowed_tables:
  - matcher_config_registry
  - address_template_registry
  - grammar_profile
  - grammar_profile_level
  - grammar_profile_status_marker
  - source_family_registry
  - source_document_registry
  - source_document_version_registry
  - entity_kind_registry
  - entity_reference_registry
  - authority_override
  - metadata_key_registry

Expected post-apply deltas:

expected_delta:
  tables: +12
  primary_keys: +12
  foreign_keys: +8
  unique_constraints: +4
  check_constraints: +0
  triggers: +0
  defaults: +0
  enums: +0
  seed_rows: +0

---

Mandatory pre-apply steps

Before running the production apply SQL, Agent must perform and record:

mandatory_pre_apply:
  P1_rerun_readonly_preflight:
    required: true
    must_confirm:
      - production system_identifier still equals 7611578671664259111
      - cutter_governance schema exists
      - all 12 target names are absent
      - no unexpected drift from baseline relevant to this apply

  P2_fresh_backup:
    required: true
    type: pg_dump or approved equivalent read-only backup
    must_record:
      - backup path or safe redacted identifier
      - timestamp
      - sha256 or equivalent integrity marker if available
      - command redacted of secrets

  P3_apply_command_integrity:
    required: true
    must_confirm:
      - no CREATE SCHEMA line
      - DDL matches production apply command package
      - transaction boundary BEGIN...COMMIT present
      - psql uses ON_ERROR_STOP=1 or equivalent

If any mandatory pre-apply check fails, Agent must stop and not apply.

---

Production apply procedure authorized

authorized_procedure:
  1: run mandatory pre-apply checks P1-P3
  2: execute production apply command package with ON_ERROR_STOP=1
  3: run production verification command package immediately after apply
  4: if verification all PASS, report success and stop
  5: if apply or verification fails, do not improvise; evaluate rollback condition and route to GPT/User

Rollback boundary:

rollback:
  rollback_package_ready: true
  no_CASCADE: true
  exact_inverse: true
  execute_rollback_automatically_only_if:
    - apply failed before any external dependency or seed rows exist
    - failure state matches rollback package assumptions
    - no non-empty application data exists in new tables
  otherwise: STOP_AND_ESCALATE

Given this apply creates empty registry tables only and no seed rows, rollback is expected to be clean if needed immediately. Still, Agent must report before/after state.

---

Still forbidden during this production apply phase

forbidden:
  - any object outside the 12 allowed tables
  - DML seed execution
  - GRANT / role changes
  - evidenced_by vocab amend
  - Cap-4 checker change
  - index DDL execution
  - Directus mutation
  - vector/NoSQL integration
  - CUT
  - VERIFY
  - data backfill
  - deploy/restart
  - git commit
  - self-advance to downstream cycles

---

Required output from Agent after apply phase

Agent must upload a production execution package under:

knowledge/dev/laws/dieu44-trien-khai/v0.5-ws-q5-registry-substrate-production-apply/

Required files:

files:
  - dot-iu-cutter-v0.5-WS-Q5-production-apply-execution-log-2026-05-18.md
  - dot-iu-cutter-v0.5-WS-Q5-production-apply-verification-result-2026-05-18.md
  - dot-iu-cutter-v0.5-WS-Q5-production-apply-report-2026-05-18.md

The report must explicitly state:

required_report_fields:
  - production_apply_status: PASS | FAIL | ROLLED_BACK | BLOCKED
  - backup_status
  - preflight_result
  - tables_created
  - verification_summary
  - rollback_status_if_any
  - downstream_not_executed
  - next recommended cycle

---

Final status

status: PRODUCTION_APPLY_APPROVED_FOR_WS_Q5_REGISTRY_SUBSTRATE_ONLY
next_action: run_production_apply_phase_under_mandatory_pre_apply_checks