- Status: accepted 2026-10-12, by Alessandro Prandini, the text first and before any code, the way ADR 0035 and ADR 0048 were. Nothing in it is implemented. What it decides was ruled before it was written, in discussion, on 2026-09-30, and is recorded here as ruled (§1 to §5), except two decisions this record takes itself, both in §5 and both of 2026-10-12, marked decided here where they are made: the kind recorded beside the identity, and the reason the source is recorded. The text was rewritten from what was decided since, before acceptance: §5, and dated notes where another record has answered a point it left open. The three problems it names (§6 to §8) are not resolved here, except where those notes say so, and Not decided here lists what stays open; none of it blocks acceptance
- Shipped: unreleased
- Date: 2026-10-01
- Opens: nothing on landing. No
SCHEMA_VERSION, noOUTPUT_VERSION, noREGISTER_VERSION, noJOURNAL_VERSION, noLEDGER_VERSION, no migration - Requires, at implementation, each as far as it is ruled and no further:
- a gesture at a page served at the data owner's side, by which a person at the software house asks to see one case in clear (§1);
- a reason that the gesture cannot be made without, with a default the data owner's side computes (§4);
- a trace of every disclosure that names the person, with the source of their identity (§3, §5). Where the trace lives is not decided (Not decided here)
- Assumes: ADR 0002 §2 (the
payload stays where it is born), §3 (widening what leaves a perimeter is a
change somebody writes and a reviewer sees) and §4 (a
Comparisondoes not cross a boundary); ADR 0034 §1 (the store is in the end company's perimeter) and §6 (the name table is the re-identification key); ADR 0035 §4 and §11 (a record of a removal, and what such a record concentrates); ADR 0036 §7 (the process that owns the table serves the pages); ADR 0037 §4 and §7 (who elects, and the page where the text is read); ADR 0038 §2 and §3 (a served projection, and shape C of the comparison) - Touches, in
CLAUDE.md's fixed section: decision 9, and §8 says how. A disclosure puts a case's payload in front of the software house. That payload is what decision 9 keeps where it is born, and nothing in the suite's code declares the crossing. This is why the ruling needs a record and cannot be implemented as an issue. The tension is named in §8 and is not resolved here - Number: 0039. Swept on 2026-10-01, before a line was written, across
origin/main(aadf75f), every local and remote branch and tag, thedocs/adr/of every sibling worktree, the stash (empty), the open pull requests (none), and the site repository's refs. The highest number taken anywhere is 0038
Context¶
ADR 0038 stated one ruling and left its other half for later. Its status line records a ruling made in discussion on 2026-09-30. Pages served to the software house show projected documents by default. "Seeing a case in clear is a disclosure that is asked for, seen and recorded." ADR 0038 built on the first half. Its §2 says "'no more without the act of disclosure' is already ruled", and its Not decided here leaves the act itself open: where its record lives, whether a disclosed case stays disclosed, and whether the client is told. This record is that act.
What the software house may see did not narrow, and what it is shown unasked did. The ruling that stands behind both halves, made in discussion and amended on 2026-09-30, is this: the software house can see everything, and disclosure on record is how. What it is shown by default is the projected document. A case in clear is a second act, separate from reading, and it is recorded.
It repaired an earlier ruling, made the same day, that described a loop that
cannot run. The earlier ruling allowed and declared a telephone loop: the
software house sees a case degrade on a projected page, calls the client, and
the two talk about it. The correction came the same day. To telephone, the
software house has to be able to say the question and the two answers, and
the projection removes exactly those (ADR 0034 §4, §5 and §8). With a token
alone, the call is "case cap-7f2a degraded", and nobody at the client
knows what that is. Disclosure on request is what replaced it.
One word, two meanings, and this record uses only one. Disclosure is
already a type: what a suite declares, in code, that may cross a boundary (ADR
0002 §3, ADR 0003). Disclosure on request is not that type. It is an act a
person makes at a served page, for one case, with a reason. Where this record
means the type, it writes Disclosure in code. Where it means the act, it
writes disclosure or a disclosure.
Decision¶
§1 to §5 were ruled on 2026-09-30, in discussion. They are recorded here, not decided here, except two blocks of §5, decided here on 2026-10-12 and marked where they are.
1. The software house can ask to see one case in clear, and it sees it¶
A person at the software house can ask, at a page served at the data owner's side, to see one case in clear. The case is shown.
The unit is one case. A disclosure is never a run, and never a suite.
Noted 2026-10-06: amended in part by ADR 0037, accepted that day, at a served review page only (0037's Amends and §7). §1: at the review page the unit of a disclosure is the opening of the page, not one case; a list of N flagged answers is not N disclosures. §6: of the two alternatives §6 names and does not choose, neither is taken: the review page is not an exception to the projected default, and it is where a disclosure happens, a software house's person opening it being the recorded act. §6's default reason, which has no subject at review, is not touched. The text here is kept as written.
2. The end company does not authorise case by case¶
No person at the end company approves a disclosure before it is made.
The reason is availability, not trust. Authorising in advance needs somebody at the client to be available at the moment the software house needs them. If nobody is there to answer the phone, nobody is there to authorise either. A permission that waits for a person who is not there is a disclosure that does not happen, or that happens by some other route that leaves no record. The ruling compares this with the link and finds the same defect in both. Which link is not written down with the ruling. So this record states the defect, and does not name the other half of the comparison.
3. The control moves from permission to trace¶
The end company cannot stop a disclosure. It can read every disclosure that was made.
What the trace is for: it is what a controller shows an authority. My supplier saw these eleven cases, on these dates, for these reasons. The client gives up preventive authorisation, and it receives the trace in exchange. A trace that cannot say who looked is worth nothing as a trace, and §5 is what makes it say so.
4. The reason is a required field, with a default the data owner's side computes¶
A disclosure cannot be made without a reason. The reason has a default, and the default is a fact about the case, computed where the data is: "worse in the run of
against the reference" .
- Not a generic sentence. A default that fits every case is the value nobody changes, and then the reason stops informing.
- The data owner's side knows whether the case degraded against the reference, so the default is that fact. The software house changes it only when its reason is something else.
- The consequence that makes it work. If the software house asks for a case that did not degrade, the default does not apply, and it has to write a reason. So the obligation to explain falls exactly on the cases somebody might want to look at without an obvious reason.
5. A disclosure names a person, with the source of their identity¶
The ruling in the box, and the paragraphs not marked otherwise, were ruled later the same day, 2026-09-30, repairing a gap in §3. The two blocks marked "decided here" were decided on 2026-10-12.
A disclosure is attributed to a person, not to a caller's key. The record says where that person's identity came from.
Why the repair was needed. A machine at the software house authenticates with a credential of its own. A disclosure attributed to that credential would name a party and no person, and §3's trace would lose the one thing it gave the client in return.
What attributes it. A person at the software house signs gestures as a local user of the process that serves the page. That is the default identity, which cannot be turned off. The record carries the source: a local user, and not the client's directory.
Decided here, on 2026-10-12. The record carries the kind beside the identity: a person or a machine. Today a disclosure is attributed to a person only, and the record still says so, in a field of its own. A reader must not infer the kind from the absence of something else, here from the absence of a key. And refusing the key is a rule, which can change, while the record is permanent: a line has to say what signed it without its reader knowing which rule held when it was written. ADR 0035 §4 records a decider's kind the same way.
Two words, kept apart. Kind and source answer two different questions, and this section gives each its own word, as ADR 0035 §4 does for a decider: - the kind is what signed the line: a person or a machine; - the source is where the identity comes from: which register issued the name, a local user of the process that serves the page or the client's directory.
This section never writes kind for a source. Kind has other meanings elsewhere in this corpus, a token's kind (ADR 0036) and a case's (ADR 0037); here it means only the first of the two above.
Decided here, on 2026-10-12. Why the source is recorded. The source says which register the name comes from, so that a reader does not have to infer it. It says no more than that: ADR 0037 §4, "The identity's source does not tell the parties apart." It is written on every line a person signs: the client reads which source the identity that signed the line comes from, and does not have to assume.
What the source does not state, and the cost of that. Whether the client
can revoke or verify that identity is not a property the source states.
source="local" names a register, not who administers it. So two
installations whose lines carry the same source can differ in whether the
client can withdraw that identity, and the record does not say which holds.
That is a matter of the contract between the parties, and no field of the
record carries it. A client reading a line learns where the name came from,
and not whether it can withdraw it.
Noted 2026-10-06: "by construction" no longer holds as written. Ruled
2026-10-05: whether the client can revoke a local user is not read off the
identity's source alone, and source="local" does not say which case holds.
A client-directory identity is still revocable by the client; it is no longer
the only one that may be. Who can revoke a local user is the question the
next paragraph leaves open, and it stays open here. The paragraph is kept as
written.
Noted 2026-10-12: the paragraph the note above is about was rewritten, and no longer says "by construction". What the note says is now in the text, under "What the source does not state". Its "next paragraph" is still the one after these notes, which leaves open who can revoke a local user. The note is kept as written.
What it does not say: who creates that local user and who can revoke it. That is open (Not decided here), and under this ruling it decides who can disclose.
Noted 2026-10-12: half of this is ruled. Ruled 2026-10-05: whoever owns the machine that serves the page administers its users, creating them and revoking them. Who can revoke a local user in a given installation still depends on the contract between the parties, and that half stays open. The paragraph is kept as written.
Problems this record names and does not resolve¶
Each of these was found after 2026-09-30. Each is written as a problem. None of them is resolved here.
6. The default reason has no subject at review¶
§4's default, "worse in the run of
This meets ADR 0037 at two places, and neither of them says anything about disclosure: - §4 lets the software house's person elect. - §7 says "the page is a review screen, and it is where the text is read."
A person cannot write an expected without reading the answer. A page served to the software house is projected by default. Either an election by the software house's person is a disclosure, case by case, with a reason the default never fills, or the review page is an exception to the projected default. Neither is written anywhere, and this record does not choose.
Noted 2026-10-06: ADR 0037 chose, at its acceptance that day — the note under §1 says how. The paragraph is kept as written.
Noted 2026-10-06, on the paragraph's first sentence: it claims more than the design supports. What a person must have read to write an expected is, in every case, the input. The answer is needed only when the expected judges a generated answer; otherwise the application's verdict stands in for it. So the conflict this section names is over the input, which is what a projected page removes, and not over the answer. The sentence is kept as written.
The default needs a comparison in clear, even where a case exists. "Worse … against the reference" is a fact only a comparison of the case in clear, made at the data owner's side, can establish. ADR 0038 §3 left exactly that comparison open as shape C, "new material, not a corollary", and said so of this default by name. §4's default rests on shape C, and shape C is not ruled.
7. The perimeter is not broken; it is consumed¶
Recorded 2026-09-30 as a consequence of §1, and left unruled by choice.
ADR 0034 §6 calls the name table the re-identification key. Its acceptance sidestepped counsel's question: "the committed file carries no text, so there is nothing in it to erase; erasure happens here, in this table, and what history keeps is tokens that point at nothing." Under the ruling on what the software house is shown, it no longer holds the whole table by default.
- A disclosure hands the software house one row of the table: the text a token stands for. n disclosures hand it n rows.
- The perimeter does not break. It is consumed. The question the pseudonymisation ruling and counsel's question need answered is no longer whether the software house holds the means. It is how much of them it has accumulated, one recorded row at a time.
- How many rows one disclosure hands over is not counted here. The ruling says one row. A case shown in clear also shows its group labels and its verdict names, and their tokens are shared with other cases (ADR 0036 §4). Whether those are rows a disclosure hands over is not ruled. Noted 2026-10-12: answered by ADR 0047 §4, accepted 2026-10-08. A row whose token is shared with other cases stays a token; a disclosure hands over the case's own row. The bullet is kept as written.
8. Fixed decision 9 and ADR 0002 §2–§3: payload crosses, and no code declares it¶
Decision 9 and ADR 0002 §2: the payload does not cross a boundary. ADR 0002 §3 adds that widening what leaves a perimeter "must be a change someone writes and a reviewer sees", in the suite's code, never read from the data. A disclosure shows a case's payload to the software house, and no change in the suite's code declares it. The widening is a gesture at a page, with a reason and a trace (§3, §4). It is not a line in a reviewed file.
What the rulings did instead. They put the control in the trace (§3), and the attribution in a person with a source (§5). Whether that satisfies the property decision 9 protects, or amends decision 9, is not decided here. Accepting this record cannot happen without deciding it. Decision 9's amendment of 2026-10-01 for ADR 0038 names the served projection. It does not name a disclosure.
Noted 2026-10-12: decided by ADR 0046, accepted 2026-10-08. The trace satisfies the property fixed decision 9 protects, and fixed decision 9 is not amended. This section's condition for acceptance is met. The section is kept as written.
What it touches¶
- ADR 0037 §4 and §7. An election by the software house's person reads text that a projected page withholds (§6). ADR 0037 has no place for disclosure, and this record does not amend it. Amended 2026-10-06 by ADR 0037, at its acceptance: 0037 now has one. Its §7 makes the review page the place where a disclosure happens, and it amends §1 and §6 here too (the notes there). This record still does not amend 0037.
- ADR 0034 §6. The table is the re-identification key, and a disclosure hands it out one row at a time (§7). §6's acceptance, "tokens that point at nothing", was written about the committed file. It is unchanged for that file. It does not reach a token whose row was disclosed: that token points at text the software house now holds.
- The ruling on what the software house may see, as amended on 2026-09-30. What the software house may see does not narrow; what it is shown unasked does. This record is the second act that the amendment names.
- ADR 0035 §11. That section names what a record of removals concentrates: beside a restored backup, a list of the people who asked to be erased. A trace of disclosures is a record of the same shape: an index of the cases the software house looked at, with dates, persons and reasons. Whether it concentrates in the same way, and where it should sit because of it, is not decided here. And a case that was disclosed and then erased: ADR 0035 §4 already says an entry never claims that the data no longer exists. A disclosure is one more place where that data survives, and it is outside the data owner's perimeter.
- ADR 0038 §2 and §3. §2's "no more without the act of disclosure" points here. §3's shape C is what §4's default rests on (§6).
CLAUDE.md's fixed decision 9 (§8).
Alternatives considered¶
Each of these was weighed in the 2026-09-30 discussion. This record records the weighing; it does not reopen it.
- The telephone loop. Allowed and then corrected the same day: it describes a loop that cannot run, because the projection removes what would have to be said (Context).
- Authorisation case by case at the end company. Refused in §2: it needs somebody available at the moment it is needed.
- A generic default reason. Refused in §4: a default that fits every case is the value nobody changes.
- Attributing a disclosure to the caller's key. Refused in §5: it names a party and no person, and the trace loses its worth.
Not decided here¶
Ruled 2026-10-12: none of the points below blocks this record's acceptance. Each stays open, with the condition written beside it.
The three left open by the ruling itself: - Where the disclosure's record lives. The ruling says it is not the deletion ledger of ADR 0035. Whether it is a third artifact is open, and so are where it sits, its retention, and who may read it. Noted 2026-10-12: ADR 0035, accepted 2026-10-09, keeps two deletion ledgers per tenant (§2); the ruling meant neither. The bullet is kept as written. - Whether a disclosed case stays disclosed, or whether the clear text is shown once. - Whether the client is told, and when.
Opened by what came after: - The default reason at review (§6), and whether an election by the software house's person is a disclosure. Noted 2026-10-12: the second half is answered by ADR 0037, at its acceptance on 2026-10-06; the notes under §1 and §6 say how. The default reason at review stays open. The bullet is kept as written. - Shape C of ADR 0038 §3, on which §4's default rests (§6). - Consumption (§7): how much of the table the software house may accumulate, and how many rows one disclosure hands over. Noted 2026-10-12: the second half is answered by ADR 0047 §4 (the note under §7). How much of the table the software house may accumulate stays open. The bullet is kept as written. - Decision 9 (§8): whether the trace satisfies it, or whether it is amended. Noted 2026-10-12: decided by ADR 0046 (the note under §8). The bullet is kept as written.
Not addressed by any ruling: - What a case in clear contains. Its input, the recorded answers, the judge's reasons, and its names, or a subset of these. Noted 2026-10-12: answered by ADR 0047, accepted 2026-10-08. The bullet is kept as written. - How the record names the disclosed case: by its token, or otherwise. And what that name means once the case's row is erased. - Who creates and revokes the local user that a software-house person signs with (§5), which decides who can disclose. Noted 2026-10-12: half of it is ruled (the note under §5's last paragraph). Who can revoke a local user in a given installation stays open. The bullet is kept as written. - How the gesture is protected against a request forged by another page. A disclosure is a gesture, and no gesture at a served page has that protection written down yet. - A disclosure through a snippet. ADR 0038 names #279: a line that hands over a case id in clear is either a disclosure or a token that no suite reads. This record does not rule which.
What this record does not claim¶
- That a disclosure can be prevented. §3 says the opposite: the end company reads disclosures, and it does not stop them.
- That the trace is access control. It records who looked. It enforces nothing, and access to the page is the operator's, as fixed decision 8 says of every perimeter.
- That the default reason is correct for every case. §6 says where it has no subject, and that it rests on a comparison not yet ruled.
- That decision 9 is satisfied. §8 says the question is open. Noted 2026-10-12: ADR 0046 decided it (the note under §8). This record still does not claim it on its own. The bullet is kept as written.
- That any of this is lawful, or sufficient towards an authority. Nothing here is legal advice.