Accepted adr-003 · 2026-09-29

A Dossier's Rounds Are Transient in the Service, Which Never Reads the Project; the Agreement Is the Person's Act, Written in Their Copy with Every Point Dispositioned

Context

adr-002 left open how a deployed service learns which projects to read, whether it keeps their addresses, and how a guest with no access to the project reaches the part put to them. The principal's interview of 2026-09-28 holds that only the agreement must persist and the rounds may not (P5), that a guest sees only their part (P8), and that no agent answers for an agreement (P3); core.ncl recorded that specdossierd's redb kept a SOW's remarks as if they were the record, with no disposition, gathered by nothing.

On 2026-09-29 the walk of dossier-walk opened → agreed put it before a real case. The principal chose, among the characterized options, a round put by the person from their copy, a guest's identity from the authority, one core action per act reached by every face, a point anchored to a part of the document with the digest read, and an agreement written by the person in their copy (code/.governance/sow-agree-a-dossier.ncl, receipt signed with the level's key). signatio 1919c0c, which seals the resource an Authorize decision is about, made a guest's point allowed for a document and its bytes possible.

Decision

A DOSSIER'S ROUND IS TRANSIENT, AND IT IS THE SERVICE'S. The person who opened the dossier puts the governed document, as it is in their copy, before a round of the service: the dossier, the document's bytes and their digest. The service holds the round while it lasts — the document as put, its revisions, the points raised on it — and nothing it holds is the record: a round is not mirrored, and losing it loses no agreement.

THE SERVICE NEVER READS THE PROJECT FOR A ROUND. A guest reads exactly what was put before them; the service keeps no address of the project and reaches nothing else of it. (AMENDED 2026-10-08 BY adr-020: outside a round, a service may read — never write — the dossiers its level's declaration names, to show them; a round still reads nothing of the project.) A round is readable, and a point may be raised on it, only by someone the dossier invites or the person who opened it, as the authority knows them; it is put only by the person who opened it, and never over a round someone else opened under the same id.

A POINT ANSWERS A PART OF THE BYTES IT READ, AND STAYS OWED UNTIL THE AGREEMENT DISPOSES OF IT. A new revision expires the reading, never the debt.

THE AGREEMENT IS THE PERSON'S ACT, IN THEIR COPY. The person who opened the dossier declares agreed the version the round shows, which must be the one in their copy, closing every point incorporated, declined with its reason, or routed; anything owed refuses it. The digest agreed and every point with its disposition are written into the dossier in the project, by that person. No source of the service writes a dossier.

WHAT FOLLOWS THE AGREEMENT IS NOT SPECDOSSIER'S. When the dossier's closing asks for a signature, whether and by whom the agreed version is signed is decided by the project — with ontoref, by its ratification policy — and the signature is made on the signer's machine and attested by the authority (signatio); SpecDossier only verifies it and shows it (adr-001). Landing the agreed file through a channel the project grants, and the service's signed log, stay dossier-walk agreed → landed.

Constraints

Alternatives considered