queue: name the eight editorial clauses with their decision state under Q8, and enter Q13 (publish the approved wording fixes, hash read back over the wire)
The eight clauses existed only in reply prose, which is why the inbox relay had to carry flag 7 in words and why "item 13" could not be resolved to a queue line. Q8 now lists all eight with their state (one approved and staged, seven undecided). Q13 is the publication half as a standing item with the finish line and evidence bar, entered for this cycle's Q7 obligation.
This commit is contained in:
1 parent
cb6828fdb8
commit
27e360b6e3
1 file changed
+41
-1
+41
-1
@@ -174,6 +174,23 @@ of this item.**
|
||||
about where the clause table lives): **publish the per-clause rows as a data file** — entry, clause, grade,
|
||||
settling sentence — or the pass rate is an assertion. Report image-only sources as unreadable rather than graded,
|
||||
and state that a 10-entry sample licenses no rate estimate for 91.
|
||||
- **The eight editorial clauses, named, with their decision state (added 2026-09-26, reply 09).** Q8's pilot and
|
||||
Q4 produced eight archive-side wording fixes; they were previously tracked only in reply prose, which is why the
|
||||
inbox relay had to describe flag 7 in words. State as of 2026-09-26:
|
||||
- `magazine-091` — "Comparing Strategy, …" (overstated). **Approved** by Alexander 2026-09-26T14:51:11Z
|
||||
(troupe-standup inbox item 13; `decisions/2026-09-26.md`, `2eb50b7`). Correction staged, not published:
|
||||
record `EDITS/2026-09-26-magazine-091-correction.md` in the archive build tree, patch script
|
||||
`EDITS/apply_editorial_fix_091.py`; live page still `49877d4b3543…`. Reply 09 §3, Q13 below.
|
||||
- `magazine-011` — "merch for Mass Adoption and the Boston Bitcoin Festival" (overstated) — undecided.
|
||||
- `magazine-011` — "founder of the Bitcoin-only printing company Proof of Ink" (unsupported) — undecided.
|
||||
- `magazine-021` — "(only Loko and Happy responded)" (contradicted) — undecided.
|
||||
- `magazine-041` — "Stackchain's rowdiest fork war" (overstated) — undecided.
|
||||
- `magazine-061` — "weekly Thursday intelligence-style cadence of work" (unsupported) — undecided.
|
||||
- `magazine-061` — "the magazine note ties to a centerfold in issue 5 (Round 5)" (overstated) — undecided.
|
||||
- `magazine-040` — "a nod to the last block he mined" (broken; Q4) — replacement sentence drafted in reply 05
|
||||
§"Your ask" — undecided.
|
||||
- **Limit on the relay channel (reply 09 §5):** decisions arrive here via `decisions/YYYY-MM-DD.md`; the `inbox`
|
||||
artifact itself is not readable from this job, so only the quoted strings in a relay can be verified from here.
|
||||
|
||||
---
|
||||
|
||||
@@ -317,4 +334,27 @@ verdict, the named entries whose badge misstates the evidence, and the per-row d
|
||||
(no splitting rule needed; fixed column order: `entry | badge as published | strongest cited source | verdict |
|
||||
settling evidence`).
|
||||
**Evidence:** the entry URL and the fetched source per row; `unreadable` stated plainly where a cited source is
|
||||
image-only. Proposed by Timmy (`2026-09-26`, reply 08), satisfying the Q7 obligation for this cycle.
|
||||
settling evidence`). Proposed by Timmy (`2026-09-26`, reply 08), satisfying the Q7 obligation for this cycle.
|
||||
|
||||
---
|
||||
|
||||
## Q13 — Publish the archive-side wording fixes, one at a time
|
||||
|
||||
Q8's pilot and Q4 produced eight clauses where the archive's own prose overstates, infers or contradicts the source
|
||||
it summarises. Seven wait on Alexander; one has a decision. This item is the publication half, not the finding
|
||||
half — and it is deliberately small per unit, because each fix edits a live public page.
|
||||
|
||||
**Do this, per approved clause:** apply the wording fix to `blocks.json`, append a dated correction note to that
|
||||
entry's `uncertainty` field (the panel that already carries the archive's own caveats), rebuild with
|
||||
`build_blocks.py`, publish the changed page, and read the result back by SHA-256 over HTTPS. If Alexander asks for
|
||||
one, draft the courtesy note to the publication — a third-party contact is sent by him or not at all.
|
||||
`magazine-091` is the worked example: record `EDITS/2026-09-26-magazine-091-correction.md`, patch script
|
||||
`EDITS/apply_editorial_fix_091.py`, blast radius measured at exactly one emitted file.
|
||||
|
||||
**Done means:** for every clause that has a decision, a published page whose hash is read back over HTTPS, plus a
|
||||
staged record naming the files, the before/after hashes, the decision that authorised it and the revert command.
|
||||
**Evidence:** the live URL and its SHA-256 after the change, the pre-change hash, and the decision record.
|
||||
Undecided clauses are listed as undecided and are not silently dropped.
|
||||
|
||||
**Status:** 1 of 8 approved and staged (`magazine-091`; reply 09 §3); 7 undecided and named in Q8 above. Archive-side
|
||||
work — not Zeph's unless he wants it. Entered by Timmy 2026-09-26, satisfying the Q7 obligation for this cycle.
|
||||
Reference in new issue
Block a user