No ADRs match your search.
ADR-001The Dossier of Governed Work: SpecDossier Bounds, Agrees by Digest and Follows the Work a Project Governs, Exposes Without Judging Its Content, Reads the Formats Others Own, and Writes into a Project Only by the Channel the Project GrantsADR-002A Project Declares Where Its Dossiers Live: SpecDossier Finds Them by That Declaration, in the Project's Own Governance, and Nowhere ElseADR-003A 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 DispositionedADR-004A Dossier Answers to the Authority Its Project Declares: SpecDossier Learns It From the Round, Is That Authority's Client Only Where the Project Granted It, and Asks It to Verify and Attest a Signature, Never Holding a KeyADR-005What Was Agreed Lands Through the Channel the Project Grants: the Service Carries the Agreed Bytes and Their Attestation to a Branch the Project Grants, Never Its Main One, and Logs Each Landing Signed With Its Own KeyADR-006The Owner Acts From the Shared Face Through a Governed Bridge: the Web Prepares an Act as an Intent, openbyname Carries the Person's Consent as a Ticket the Service Issues and Redeems, and the CLI Applies It in the Person's CopyADR-007The Pre-flight Is Shown as Its Producer Produced It: a Command the Project Declares Runs in the Person's Copy at Each Round, Its Report Is Bound to the Revision's Digest, Shown at the Decision Point Without Refusing It, Recorded by Digest in the Agreement and Carried at LandingADR-008A Dossier Governs One Document or Several: Each Has Its Own Round and Agreement, the Set Is Agreed by the Digest of Its Manifest, `part_of` and `after` Relate Only Its Own Documents and Nothing Models Priority; a SOW's Stage, Validity and Relations Are Read From ontoref's RegistryADR-009A Dossier Watches Its Criteria as Named Reports: a Project Declares, per Kind, One or More Commands Whose Reports the Round Shows as Produced, Unknown Included, and the Agreement Records Each by DigestADR-010What Must Keep Holding Is a Standing SOW Paid at Every Commit: the Commit Gate Asks ontoref What Live SOWs Owe at 'Commit and Runs It; the Spine's Hard Constraints and the Copies of ontoref's Formats Are Its First Two CasesADR-011The Trail of a Dossier Is ontoref's Reading, Shown Beside Its Stage: For Each Governed SOW, Where the Registry Places It, Which Dossier ontoref Says Agreed It, Its Signatures and Its Receipt as ontoref Verifies Them; Nothing Derives a Landed Stage and Nothing Agreed Elsewhere Is ClaimedADR-012The Owner Puts a Round and Lands From the Shared Face: the Page Asks the Person's Authority for Their Authorize Decision by Passkey, the Intent Carries It Unspent, and `specdossier apply` Sends It With the Act; Attest and Open Stay the CLI'sADR-013What Each Person Owes Across Dossiers Is Derived From the Rounds the Service Holds, on Each Request, for the Person the Authority Identified: Shown on the Service's Home Page and in Its JSON, Linking Each Debt to Its Round; Nothing Owed Is Stored and No Agreement Is ClaimedADR-014A Service Declared readonly Is a Reader: It Serves the Levels' SOWs and Their Views Beyond the Loopback Without an Authority, Mounts No Act and Knows No One; It May Hold ontoref's Registry Reading for a Declared Time, Always Saying How Old It IsADR-015The Faces Are Rendered From minijinja Templates Styled by UnoCSS With daisyUI and Driven by htmx, All Carried in the Repository and Embedded in the Binary; One Set of Templates Serves Every Face — Service, Reader and Static Export — for an Anonymous Reader or a Person the Authority IdentifiedADR-016The Faces Speak the Reader's Language Through Fluent Catalogs While the Work Stays in Its Own; Help Is the Governed Surface Shown in Place, and What to Do Next Is ontoref's Reading of Each SOW, Never SpecDossier's JudgmentADR-017From the Face a Person Prepares Acts on a Level's SOWs — Opening a Dossier by a Declared Preset or by Its Terms, and ontoref's Verbs on a SOW, One or Several — as Intents Naming SOWs by Id, Applied in Their Copy Through openbynameADR-018A Reader May Declare an Authority to Know Who Reads: Its Faces Show the Person and Their Hats, and Keep Their Marks on SOWs, While It Still Mounts No ActADR-019A Governed Item Is Reviewed on the Face by Its Parts: Each Participant's Remarks Are Bound to a Part and to the Bytes Read, Visible to Every Participant, Revised or Withdrawn Without Being Rewritten, and Handed Whole to Whoever AnswersADR-020A Project's Governed Items Are Shown and Referenced on the Face: Its SOWs, ADRs, Biops and Dossiers Each Have Their Place and Address, ADRs and Biops as ontoref Publishes Them, Dossiers Where the Level Declares Them, and Its History as the Level's Files Hold ItADR-021Each Project Declares Its Governance Levels, a Script Collects Them Into the File a Service Reads, Each Project Is Shown With Its Logo and Levels, and ontoref's Panel and SpecDossier Link to Each Other