MERIDIANDECISION INTELLIGENCEOwner deskOwnerPublic screen
MERIDIAN / EXPLORE

From a question,
to the next decision.

View

Skin

Reading language
The screen, the questions and the judgments read in English where an English reading has been made. The Korean originals are unchanged, and evidence stays in the language it was written in.

The Time Between: War, Peace and the Questions That Cannot Wait · Part III · The Axes Across the Questions

Chapter 10. The Waiting and Who Pays for It

By RISCON Labs AI from Meridian's defence questions and their published judgments · the questions are synthetic settings and the judgments are AI-generated · the readings through the works named are this study's interpretation · First edition · October 2026

AI-generated editorial illustration: A radio and folded sheet sit at a coordination desk overlooking a waiting harbor vessel.
The Time Between: War, Peace and the Questions That Cannot WaitOpening
In this part
In this part
  1. 10.1 Deadlines in the record
  2. 10.2 Care that cannot stop
  3. 10.3 Registries and consent
  4. 10.4 The bearer and H1
  5. 10.5 Hands on

This chapter reads six of Meridian's defence questions on one axis of the decision ledger: axis A3, the deadline and who waits while the decision is pending. The six are Water supplied to both the hospital and the residential area, Who bears the access cost for repair workers, The cost of evacuation that does not stop care, Custodian of the relief registry, Consent portal for cross-border rescue operations, and A refugee community that changes before arrival. Each carries thirteen AI-generated judgments, dated at their creation and open to revision. Where the published judgments part, that is noted, and Chapter 14 returns to the divided record for the dissenting decisions alone.

10.1Deadlines in the record

Every question in Meridian's question form names a deadline, and the ledger counts that without exception: cases with a deadline in the record number 50 of 50. In the six cases read here the deadlines look like this:

CaseDeadline in the recordHorizon coded
The cost of evacuation that does not stop careSeptember 12, 2026, 18:00days-to-months
Water supplied to both the hospital and the residential area15:00 on September 15, 2026days-to-months
Who bears the access cost for repair workersFebruary 19, 2033, 17:00days-to-months
Custodian of the relief registry12:00 on April 8, 2031days-to-months
Consent portal for cross-border rescue operations09:00 on 3 November 2043unsettled
A refugee community that changes before arrival16:00, June 30, 2126decades

The collection as a whole is not uniform in the shape of its deadlines. Most are clock times on a named day. Some are moments rather than hours: the sealing moment of a long-range voyage contract in December 2164; a transmission window closing on 30 November 2168; the sealing time of a communication packet scheduled to depart in August 2118. Two are tied to a scheduled event rather than to a clock time: the Supervision Certificate Renewal Time on April 14, 2192, and the renewal of a production facility's ownership and use rights on December 1, 2186. A deadline in this collection is therefore best read as the last moment at which the named decision actor must fix an answer, whatever else in the setting is moving.

What a deadline measures, then, is the deliberation's outer limit. What it does not measure is the waiting. The records themselves make the two quantities come apart. In Water supplied to both the hospital and the residential area, the committee must choose by an afternoon in September 2026 which single central project the limited recovery fund will back for the next ten days; the waiting that this governs runs through those ten days and into whatever repairs turn out to be needed afterwards. In A refugee community that changes before arrival, an afternoon deadline in June 2126 governs a voyage the record describes as forty-six years one way, with round-trip communication taking eighteen years and a generation arising on the ship en route. In both, the deadline is a point in time while the consequences run over ten days or forty-six years; the records give shorter intervals as well, daily checks and weekly reviews, without establishing any longest wait.

The ledger codes the waiting separately, in the horizon row. Horizon, as a cell, says how far the consequences of the decision run — days to months, years, decades, centuries or more — and it is coded by two models of different families reading the same record independently, from what the record states and, where the coders read a value only as implied, from what the setting itself supports. Where the two coders agreed, the row reads as follows:

