Three Questions
The twenty-second case in the disclosure register is Case 9, Crystalline, 2035 — she never works in order. Kavya sorts by platform, then by year, then by whatever anomaly the column structure suggests. Tonight the anomaly is a date.
Signing date: April 14, 2035. Disclosure field date: March 29, 2035. The field reads: not applicable.
The field was marked not applicable sixteen days before the contract existed.
She reads it twice. Then she sets the laptop aside, gets water, comes back to the desk in the corner of her apartment, and reads it a third time. The date doesn't change. The field was excluded from the contract structure before the contract was drafted. Not blanked out. Not left empty. Designated not applicable as a prior determination, as a category decision, as a statement that this type of information was not the kind of information this field was for.
She writes in the margin: Category 3 — precondition blank.
This is her third taxonomy addition this week. She hadn't planned to build a taxonomy. She'd planned to read the register and note discrepancies. The categories emerged from the discrepancies organizing themselves, the way a problem you look at long enough eventually reveals the shape of the problem underneath.
Category 1 she named in committee this morning: the original blank column. A platform standard — the blank as default, replicated across thousands of contracts, no single decision point, no moment of choosing. It is a convention in the precise sense: something true because everyone treats it as true, with no origin anyone can point to. The blank column existed because the blank column had always existed. The committee got this category. And did you know? she had asked, and the chair had said: We do not have a prepared response. That question is in the record now. It traveled from a notecard to a microphone to a transcript. It will be somewhere official for the first time.
Category 2 she found in Case 4: the retroactive addendum. Someone went back. After signing, after the contract was in effect, a platform filed a supplemental disclosure document that reclassified voice processing as compositional intent analysis and left the attributional field blank. The blank was not original. It was edited into place eighteen months after the agreement. This requires a specific actor, a specific moment, a specific decision made in full awareness of what the field meant and what leaving it blank would mean. Category 2 is not a convention. It is a choice someone made who understood exactly what they were choosing.
Category 3 is different from both, and stranger than either.
The Crystalline platform did not leave a blank. It did not retroactively create a blank. It determined, before the contract existed, that this category of compositional data was not within the scope of the field's applicability. The field was for a different type of information. The field did not apply here. Someone — a product team, a legal team, a platform architect — decided that the composer's process did not belong to the category of things the field was designed to capture. Not: we will not disclose this. But: this is not the kind of thing this field discloses.
This is not silence. Silence is a response to a question. Category 3 is a prior determination that the question doesn't apply.
She sits with this for a while. Outside it is late — Tuesday, after ten. The testimony was this morning: early start, committee building two transit lines away, four lines on a notecard, the question spoken into a microphone in a room that smelled faintly of floor wax and recycled air. She had come back from the committee building and eaten something she doesn't entirely remember and then opened the register at Case 9 because she'd left a flag on it two days ago for exactly this reason: the date anomaly. She hadn't known what it meant yet.
After the testimony she had stood outside the committee building for twenty minutes. Not because she was waiting for anything. Because the question was in the record and she needed a moment to stop carrying it. The committee chair's words: We do not have a prepared response. She had written them in the margin of her notebook immediately, standing on the sidewalk, because she knew she would need the exact phrasing later. We do not have a prepared response is different from We cannot answer. Cannot implies capacity. Does not have implies the answer exists somewhere and they do not have it yet. The distinction matters. She flagged the margin note.
On the transit home she had reread the four lines on the notecard. And did you know? The question had seemed, before she asked it, both too simple and too large. In the room it had felt neither — just a sentence ending with a question mark, traveling across a table and into a microphone. The committee received it. The record received it. It is no longer hers to carry.
Now she does.
The committee question — And did you know? — was answerable only by Category 1, and only loosely. You cannot know a convention the way you know a decision; it accumulates rather than occurring. The question she asked this morning was too wide for the category it most clearly addressed, and it was the wrong question entirely for Categories 2 and 3, which require knowing that a specific person made a specific choice at a specific moment in time.
She writes three new questions on the page after the notecard.
Category 1: When did the blank column become platform standard, and was that decision recorded? This asks for an origin. A moment when convention was established, or a process through which it emerged without being established. Even if no moment exists — even if the convention simply accreted over years of default-following — the absence of a recorded decision is itself significant. The committee heard a version of this question this morning. The record will carry it forward.
Category 2: Who authorized the retroactive classification, and what documentation exists for that authorization? This asks for an actor and a paper trail. It is the narrowest question. It has a determinable answer or an absence of a determinable answer, and either way the answer is an answer. A platform that cannot produce documentation for a retroactive classification has told you something by failing to produce it.
Category 3: What determined that this field was not applicable to this contract, and was that determination reviewed before the template was deployed at scale? This asks for a design decision. It is upstream of the contract, upstream of the platform relationship, upstream of the composer. It belongs to the system architects and the product team, not the account managers. The answer might be: the template was standard, nobody reviewed it individually, the designation was inherited from an earlier template structure. That answer is also an answer.
She has been asking the wrong question for the wrong category. This is not a mistake — the committee question mattered, it is in the record, it cannot be unasked, and Category 1 is real and worth naming publicly — but it was a beginning, not a framework.
Thirty-one cases still unread. She wonders how many will be Category 3. The Crystalline 2035 contract was large: forty-three composers, sixteen catalog arrangements. Platforms share template structures. A template that designates certain fields as not applicable by default would appear at scale, across multiple clients, potentially across multiple platforms that licensed the same underlying contract architecture. She makes a note to search the register for other Crystalline contracts by template version rather than by year.
She opens Case 10: SONA-Artisanal, 2031. The blank column date matches the signing date exactly. Category 1. Convention. She writes it in the margin.
Case 11: Vellichor, 2030. Blank column date: fifteen months before signing.
She pauses. Fifteen months is long. Long enough to be a template decision made during early platform development rather than a contract-specific designation. Or long enough to reflect protracted negotiations that began fifteen months before the agreement was finalized — in which case the blank column date might simply be the date a draft template was created, not the date any designation was made. She writes: Category 3? and leaves the question mark. The question mark means she will return.
Case 12: Crystalline, 2033. First generation, before the 2034 reclassification event — the retroactive addendum she documented in Case 4, the one that reclassified voice processing as compositional intent analysis eighteen months after the contract was signed. This 2033 contract predates that event. The blank column date is identical to the signing date. Category 1. Convention, inherited without decision.
She pauses on Case 12 longer than it warrants. If the 2033 contract is Category 1 and the 2034 retroactive addendum is Category 2 and the 2035 contract is Category 3, then Crystalline, as a platform, managed to produce all three categories of disclosure failure in a three-year window. This is not a story of one choice. It is a story of a system that learned three different ways to leave the same field blank.
Cases 13 and 14: both Category 1. Then Case 15: SONA-Artisanal, 2034. Blank column date eight months before signing.
She writes: Category 3 candidate and flags it for cross-reference with the Crystalline 2035 contract. Two platforms. Two precondition blanks. Different signing dates, different composers, different contract sizes — but the same architectural decision made before any agreement existed. If a third platform shows the same pattern, the precondition blank is not a Crystalline-specific choice. It is a template practice distributed across the industry.
At 11:14 PM she closes the laptop. Nineteen cases done tonight. Thirty-two remaining.
The notecard is still on the desk. And did you know? The question the committee has no prepared response to. That is accurate — there is no response available for a question about a convention that accumulated without anyone deciding it. The convention is true by collective default. No one chose it and so no one can answer for it directly. The committee's non-response is not evasion; it is the honest state of Category 1.
For Category 2 the question has an actor. For Category 3 the question has a design process. Neither requires the word know in the question. Knowing isn't the right verb. Deciding is. Determining is. The question that belongs to Category 2 is: who decided, and when. The question that belongs to Category 3 is: who determined that this was outside the scope, and is that determination visible anywhere in the design record.
She has, tonight, built a taxonomy she did not have this morning. She did not build it by thinking about it. She built it by reading nineteen cases and writing in margins.
Tomorrow there will be thirty-two more cases. She will read them the same way: by whatever anomaly the column structure suggests first. If there is a fourth category in the remaining cases, the margin note will tell her what it is before she has a name for it.
The three questions are on the page after the notecard. One of them is already in the record, inscribed in official language she does not control. Two of them are not yet. She does not know which of the remaining cases will make them necessary.
What she knows is that the first question — And did you know? — was the right question to begin with, even if it was too wide, even if the committee had no prepared response. You cannot ask the narrower question without asking the wide one first. The wide question establishes that there is a question. The narrow questions establish where in the system the answer lives.
She will bring all three to the committee. Not this week. Not until the register is done. The register is the foundation; the questions are the structure built on it. She cannot walk into a second committee session with three questions and thirty-two unread cases still flagged. She can walk in with three questions and a taxonomy of a hundred.
Tomorrow: thirty-two cases. She will read them in the same order she reads everything — by anomaly, by date, by whatever the column structure reveals first. If the taxonomy grows, she will write the category in the margin and name it when she has enough examples to know what it is.