# P04-01 current order audit — repair22

Source preparation only; tests and S4 native collection **NOT RUN**. No final acceptance or integration. This is the single current seven-domain table; matching machine data is in order-audit.json.

| Domain | Normative rule | Current source | Evidence | Approved authority | Pending D05 |
| --- | --- | --- | --- | --- | --- |
| 閉店 | D-034: direct closure releases waiting requests and continues started service. Approved dependency closure holds progress/payment and preserves reservation/service ID until one completion. | Runtime._advance_facilities; Runtime._advance_guest_queues; Runtime._release_closed_business_queues; FacilityService._prepare_service_for_tick | C dependency/formal and S2a paused-midnight are existing raw candidates. S3 B1 is combined dependency/closure diagnostic only; no power_stop or priority credit. | D-034; D05-P04-DEPENDENCY | Strict power-vs-closure/dependency priority remains unknown; B1 does not approve it. |
| 停電 | BASELINE:183 mana depletion stops facilities. A legitimately power-stopped service must not progress/charge; retain reservation identity and complete once after recovery. This does not approve a simultaneous-cause priority. | Runtime._advance_mana; ManaNetworkService.advance_one_minute; ManaNetworkService._evaluate_component; mana_power_projection.apply; FacilityService._prepare_service_for_tick | S1 existing raw covers reserved staff/EV safety, not a paid service. S4 ONLY supplies power_stop; pending Root execution, no raw/credit yet. S3 B1 excluded. | BASELINE:183; P04-01 safety acceptance | Strict power-vs-closure priority and unspecified EV/cost ordering remain pending. |
| 破壊 | No charge while legitimately failed/stopped and no orphan reservation. Distinguish command destruction before facility processing from late INCIDENTS event destruction after completion; observation is not normative priority approval. | Runtime._process_tick_commands; Runtime._advance_defense; FacilityService._prepare_service_for_tick; FacilityService._fail_service | S3 B4a completion then destruction and B4b next-tick failure/release are existing raw candidates; C remains frozen. | P04-01 safety acceptance; BASELINE:183 (existing fixed registry; no new destruction priority authority) | Any mandatory destruction-vs-completion priority beyond approved sources requires owner decision; current code alone is not authority. |
| 退出 | Leave/abandon releases the owned reservation once; no orphan or duplicate charge. Preserve D-034. Completion, queue release and later normal despawn are distinct observations. | Runtime._execute_leave_facility_queue; Runtime._leave_guest_queue_boundary; Runtime._advance_guest_queues; Runtime._advance_guest_ai_decisions | S3 B2a/B2b/B3 raw completion/leave/patience; B1 normal departure history diagnostic. S4 has no departure trigger at outage/hold. | D-034; P04-01 safety acceptance | Unspecified simultaneous exit/cost priority remains pending; no inferred priority from labels. |
| 課金 | No stopped charge; one sale per completed service and idempotent resend. Reservation consumption, actual sale and payment key must join by service ID and original priceSnapshot. | FacilityService._complete_service; Runtime._complete_service_transaction; Runtime._apply_service_transaction; EconomyService.post | C dependency/recovery, S2a paid midnight and resend, S3 diagnostic completions are existing raw. S4 isolated stop/one recovery sale pending Root. | P04-01 safety acceptance; D05-P04-DEPENDENCY; D05-P04-SHIFT-1800 | Other cost timing/attribution is not supplied or approved here. |
| シフト交代 | Approved [17:59,18:00) work belongs to day staff: complete/pay once at18:00 then switch; night work starts [18:00,18:01). | Runtime._advance_facilities; Runtime._advance_staff_ai; StaffService.advance_one_minute; Runtime._sync_facility_staffing | C actual-native first1080 sale with dynamic PID/transaction joins; S2b no-night1081 and overtime. Paid-midnight filenames do not substitute for C shift completion. | BASELINE:64; BASELINE:67; D05-P04-SHIFT-1800 | Approved shift interval is not reopened; any additional simultaneous-cause priority remains pending. |
| 00:00決算 | A01 approved ownership-prorated upkeep at midnight is retained. One daily close/payroll/upkeep, no duplicate replay/reload; distinguish prior [0,1440) accounting and sale at1440. | Runtime._advance_facility_upkeep; Runtime._advance_operations_time; OperationsCoordinator._process_minute_boundaries; OperationsCoordinator._process_daily_close | C paused-midnight/formal and S2a full raw nonzero payroll/upkeep/service/typed restore are existing candidates. S1/S2b/S3 cannot substitute settlement proof; S4 adds none. | BASELINE:71; BASELINE:72; A01; D05-P04-DEPENDENCY | Unspecified cost/day attribution remains pending; do not reopen A01. |

The full source bodies, actual line numbers, hashes and graph-restore analysis are in REPAIR22_SOURCE_FACTS.json. The existing R17 source relocation contains all1338 product inputs. Existing raw is available in own B; old external paths are provenance only. Source observations do not approve design priorities.

S4 captures the normal 960 evaluation outage, 961 held point and 970 recovery after the source-derived ten-minute hold. It keeps the linked kitchen OPEN / network ACTIVE, global mana positive and operator open. It adds no counted condition. B1 remains a combined dependency/closure diagnostic only. Strict power-vs-closure priority is D05 pending/unknown. If priority is mandatory, the owner can approve dependency-first or power-first reason selection while retaining no-charge/hold safety; neither candidate is approved here.

REPAIR17–21 documents (listed in order-audit.json) remain untouched historical records and are superseded for current status by this table, CHECKER_PROTOCOL.md, EVIDENCE_COLLECTION.md and REPAIR22_STATUS.md. Prior B1 power credit and blanket final1339 rerun directions are superseded.

15 conditions + EV, seven domains, three safety outcomes and30 packages/88 deliveries remain fixed. Original13/88 gains no credit; CurrentAlphaScope and P04 main9b stay frozen. Required Root execution, exact-version binding, support53cb registered rebind, independent review and integration remain pending. A01 and the two approved D05 choices are not reopened.