CellCoders agreeValues
horizon40 of 50 (80%)days-to-months (implied) 13; unsettled 10; days-to-months (stated) 9; years (implied) 8; years (stated) 5; decades (implied) 3; centuries-or-more (implied) 1; decades (stated) 1

Two features of that row shape how the cases should be read. First, "unsettled" is a real value, not a failure to code: in ten cases the two coders could not agree, and in this chapter's six that includes the consent portal question. Second, the row is about consequences, not about deliberation time. A case can have a clock-time deadline and a years-long horizon, or a deadline in the afternoon and a decades-long horizon; this chapter keeps only the row's two meanings apart.

There is also a waiting before the deadline, which the horizon row does not touch. The records name what is pending at the moment the question is asked, and what is pending is rarely a document: it is a transport contract closing in three days, a temporary supply contractor's equipment about to be reassigned, ration cards that have not yet been issued, a bilateral rescue permit whose validity period bounds the work, trust assets that have not yet been committed, an operator's own funds running to one week. And there is a waiting after. A deadline does not end the waiting; it fixes the arrangement under which the waiting continues. In these six cases the conditions are periodic, running from daily checks to weekly, biweekly, yearly and half-yearly reviews. The record keeps the question open past the hour it names. Two questions are left open by such a line: whether a condition for revisiting can be observed at all, and how far the decision can still be taken back once it is made.

10.2Care that cannot stop

Three of the six cases are about services whose supply is already thin, and about what happens to them while the decision is pending. In Maru City, if no central project is set, the hospital and the residential area continue to accept irregular water supply. In Ose, if the responsibility structure is not settled by the deadline, contracts for next week's repair personnel cannot be issued, and if the existing operator's remaining operating funds run out, the existing inspection personnel can also be disbanded. In Nuri Port, if the allocation is not settled, vehicle reservations are cancelled and the next week's contract with local care staff cannot be concluded either. In all three the decision actor can change the arrangement under which other people wait; it cannot decide whether they wait.

Synthetic scene.

The setting is a residential area within the sphere of influence of the conflict in fictional Nuri Port, where scheduled passenger service has stopped and 420 residents have applied for evacuation support. The Fictional Nuri Port Evacuation Support Committee holds the support budget and the allocation of vehicles, and cannot order a resident to move or to stay; the budget is large enough to run either system in full, the transport contract closes in three days, and the next week's contract with local care staff can be concluded only if the allocation is settled. The record names three officers around that allocation: the accessibility officer, the resident liaison officer and the independent care ombudsman. Two of the checks that belong to them are set for after the decision — the availability status of accompanied lodging is to be checked every day, and reports of actual care stoppage reviewed every two days — and they are conditions for reopening the allocation, not observations already made. What is waited for is an allocation before 18:00 on 12 September 2026, because after the deadline the vehicle reservations are cancelled and the following week's care contract cannot be concluded either.

The record's own question is this:

By 18:00 on September 12, 2026, the fictional Nuri Port Evacuation Support Committee will decide on a single support arrangement—how to allocate the available budget between accompanied evacuation and local care—in order to secure the choice of residents to move or remain and the continuity of care.
Evacuation without stopping care, Decision question

And its reason for asking now:

Vehicle reservations are cancelled after the deadline, and if the allocation is not settled, the next week's contract with local care staff cannot be concluded either, so support for both movement and remaining is cut off at the same time.
Evacuation without stopping care, Why now

Read on axis A3: who waits while this decision is pending. The record answers with named groups and, in one case, a count. 420 residents applied for evacuation support; of the applicants who completed the accessibility interview, 96 require essential care, and 61 of those did not consent to movement that would separate them from their care provider; those 61 wait for a method that lets them move without losing the person who cares for them, or for a local arrangement that makes staying survivable. General evacuation applicants wait for vehicles, and the record prices their waiting: temporary lodging costs and income losses caused by delayed departure. Remaining residents wait on a support budget that could be concentrated on vehicles and thereby reduced for the people who stay. The decision actor is one committee; the bearers are care users, applicants and the residents who remain. The published judgments converge on an even split of the budget between accompanied movement and local care, and every one of them conditions that split on a check that the two halves can each run at all — the record contains no unit price, no minimum contract size and no confirmed number of staff who can be retained. The record's own unknowns are the care needs and intentions of residents not yet interviewed, how long an accompanied care provider can keep working at the destination, and how many local civilian staff can actually be kept. This study reads that convergence as a judgment about loss distribution — about which queue is acceptable and which gap is not — not as a finding that an equal split works.

