hyperpolymath · Oct 20, 2026 · Oct 20, 2026
@@ -2,12 +2,12 @@
 // SPDX-FileCopyrightText: 2026 Jonathan D.A. Jewell (hyperpolymath) <j.d.a.jewell@open.ac.uk>
 = Ultraplan: getting the deed, K9 and contractile system right, estate-wide
 Jonathan D.A. Jewell (hyperpolymath)
-v0.3.0, 2026-10-20
+v0.3.1, 2026-10-20
 :toc: left
 :toclevels: 3
 :sectnums:
 :icons: font
-:status: DRAFT — for owner review. v0.3.0 records fifteen owner rulings of 2026-10-20, with Q16 open (<<owner-model>>, <<decisions>>). Measured sections are facts with commands. Sections marked PROPOSED are design, not rulings, and are written to be reviewed by a second, unanchored reader.
+:status: DRAFT — for owner review. v0.3.1 records all sixteen owner rulings of 2026-10-20 (<<owner-model>>, <<decisions>>). Measured sections are facts with commands. Sections marked PROPOSED are design, not rulings, and are written to be reviewed by a second, unanchored reader.
 
 [.lead]
 The owner found the template with what looked like only an Adjustfile in its
@@ -323,9 +323,9 @@ self-diagnosing, self-healing repair script that user-facing applications must
 ship (`docs/UX-standards/DUSTFILE-SPECIFICATION.adoc`, advertised by the UX
 standards README, with `dustfile-template.sh` and three other UX documents).
 |three repos, four meanings. *Ruled 2026-10-20:* the Dustfile is exnovation:
-stripping down, uninstalling, retiring. Reading (d) is normative and
-contradicts the ruling; it is closer to the Bustfile's "how to fix things
-when they break". Where it goes is Q16.
+stripping down, uninstalling, retiring, reverse-engineering guidance and the
+deliberate disabling of features ("from dust to dust"). Reading (d) is the
+Bustfile's specification, not the Dustfile's (Q16, ruled 2026-10-20).
 
 |`bust`
 |(a) hard stop, expiry, must-not-run (template README); (b) rollback
@@ -701,8 +701,8 @@ from the template and coaptation, and are proposals where marked.
 |`must` |Mustfile |Invariants. On a violation everything stops until the contract is settled. |blocking |boolean
 |`trust` |Trustfile |Security, privacy and safety. |blocking |boolean + provenance
 |`adjust` |Adjustfile |Accessibility. Its descriptile counterpart is ADJUST, the repo's actual state. |advisory (floor may graduate to `must`; PROPOSED) |graded [0,1]
-|`dust` |Dustfile |Exnovation: stripping down, uninstalling, retiring. |advisory |reported, never alarms
-|`bust` |Bustfile |Likely failure pathways and weaknesses, and how to fix things when they break. |alarm when a declared failure pathway is active (PROPOSED) |alarm
+|`dust` |Dustfile |Exnovation: stripping down, uninstalling, retiring, reverse-engineering guidance, deliberately disabling features. |advisory |reported, never alarms
+|`bust` |Bustfile |Likely failure pathways and weaknesses, and how to fix things when they break: self-healing, self-diagnosing, domain-specific fix scripts, including partial fixes that acknowledge a failure (Q16). |alarm when a declared failure pathway is active (PROPOSED) |alarm
 |===
 
 Drift tolerance, the other reading of `adjust`, becomes a tolerance band on any
@@ -804,8 +804,7 @@ One rule for all three formats, generalised from the K9 contract:
 == The plan
 
 Each step names its home and its acceptance check. A `(Qn)` tag names the owner
-ruling in <<decisions>> that the step implements; all are ruled except Q16,
-which only the UX-standards half of P1.2 waits on.
+ruling in <<decisions>> that the step implements; every one is ruled.
 
 === P0 — stop the bleeding (days)
 
@@ -924,7 +923,9 @@ which only the UX-standards half of P1.2 waits on.
   a verb, citing the ruling: the template contractiles README, the contractiles
   repository's canonical-directory README, `CONTRACTILE-SPEC.adoc`,
   `ADJUST.contractile`, the template `CLAUDE.md`, coaptation, and the UX
-  standards' Dustfile documents as Q16 rules. The live records that feed the
+  standards' Dustfile documents, which Q16 ruled are the Bustfile's
+  specification: `DUSTFILE-SPECIFICATION.adoc` and `dustfile-template.sh` are
+  renamed to the Bustfile, and their four companion documents re-pointed. The live records that feed the
   runner are edited in the same step, or P2.2 would carry the old meanings into
   it. In standards, `adjust.k9.ncl` declares
   `drift-tolerance-and-corrective-action`, `dust.k9.ncl` describes rollback and
@@ -1142,7 +1143,7 @@ All fifteen answered on 2026-10-20 through the selector: Q1 to Q4 (<<owner-model
 then Q9 to Q15, then Q5 to Q8, each on the recommended arm. Q9 was ruled after the
 plus-minus-interesting comparison the owner asked for (<<q9-pmi>>). Q5 was
 confirmed as one rule shared by all three formats. Q16 was found in review after
-those rulings and is open.
+those rulings and was ruled the same day. No owner question is open.
 
 [cols="1,3,3",options="header"]
 |===
@@ -1193,7 +1194,7 @@ its runner, with `:contractiles_required` derived from it.
 |Q15 |What is `0-AI-MANIFEST.deed` for, beside the chora deed? |*Ruled 2026-10-20:*
 a pointer-only front door: where to read first, and the startup checklist. Every
 fact lives in the chora deed.
-|Q16 |What happens to the UX standards' repair-script "Dustfile" (`<app>-dustfile.sh`)? |*Open* (found in review, 2026-10-20). (E) it becomes the Bustfile's executable half, renamed, since repair is "how to fix things when they break"; or it keeps its job under a new name outside the six verbs; or it stays and is registered as a homonym.
+|Q16 |What happens to the UX standards' repair-script "Dustfile" (`<app>-dustfile.sh`)? |*Ruled 2026-10-20:* it is the specification of the Bustfile: self-healing, fault-tolerant, self-diagnosing and observability-oriented fix scripts for recognised weaknesses, domain-specific, including partial solutions that acknowledge a failure. "If something is broken, i.e. bust, that is where it comes in." The UX documents are renamed to the Bustfile (P1.2). The Dustfile keeps exnovation: reverse-engineering guidance, removal of everything, and the deliberate disabling of features.
 |===
 
 [[q9-pmi]]