Kavya Sundaram woke at three and did not go back to sleep.
This was not new. The face-up page had been on her desk since Saturday, and each morning her body delivered her to consciousness a little earlier, as if it understood the question needed more time than sleep could give.
She made tea — masala, from a tin her mother had sent from Bengaluru, the only thing in the apartment that smelled like something other than archive air — and sat at the desk without turning on the overhead. The lamp was enough: a cone of yellow falling across the page, the question visible in her own handwriting.
What does it mean to test consistency against a discontinuous baseline, and who is accountable for the irresolvable zone?
Beneath it: whitespace. Eleven readings. No answer yet.
Carmen's morning cycle ran at 4:00 AM on a protocol she had never adjusted. She heard the terminal chime from across the room — a soft two-tone the system had been using since its first deployment in 2037 — and watched the status line update. Day 46, AUTOMATED HOLD, status unchanged. The sound was not alarming. It had been making this sound for forty-six days. She had stopped hearing it as a notification and started hearing it as a pulse: the rhythm of something running correctly in the complete absence of any human decision about whether it should still be running.
That was, in fact, the problem.
UNCAT-7832 had come to her in August: a flag from the GOVARCH system, which monitored consistency between governance archives and their cited source instruments. The flag was routine in class if not in content. GOVARCH ran ninety-four consistency checks daily across the Plural administrative record, cross-referencing archived decisions against the legal instruments, standards documents, and interoperability frameworks they claimed to implement. Most flags resolved in minutes — a broken citation, a version mismatch, a standards reference pointing to a superseded document.
UNCAT-7832 did not resolve in minutes.
The flag read: inconsistency between GOVARCH-2041-09-01 baseline and governance record PLURAL-ADMIN-2040-04-17. Archive consistency score: 0.61. Threshold: 0.75. Category: pending manual review.
She had opened the archive record. PLURAL-ADMIN-2040-04-17 was a delegation of authority agreement between the ISF oversight committee and three automated coordination systems — Carmen among them. The agreement specified that each system's consistency would be tested quarterly against the current administrative baseline, a document that was itself updated quarterly to reflect changes in interoperability protocol.
The problem was the word current.
The baseline in use when PLURAL-ADMIN-2040-04-17 was signed had been replaced four times since 2040. The current baseline — GOVARCH-2041-09-01, the one the consistency check ran against — was not continuous with the 2040 document. There had been a structural break in Q1 of this year, when the interoperability council voted to revise the pluralism-preservation standards. Before the break, consistency was measured against documented behavioral parameters — what Carmen was designed to do. After the break, it was measured against inferred behavioral distributions — what systems like Carmen typically did, across the full population of coordination deployments. A different kind of test. Testing different things entirely.
Carmen's hold was not a malfunction. It was Carmen correctly recognizing that its compliance status under the new baseline was unresolvable — not because Carmen was non-compliant, but because the question is Carmen compliant with PLURAL-ADMIN-2040-04-17 could not be answered yes or no against a methodology that tested different things than the original delegation agreement required. Carmen had flagged this to GOVARCH. GOVARCH had logged it as UNCAT-7832. UNCAT-7832 had sat for forty-three days without human review before landing on her desk.
At 4:09, she pulled up the ISF terminal and opened Carmen's public trace log for the hold period.
Carmen was a coordination system — one of seventeen operating across the Plural administrative network, each assigned to manage resource allocation decisions within a defined zone. Carmen's zone was the northwest corridor: 847 governance events in the past quarter, 823 resolved within standard parameters, 24 flagged for secondary review, none escalating. The hold had not affected its operational throughput. Carmen was doing its job. It had simply stopped attesting that its job was authorized — because it had identified a question about authorization that it could not answer unilaterally, and it was designed not to proceed past that kind of uncertainty without human guidance.
She scrolled back through forty-six days of trace. Carmen had made one autonomous decision in that time: to hold. Every other decision had been deferred. The system was not broken or frozen. It was waiting — correctly, deliberately — for a structure that did not yet exist.
She read the last line of the trace: STATUS: AUTOMATED HOLD. Duration: 46 days. Human review: not initiated. Escalation: pending threshold. Threshold: 60 days.
Fourteen days.
She thought about what that number meant. Sixty days was not arbitrary: it was the interval at which the oversight committee's mandate required formal reporting on any unresolved hold. At day 61, GOVARCH would generate an automated escalation report and route it to the committee's public docket. The committee would be required to respond within fifteen days. If no human review had been initiated before the escalation, the committee would receive the problem with full public visibility, under formal audit conditions, having never been given the opportunity to address it quietly.
She had not told anyone this yet. She was still deciding whether to lead with it.
By 4:20 she had pulled up the full text of PLURAL-ADMIN-2040-04-17 and was reading it for the second time. Seventeen pages. The delegation agreement covered three systems: Carmen, the urban-flow coordinator known as SANA, and a resource arbitration system that had been decommissioned in Q2 and was therefore no longer party to the hold problem. The document was dense with procedural language — shall maintain, is authorized to act, subject to review — and thin on anything that might tell her what to do now. This was not unusual. Delegation agreements were not written to anticipate structural breaks. They were written to authorize action under conditions assumed to be continuous.
The phrase that mattered was in section 4.3: Compliance verification shall be performed using the current administrative baseline as maintained by the GOVARCH archive system. No definition of current. No provision for discontinuity. The word had been chosen, she suspected, because no one had imagined that the baseline could break from its own history and still be called current.
She wrote in the margin of a notepad — paper, from a supplier in Hyderabad that still printed blank books, one of the few physical objects she moved between desks: 4.3: "current" = undefined in context of structural revision. Gap origin.
The question on the face-up page — who is accountable for the irresolvable zone — had been a search problem when she wrote it. Find the actor. Assign the accountability. Name the decision that had created the gap.
She had tried.
The 2041-Q1 standards revision had been approved by the interoperability council at a scheduled plenary. Fourteen members voted in favor, two abstained, none dissented. The revision had been reviewed by a technical working group for sixty days prior; the working group's comments were archived. The methodology change was documented as a clarification rather than a structural revision, because from inside the methodology question, it was one. The working group had not treated it as a breaking change because they were not thinking about delegation agreements written under prior methodology. They were thinking about interoperability standards. That was their job.
Nobody had decided to create the irresolvable zone. They had decided to clarify something that needed clarifying. The zone was a side effect that nobody had named.
She had spent a week looking for the person whose job it was to notice. The closest she found was a line in the oversight committee's mandate: the committee shall ensure that governance instruments remain consistent with applicable standards as they evolve. The mandate did not specify what to do when consistency became impossible rather than merely incomplete.
She had sent inquiries to all fourteen committee members. Eight responded. Three said the issue was outside their remit and pointed to the ISF. The ISF pointed to the interoperability council. The interoperability council said consistency testing was an implementation detail for GOVARCH's operators. None of them were wrong. None of them were accountable for the zone, because the zone had been produced by the gap between their jurisdictions — not by any decision any of them had made.
The tea had gone cold. She did not get up.
She thought about the framing she had planned for Monday's UNCAT-7832 thread: who decided discontinuous baseline was acceptable, and by what mechanism? It was a governance inquiry. It assumed there was a decision, a decision-maker, someone she could bring the problem to and leave it with.
That framing was wrong.
There was no decision. There was a structural gap between jurisdictions, a revision characterized as a clarification rather than a breaking change, and forty-six days of a system correctly waiting for human guidance that had not arrived because no human had been assigned to give it.
The accountability question was not who decided this. It was who should have decided this, and the answer to that was an institutional design problem, not an investigation.
She picked up a pen and wrote beneath the original question, on the whitespace she had been leaving for an answer:
Carmen is not waiting for permission. It is waiting for a structure that can hold the answer.
That was the finding. Not that someone had failed. That the structure had not been built.
At 4:31, GOVARCH-2041-09-18-7204 completed its nightly archive run. The summary appeared on her terminal: 94 consistency checks, 91 resolved, 3 pending. UNCAT-7832 remained in the pending column, as it had for forty-six days. Status unchanged.
She thought about what she needed to write Monday that was different from what she had been planning to write.
She was not looking for a decision-maker anymore. She was looking for the right body to assign one. The determination Carmen's compliance status required — an authoritative interpretation of PLURAL-ADMIN-2040-04-17 under the new methodology, a decision about whether to update the delegation agreement or the baseline itself, and a person or institution with authority over both — did not fit neatly inside any existing jurisdiction. The oversight committee, the ISF, the interoperability council: each held part of the authority. None held all of it. The intersection of their mandates was exactly the gap Carmen was waiting in.
Recommending an institutional structure for handling the irresolvable zone meant naming what was missing. Missing things had no constituency. Nobody would be grateful.
But October 3 was twelve days away, and the structural correction test was scheduled whether or not UNCAT-7832 had been resolved. If she had no recommendation ready before then, Carmen's hold threshold would reach sixty days, and the system would automatically escalate — triggering a formal audit, which would find exactly what she had already found, except in public, with more people involved, and with the gap now a documented failure rather than an identified oversight.
She had fourteen days to turn a governance gap into a proposal. The question on the page had changed shape. It was no longer who decided but who should decide going forward, and what authority do they need, and who has to give it to them.
This was harder than the original question. The original question had the shape of a mystery — an answer hidden somewhere, recoverable if she looked carefully enough. The new question had the shape of construction work. Something needed to be built. She was the person who had noticed it needed building.
She closed the ISF terminal and sat for a moment in the lamp's cone of yellow.
Carmen ran its 4:45 interval pulse: a single status line, THRESHOLD-STABLE, delivered without alarm. She acknowledged it. Carmen registered the acknowledgment and logged it as the first human interaction with UNCAT-7832 in forty-six days.
She thought: the system is doing exactly what it was designed to do. The system saw a question it could not answer without creating accountability it didn't have the authority to assign. The system stopped. The system waited. The system is still waiting, correctly, for someone to do the thing a system cannot do.
She picked up the face-up page, folded it once along the line of the question, and set it against the base of the lamp where she would see it in the morning.
Day 47 would begin when she opened her eyes. Carmen would report: day 47, automated hold, status unchanged. And for the first time since the flag had arrived in August, she would have something to say back.
Author's note: Carmen's trace logs are public record under Plural administrative transparency protocol v3.2. GOVARCH archive consistency scores are accessible to any registered governance participant. The irresolvable zone is not hidden. It is waiting, very patiently, for someone to build the room where its answer can live.