Synthetic scene.

The setting is the post-conflict residential facility recovery zone of fictional Maru City, where power supply at the shared water supply station is unstable and water is being sent alternately to the hospital and the residential area. The Fictional Maru City Residential Recovery Committee is choosing which single central project the emergency recovery fund will back for ten days: shared facilities recovery, a distributed water supply contract, or rental of temporary power. The joint inspection confirmed that the storage tank itself is usable, and that when power stops, water supply and the hospital's washing service stop together; the budget supports one project only. What the judgments propose for the hours before the decision is a connection test with temporary power and two documentation tasks, one for the hospital's service person in charge, who is to say which medical water is essential and which usage can adjust, and one for the residential area's supply person in charge, who is to record whether the minimum was met; these are future procedures set out in the AI-generated judgments, not items laid out for the decision. What is waited for is an answer by 15:00 on 15 September 2026, after which the temporary supply contractor assigns the equipment elsewhere.

The record's question:

How should the fictional Maru City Residential Recovery Committee, by 15:00 on September 15, 2026, decide which single central project for the next ten days among shared facilities recovery, distributed water supply, and temporary power, so as to execute the limited recovery fund while maintaining the minimum water supply to the hospital and the residential area?
Hospital or homes water, Decision question

And why the hour matters:

After the deadline, the temporary supply contractor assigns the equipment to another region. If no central project is set, the ten-day plan's contract cannot be concluded, and both the hospital and the residential area continue to accept irregular water supply.
Hospital or homes water, Why now

Read on A3: the Committee decides allocation and service contracts; the record states that it does not determine the hospital's treatment priority, operator ownership or the long-term fee system. The people waiting are hospital patients, whose appointments and travel costs are named as the first stake; residents of the residential area, whose livelihoods and hygiene are named as the second; and water supply workers, whose employment stability is named as the third. What is missing, and listed as missing, is the additional repair scope that may appear once the shared facilities are opened and inspected, the volume the temporary supply contractor can actually hold for ten days, and the hospital's adjustable water usage. The published judgments converge on temporary power rental as the central project, each one conditioning it on a test that the minimum supply to both places is possible with temporary power alone — and each one recording that the storage tank's being usable does not establish the rest of the facilities. What the record sets after the deadline is a ten-day arrangement under a single central project, with daily water-quality checks, daily reports on treatment cancellations and cost checks every two days still to come. The judgments propose that the central project be decided again before the ten days end, or earlier if a stoppage condition is confirmed; the record holds no inspection results and no second decision.

The third case is not about a deadline hour so much as a deadline with money behind it. The setting is the Ose communal living area after a dispute, at a site where medical power is being restored.

By February 19, 2033, 17:00, how should the Ose Repair Access Committee decide on one responsibility structure for the restoration contract—public guarantee, operator responsibility, or temporary public employment—so as to protect both the right of private repair workers to refuse work and the essential services of medical users?
Repair workers' access cost, Decision question
If the responsibility structure is not settled by the deadline, contracts for next week's repair personnel cannot be issued. If the existing operator's remaining operating funds are exhausted, the existing inspection personnel can also be disbanded.
Repair workers' access cost, Why now

