Records that cannot prove human approval

The options

The order shown is not a ranking of preference.

1. Option 1

   Full suspension and manual records

   People directly control record creation and the spread of defects is stopped, but the review queue grows, and manual errors and extra staffing costs follow.

2. Option 2

   Keep limited use for record organization

   Routine administrative throughput is maintained and approval judgment stays separate, but source-document verification work remains, and reassembling accountability material carries a cost.

3. Option 3

   Keep use with independent duplicate records

   Existing throughput and separate evidence are secured at the same time, but the burden of reconciling record mismatches grows, and audit resources are consumed by running a double system.

The situation as it stands

The policy must be settled before the approval record form for the next operational cycle is distributed. If it stays undecided, new records keep piling up under a form carrying the same defect risk.

Approval and audit administration office of the fictional Ongyeol National Defense Agency. This is a present-day synthetic scenario in 2026; the events, institutions, AI systems, and figures are all a synthetic premise.

1. Premise 1The audit office of the fictional Ongyeol National Defense Agency was unable to reproduce the link between approver signatures and source documents in 27 of 300 approval records organized by the military AI. This finding concerns record defects; it is not a determination that unauthorized use of force occurred.
2. Premise 2The Civil Oversight Committee of the fictional Ongyeol National Defense Agency may restrict or suspend use of the administrative system. The duty of final human approval remains, and manual staff can review only half of the current intake volume within the same day.
3. Premise 3The audit officer argues that accountability is hard to trace without reproducible records. The approval officer worries that switching to manual work also delays review of legitimate protective duty, and appellants are not receiving explanations because the records are incomplete.

Where it holdsDecide the scope of use and the suspension conditions for a military AI administrative system that manages human approval records.

What can be lost

• Appellants may lose the chance to see the basis and the responsible officer for a decision that affected them.
• Approval officers may bear responsibility wrongly, for lack of records that prove their own judgment.
• Personnel on protective duty may receive needed support late, because of delays in administrative review.

What is still unknown

1. Unknown 1The share of records whose original approval can be recovered where the link could not be reproduced
2. Unknown 2The actual range of errors and delays that manual records would produce
3. Unknown 3Whether a separate record system operates independently of the existing defects

Signals to decide again

• The audit office checks each week whether random records can be re-linked to their originals, and reconsiders the scope of use if new defects are found.
• The head of administrative processing tabulates the review queue and delays to protective duty each day, and puts staffing and operating policy back on the table if the approved processing standard is exceeded.
• The appeal examiner reviews failures to confirm responsible officers and delays in accessing materials every two weeks, and demands a review of record policy if repeated cases are confirmed.