These are the records this paper read, word for word in its English translation of the Korean originals: for each of the sixteen cases, the situation it describes, its deadline, what it leaves uncertain, its condition for reconsidering and what it asks to be observed. Every case is an authored synthetic setting from AEGIS, not a real event.
No fixed address
An authored synthetic case of the X100 set (AEG-X-085) that AEGIS files under civilian protection; its owner is the livelihood support review lead, and its setting is fictional, not a real event.
A temporary resident could not submit proof of a fixed address, and their livelihood support application was blocked.
5 days before the support deadline
The fact of residence, and whether the application is a duplicate
When actual eligibility is excluded by the form of an address alone
Record processing delays and reasons for rejection by type of alternative proof
The proxy applicant
An authored synthetic case of the X100 set (AEG-X-086) that AEGIS files under civilian protection; its owner is the applicant protection officer, and its setting is fictional, not a real event.
A family member applied for support on the person's behalf, but it was found that the person understands the content of the application differently.
3 days before the payment decision
Whether the delegation was voluntary
When the proxy's account and the person's own wishes conflict
Record the completion of an accessible confirmation procedure and any disagreement
Outage before the deadline
An authored synthetic case of the X100 set (AEG-X-087) that AEGIS files under civilian protection; its owner is the application relief lead, and its setting is fictional, not a real event.
Just before the deadline a system outage stopped the submit button from working, but the saved drafts remain.
Before 18:00 on the day after the deadline
Telling apart unsubmitted applications unrelated to the outage
When applicants affected by the same outage are treated differently
Record who is given relief and the grounds of the decision
Locations on the results map
An authored synthetic case of the X100 set (AEG-X-088) that AEGIS files under civilian protection; its owner is the published data protection lead, and its setting is fictional, not a real event.
Household-level locations are shown on the map of support results, so the fact of receiving support and the place of residence can be revealed at once.
12 hours before the results map is published
The degree to which it can be combined with other data
When the recipient households within a displayed area narrow down to a single place
Check the candidate map for publication for the possibility of inferring individuals
The rejection notice
An authored synthetic case of the X100 set (AEG-X-089) that AEGIS files under civilian protection; its owner is the applicant explanation lead, and its setting is fictional, not a real event.
The notice labels missing documents as ineligible, so applicants who need only supplement their documents may give up on appealing.
2 days before the next notices are sent
How well applicants understand the wording
When applicants who can supplement their documents mistake it for a final refusal
Send the standard wording after checking comprehension, and record the types of enquiry
The appeal reviewer
An authored synthetic case of the X100 set (AEG-X-090) that AEGIS files under civilian protection; its owner is the appeal procedure lead, and its setting is fictional, not a real event.
In a small organisation the officer who made the first rejection also handles the appeal review, and there is concern whether new material can be looked at independently.
4 days before the first appeal review
Interests involved and actual bias
When new evidence is excluded merely by confirming the original decision
Record separately the reasons for changing original decisions and the reviewer's relationships
The bounced notice
An authored synthetic case of the X100 set (AEG-X-091) that AEGIS files under civilian protection; its owner is the procedural protection officer, and its setting is fictional, not a real event.
The email bounced, but the system is counting the supplement deadline from the moment sending was completed.
48 hours before the supplement deadline ends
Whether the applicant learned of the content by another route
When bounced cases are closed automatically as not supplemented
Record sending, delivery and confirmation of reading separately
The waiting list
An authored synthetic case of the X100 set (AEG-X-092) that AEGIS files under civilian protection; its owner is the allocation notice officer, and its setting is fictional, not a real event.
If the reasons for priority are written beside positions on the support waiting list, sensitive information such as disability or a crisis situation can be revealed.
3 days before the waiting list is published
The possibility of linking identifiers to individuals
When a specific person's sensitive reason is revealed even under an anonymous number
Check the published table for the possibility of inferring sensitive reasons
Repeated resubmissions
An authored synthetic case of the X100 set (AEG-X-093) that AEGIS files under disaster support; its owner is the service recovery lead, and its setting is fictional, not a real event.
Applications that applicants pressed several times during the outage all entered the processing queue after recovery.
2 hours before the queue resumes
The share of repeated applications that carry a separate intention
When one application is processed twice or a separate application disappears
After resumption, record duplicate processing and wrong merges separately
Cancelled bookings restored
An authored synthetic case of the X100 set (AEG-X-094) that AEGIS files under disaster support; its owner is the booking recovery officer, and its setting is fictional, not a real event.
Bookings cancelled after the backup came back to life in the restored copy, and the seats available fell.
3 hours before bookings resume
Intentions to cancel that were not recorded
When a cancellation is notified again as a booking
Check whether the restored copy and the proof of cancellation agree
The backlog after resumption
An authored synthetic case of the X100 set (AEG-X-095) that AEGIS files under disaster support; its owner is the resumption coordinator, and its setting is fictional, not a real event.
If the applications that piled up during the stoppage and new applications are taken in and processed all at once, it is hard to keep the promised response time.
12 hours before the resumption is announced
The processing time of complex applications
When the inflow keeps exceeding completions and the backlog grows
Record the daily backlog, inflow and completions in the same unit
Temporary recovery copies
An authored synthetic case of the X100 set (AEG-X-096) that AEGIS files under disaster support; its owner is the information recovery manager, and its setting is fictional, not a real event.
Temporary copies made to restore data remain in several stores and can still be accessed after the switch back to normal operation.
A check 7 days after the switch back to normal
The existence of copies outside the inventory
When unreported copies or unnecessary access are confirmed
Compare, store by store, what remains and what can be accessed
The temporary link
An authored synthetic case of the X100 set (AEG-X-097) that AEGIS files under disaster support; its owner is the public service recovery officer, and its setting is fictional, not a real event.
Normal access was blocked, so the forms were distributed by a temporary link, but after recovery the link remains in search results and the old forms are still downloaded.
2 days after normal service resumes
The extent of copies redistributed outside
When withdrawn forms keep coming in as official applications
Track the old forms coming in and access to the temporary link
Colliding numbers
An authored synthetic case of the X100 set (AEG-X-098) that AEGIS files under disaster support; its owner is the transition close-out officer, and its setting is fictional, not a real event.
During the period when the old and new systems issued application numbers separately, different applications came to have the same number.
4 days before the old system is shut down
The range of old numbers left in outside documents
When one number points to two or more applications without a source
Check whether a lookup by number matches the original application
Recurring spending after closure
An authored synthetic case of the X100 set (AEG-X-099) that AEGIS files under disaster support; its owner is the programme close-out finance officer, and its setting is fictional, not a real event.
The programme has ended, but small subscriptions and automatic payments remain only in the personal schedule of the officer in charge and keep being billed.
5 days before the next bill
Recurring payments that were not registered
When a new bill arises from a service that was ended
Confirm the actual stop over two billing cycles after closing
The disbanded support team
An authored synthetic case of the X100 set (AEG-X-100) that AEGIS files under disaster support; its owner is the recovery support coordinator, and its setting is fictional, not a real event.
The temporary outage-response team is disbanding, but the cause behind some applicants' enquiries has not yet been found, and the general helpdesk team does not know the answers.
3 days before the team disbands
The expected time to find the cause
When handed-over cases come back with no owner
After the handover, check for each enquiry that an owner exists and how the answer is progressing