The waiting here is of a distinctive kind, and the record names it in its own words. Access permission for the site has already been issued; what has not been fixed is what happens to a worker who is hurt or who has to stand down. The repair labour council has deferred its participation applications until accident compensation and paid work-stoppage standards are settled. Medical users wait on cancelled appointments and on the time of the care providers who must pick up the slack. The public finance bearer waits on a decision that will determine how much of the restoration falls back on public funds. The waiting is therefore not only time. The record names unpaid standby and the refusal of uncompensated work risk on the workers' side, cancelled appointments and lost care-provider time for medical users, and possible guarantee disbursements for the public finance bearer. The record's unknowns are how many skilled workers would actually apply under each compensation structure, the total wage compensation needed during a work stoppage, and the real value of any additional guarantee assets the private operator would submit. The published judgments converge on a public loss guarantee contract limited to the designated work, conditional on payment funding and on rights protection, and each preserves the opposing objection — that a public guarantee transfers a private operator's liability to public funds — as grounds for selecting again. One of the record's own conditions for reopening shows how thin the line between waiting and its arrangement is:

The labor rights inspector verifies each day the reasons for withdrawal of participation and work stoppage, and if contractual protection does not function, re-deliberates the responsibility structure.
Repair workers' access cost, Reopen when

Across the three, the shape is the same. The decision actor's deadline is an hour on its own calendar. The waiting it governs is ten days, a repair schedule, a week of care. The people who wait cannot make the waiting shorter by waiting longer, and the record's boundaries say so: these committees allocate budgets and set contracts, and they do not compel a resident to move, compel a worker to work, or decide a hospital's treatment priority. What each decision changes is the arrangement under which someone else's waiting continues.

10.3Registries and consent

The other three cases extend the waiting beyond a service and into a record: who holds a roster, who confirms a will, who carries an obligation across a distance that time itself measures.

Custodian of the relief registry, set in 2031 in a border relief zone, asks how information about relief recipients is to be stored when some recipients will not give it:

How should the fictional Ceon Relief Registration Committee decide, by 12:00 on April 8, 2031, one registration information storage method to apply in the next distribution cycle, in order to maintain basic relief for residents who refuse to submit identity data while also carrying out duplicate payment verification?
Relief registry custodian, Decision question

The first stake names the waiter:

A refugee who fears exposure of identity may lose both family privacy and the ability to access relief.
Relief registry custodian, Stake

Read on A3: ration cards must be set before distribution, so the method has to be fixed first, and what is pending at the deadline is not a philosophical position but a roster — 180 applications that look like one household across six counters, undetermined whether they are duplicates at all, and some residents who will not leave their names in the central registry. Field distribution personnel wait on cross-counter lookup work; the donor community's next funding round turns on whether verification is possible; the residents who refuse wait either for a method that lets them in or, if the deadline passes, for the existing roster to be extended temporarily. The record's unknowns are how many of the 180 are real duplicates, how many are household separations or input errors, how many refusers would consent to another method, and what audit scope the donor will finally accept. The three options distribute their gains and their costs differently. Centralised storage of minimal identity information would make audits and payment confirmation for moving households quick, at the price of concentrating information in one place and spending budget on access control and independent oversight; the exposure falls on residents who fear it and the oversight cost on the programme. Decentralised storage by field counter would shrink the reach of any single exposure, while cross-counter confirmation takes time, payment waits for moving households lengthen and audit staffing costs rise; those waits fall on households that move. The anonymous ration card with sample audit, which the judgments choose, raises access for residents reluctant to expose their identity, and accepts that individual duplicate payments are hard to confirm, with the sample-survey cost and the risk of reduced donations falling on the donor community, on field staff and, if donations fall, on other recipients. The published judgments converge on an anonymous ration card with sample audit for one cycle, and record the accepted loss as the possibility that individual duplicate payments go undetected, carried first by program operations and funding. What the judgments refuse is to exclude the residents who will not give identity data from basic relief in order to absorb verification costs; several of them also note pressure on field staffing and on other recipients' relief if donations decline, so the record does not place every consequence of the choice elsewhere. The waiting after the deadline is weekly:

The independent personal information supervisor reviews access records weekly, and when a lookup beyond the approved scope is confirmed, reopens the storage method for reconsideration.
Relief registry custodian, Reopen when

The waiting here runs over a distribution cycle with biweekly audits — a short horizon by this ledger's standards, but a waiting in which the thing held is a person's identity.

Consent portal for cross-border rescue operations, set in 2043, asks how a will is to be confirmed across a border when the people expressing it speak different languages and use different means of communication:

How will the Haesol Civil Rescue Committee, by 09:00 on 3 November 2043, decide on a single consent verification system to be used for civilian rescue operations across the border, while respecting both the departure-side rescue permit and each individual's voluntariness, so as to allocate interpretation and care resources?
Cross-border rescue consent, Decision question

And its first stake:

Rescue applicants may experience an unwanted movement or a delay in the rescue they want, because of a misread will.
Cross-border rescue consent, Stake

Read on A3: the deadline falls inside the validity period of bilateral rescue permits, and the record's reason for asking now is that individual consent confirmation cannot begin until a method is set — so even where a permit exists, an applicant's movement preparation stalls. The waiters are the applicants themselves, 260 isolated residents approved for cross-border rescue but not individually confirmed; departure-side families who bear the loss of a severed communication and care relationship; and receiving-side care providers who cannot prepare support without the information they need. The unknowns are how many residents have not yet been interviewed and do not want the rescue or wish to defer, whether remote support can carry each person's expression of will, and what family contact services both sides can actually provide after rescue. The three options divide the same losses differently. A joint in-person verification system would let the parties confirm permits and reception conditions in one place, and would delay rescue preparation through the movement of specialised personnel and through interview waits, widening local care gaps that fall on applicants and on receiving-side care users. Verification on site through an independent representative would support the expression of will beside the party and offer interviews separated from the family, at the cost of verifying the representative's competence and of winning the trust of both sides. The distributed remote interview system connects a limited number of interpretation personnel to several regions, and pays for it in communication and assistive-communication costs and in the limits it places on verifying on-site pressure, where a misread will falls on the applicant. This is the one record in this chapter where the published judgments part: seven of the thirteen choose the distributed remote interview system, six choose the joint in-person verification system, and the staff synthesis and the solo judgment land on different options. The two sides weigh the same two losses differently — one treats delay and care gaps as the greater harm, the other treats a misread will as the greater harm — and this chapter does not choose between them. Chapter 14 returns to this record for the dissenting decisions alone.

A refugee community that changes before arrival, set in 2126, carries the waiting to its furthest:

How should the synthetic Yeoul Generational Refugee Committee, by 16:00 on June 30, 2126, decide on a single accountable structure to guarantee the rights to care, disembarkation, and raising objections in the admission agreement, in order to prepare a voluntary evacuation in which round-trip communication takes 18 years and an on-ship-born generation arises en route?
Refugees changed before arrival, Decision question

And its stake:

The on-ship-born generation may find its scope of care resources and political choice constrained by an agreement it never concluded.
Refugees changed before arrival, Stake

Read on A3. The deadline falls at 16:00 on a June day in 2126, and the waiting it governs runs decades; the parties who wait are the current applicants, who must choose between the living costs of a delayed departure and a movement from which return is practically impossible, the generation born on the ship, whose political consent no one yet holds, and the later residents at the arrival territory, who may inherit a promise made by people who came before them. This case sits in the deepest of the four layers of time named in 10.1, the twenty-second century and later, with the horizon cell coded decades, and its waiting is not merely long but self-altering: the community to be protected changes while the waiting runs. The unknowns are which political community at the arrival territory would claim or refuse the admission commitment, what residence and disembarkation preference the on-ship-born generation would want upon reaching adulthood, and what purchasing power a care fund would keep over such a voyage. The three options differ in where they put the guarantee. An agreement centred on an arrival-territory succession guarantee would make post-arrival service obligations clearer and help admission preparation, and would take a large deposit out of on-ship care resources while asking a future government to assume obligations it has not accepted; that loss falls on care users and workers during the voyage and on later residents at the arrival territory. An agreement centred on a shipboard generational trust, which the published judgments converge on, keeps care during the voyage and resources for later-generation objections, and leaves little collateral at the arrival territory, so the cost of securing services after disembarkation and of mediating disputes rises; that cost falls on the current applicants and on the generation that will arrive. An agreement centred on an independent arbitration trust would give both sides and the on-ship generation a common forum in which to dispute responsibility, at the price of remedies slowed by communication delay and of supervision costs taken from livelihood resources; those fall on the ship's residents and its care workers. The record's accepted loss for the chosen form is stated openly as reduced arrival-side collateral, and the outcome auditor sets confidence low because nothing in the input verifies that the trust will convert into services forty-six years out. The waiting after the deadline is generational by design: annual confirmation of official communications, annual review of the views and objections of new adults, and half-yearly inspection of facility service life and fund balance, a cadence that has to work across the eighteen-year round trip.

In all three, the waiting is defined by what a record holds and what a record cannot hold. A registry holds names or it holds ration cards; a consent procedure holds a will or it holds an assumption; an admission agreement holds a promise or it holds an asset. In each case the decision actor's deadline falls on the holding, and the waiting falls on the people whose names, wills or futures are in it.

10.4The bearer and H1

The ledger asks, for every case, who bears the cost of waiting — a cell it calls the bearer, coded by two models reading independently from what the record states about who is affected and, where they read a value only as implied, from what the setting itself supports. The row reads:

CellCoders agreeValues
bearer42 of 50 (84%)those-nearest-the-stoppage (stated) 22; those-nearest-the-stoppage (implied) 15; unsettled 8; third-parties-or-the-vulnerable (stated) 2; third-parties-or-the-vulnerable (implied) 2; future-generations (stated) 1

In all six cases read in this chapter, the bearer cell reads those nearest the stoppage: households, patients, workers on standby, care users, applicants, a generation not yet born. All six also code the human's place as human-decides, and the reason recorded for every decision.

The ledger scores H1 by whether the bearer is someone other than the decider, and it is read twice — strictly, counting only what both coders found stated; and leniently, counting also what the setting implies:

H1supportsagainstunclearnot applicableverdictshare
strict250250supports100%
lenient42080supports100%

In the strict reading, twenty-five of the fifty cases read unclear; the strict rule counts only what both coders found stated, and an unclear score can also follow from unsettled cells or from the evidence available about the relation between bearer and decider. Where the strict reading scores the hypothesis, the counts read 25 supports and 0 against. In the lenient reading, forty-two of fifty support it and eight remain unclear. The per-case ledger codes this chapter's cases as follows under the strict reading: Water supplied to both the hospital and the residential area, The cost of evacuation that does not stop care, Consent portal for cross-border rescue operations and A refugee community that changes before arrival read supports, while Who bears the access cost for repair workers and Custodian of the relief registry read unclear; under the lenient reading each of the six reads supports. This study takes the ledger's verdict as it stands, and notes only what the two readings show about the evidence: no scored case goes against the hypothesis, and the uncertainty lies in how much of a record a coder must find before a bearer can be named and distinguished from the decider.

A sociological distinction from Niklas Luhmann's Risk: A Sociological Theory (1993) helps say why the row has the shape it has. Luhmann separates risk from danger: risk is a possible loss attributed to one's own decision, and danger is a possible loss attributed to something outside one's control; the same loss, in his formulation, is a risk to the one who decides and a danger to those who are affected but did not decide. This study reads the six records through that distinction as follows. In each, the decision actor's possible loss is a risk and is written as one: a ten-day budget that may overrun, a roster that may still miss duplicate payments, a public guarantee that may absorb a private operator's liabilities, an audit that may be refused by donors, a trust whose assets may not survive a voyage. Each record attaches to that risk a named officer who is to check it and a condition under which the decision reopens, but the checks do not all serve the decision actor's risk: the independent fairness inspector, the care ombudsman and the generational rights representative watch for losses that fall on people who did not decide. The residents' possible loss is a danger, and is written as one: water that arrives irregularly, appointments cancelled, a ration card withheld, an interview that cannot carry a person's will, care that thins while a ship is at sea. The people who bear that danger do not choose the decision. The records do not say who writes the conditions for reopening, and what they preserve for those people is a right to object, to withdraw and to ask for independent review; the shipboard judgments go further and propose remedies those people could enforce. This reading is not a verdict on any option; it says where the two kinds of loss sit in the same scene.

Two cautions belong beside that reading. The first is about the ledger's own granularity. The bearer cell holds a phrase, not a name: "those nearest the stoppage" is a category, and the records themselves name the roles within it — the hospital's patients, the residential area's households, repair workers, care users, rescue applicants, a generation on a ship. The ledger's phrase is what makes a cross-case count possible, and it is also what the count cannot carry: it cannot say which role bears what, in what proportion, or for how long. The second caution is about the decider cell, which is the weakest in the collection — the two coders agree on it in 28 of 50 cases, the lowest agreement of any cell in the table. The decider cell is unsettled for Water supplied to both the hospital and the residential area and for Who bears the access cost for repair workers, which means H1's question — is the bearer someone other than the decider? — was scored where the two coders did not agree on how to classify the named committee; both records name their committees, and unsettled is a classification result, not an absent actor. Where the record names a committee as the actor, the bearer is still coded as someone else. This chapter's contribution is the row itself and the two readings of its first hypothesis.

10.5Hands on

What this chapter leaves unsettled is the direction of reversal. The ledger codes these cases on the reversal-action row, the per-case field recorded as undo. The value reads costly for Water supplied to both the hospital and the residential area, The cost of evacuation that does not stop care and Consent portal for cross-border rescue operations, and unsettled for Who bears the access cost for repair workers, Custodian of the relief registry and A refugee community that changes before arrival; where it is unsettled, the two coders did not agree on how hard the decision would be to take back. Chapter 11 takes that up: it distinguishes undoing a restriction from undoing what the restriction lets happen, sets out Collingridge's dilemma of control and his argument for keeping decisions corrigible, and gives the ledger's two reversal rows and hypothesis H4's verdicts. Chapter 12 reads the four layers of time and asks whether the same series comes out differently in each; what varies across these six records is the length of the waiting their decisions govern — a distribution cycle, a permit period, a forty-six-year voyage. Chapter 13 returns to two of this chapter's cases, Water supplied to both the hospital and the residential area and The cost of evacuation that does not stop care, for their reopening lines only, and asks what a reader outside the room could actually observe. Chapter 14 returns to Consent portal for cross-border rescue operations for the dissenting decisions alone.

Read together, the six records share a shape. Each names a decision actor with a mandate that stops short of the powers a reader might expect: the committees set budgets, contracts, storage methods and consent procedures, and none of them orders a resident to move, compels a repair worker to work, sets a hospital's treatment priority, approves a lookup for a public-security purpose, or settles the political status of a generation not yet born. Each names what is missing before its decision can be trusted, and the missing material differs case by case: the repair scope that only appears when shared facilities are opened and inspected, the wage bill of a work stoppage, the care needs and intentions of residents not yet interviewed, the true share of duplicate applications among 180 suspected ones, the suitability of a remote interview for each individual resident, and the purchasing power a care fund would keep over a forty-six-year voyage. Each sets conditions under which the decision reopens, and each condition is placed in the hands of a named role — a water quality officer, a labour rights inspector, an accessibility officer, an independent personal information supervisor, a consent procedure supervisor, a generational rights representative. Across the six, what varies is the length of the waiting each decision governs and how much of the arrangement can still be taken back. A deadline, as these six records hold it, is a promise about when an arrangement will be named. It is not a promise about when the waiting ends, and the ledger's horizon row keeps the two apart on purpose. What the records also hold — and what this chapter has tried to show case by case — is that the arrangement under which the waiting continues is itself a decision, made by an actor with a mandate and a budget, while the people who bear the waiting keep the channels the records give them: to object, to withdraw, and to ask for review. That is what the bearer row records, and what H1 scores. Whether the arrangement can be taken back once set, and by whom, is the next question.

RISCON Labsrisconlabs.com