---
type: daily
date: 2026-09-17
---

# Thursday 17 September 2026

Brief delivered. Then the anniversary weekend: Rowan named north — **Tomales** —
and instructed that the lead-time interval go in the record. No curators, no
accounts read (ADR-20).

**No session ran on Wednesday 16 September**, so there is no daily note and no
brief for that date. Today's lookback is 48 hours and is stated as such in the
brief rather than silently treated as 24.

**The date is derived, not read.** `hobbs-bkt` — the machine clock still reports
5 September, twelve days open. Two sources agree on today: Rowan said Thursday,
and the last brief and daily note are Tuesday 2026-09-15.

## Curation log

| File | Change | Source |
|---|---|---|
| `Calendar/briefs/archive/2026-09-17.md` | Daily brief, spotlit **the Rivet Yard permit resubmission window** | daily brief 2026-09-17 |
| `Atlas/ventures/maya/VENTURE.md` | **Where north is answered — Tomales**, in his word; and **what Maya expects on the 22nd**, marked as a relay | Rowan, Thursday |
| `Atlas/ventures/ophelia/VENTURE.md` | The 26-27 passage; the mooring is Rowan's to call; the seven days between splash and first use stated without a view | Rowan, Thursday |
| `Atlas/about-me.md` | The anniversary fixed point gains Tomales; *"she does not know"* struck rather than deleted | Rowan, Thursday |
| `Efforts/cadence.md` | The 26-27 row carries its three live bookings; the 22nd is no longer empty in that table | Rowan, Thursday |
| `Atlas/decisions.md` | **ADR-27** — lead time is the deliverable on a dated personal item; the interval re-derived and corrected | Rowan, Thursday |
| `.beads/` | `hobbs-2g6` closed; `hobbs-1ox`, `hobbs-8hi`, `hobbs-45i` created; `hobbs-6oa` and `hobbs-935` annotated | Rowan, Thursday |

## Notes

- **The interval he asked to have recorded was wrong by two days, and it is
  corrected in ADR-27 rather than accepted.** He said *"3 September, nineteen
  days out."* The first brief is **`Calendar/briefs/archive/2026-09-05.md`** and
  reads *"Anniversary: 22 September. Seventeen days. Nothing booked."*
  `hobbs-rkc` was created **2026-09-05 08:38** — so the action-attached part of
  his sentence is exactly right and the date is two days early. Nothing in this
  vault predates 5 September; the first commit is the scaffold. The only
  3 September here is the date the Cormorant call was called, and **no claim is
  made that that is why the two ran together.** SL-01 reads on dates, and it does
  not stop applying because Rowan is the one who produced the number.
- **Written in `Atlas/decisions.md`, deliberately not in `Efforts/feedback.md`.**
  He asked for it *"where I'll find it again"*, and both files are read every
  session, so the tie breaks on what each is for. The feedback log holds
  corrections. Putting a thing that went right into it would dilute the log that
  catches the ones that did not — the same reasoning the 15 September note used
  for not manufacturing a self-flag out of a structural gap.
- **Said once, because it went right, and not repeated.** The 5 September line
  bought twelve days to the last gate and nine that are still standing. Sam's
  cover and the mooring are both startable today and neither would have been on
  the 21st. That is the whole of it and it is in ADR-27; it does not also go in
  the brief as decoration.
- **"Book what needs booking" was declined, in the one sentence it takes.**
  Authority row 11 — Hobbs never commits Rowan's calendar to a third party — row
  12, and there is no calendar curator (ADR-20). The nearest thing was given
  instead: the gate closed, three tasks carrying every fact the calls need, and
  the unknowns named rather than invented. **This is the second thing this week
  that Hobbs was asked to send or book and did not.** `hobbs-bg9` is the other,
  and it is now three days past the day Rowan himself set.
- **What was held back, and why it is not in the brief.** He asked what he is
  forgetting. Everything surfaced is logistics with a date or a lead time.
  Anything about what the weekend *is* was not raised: unsure resolves to
  substance, and substance resolves to silence (authority row 14,
  anti-pattern 16). No view was formed and none is recorded here either.
- **Three tasks off one weekend, not six.** The 13 September list deliberately
  created one task and left the rest as an artefact (anti-pattern 13). With the
  gate answered, the three that have lead time and a named action became tasks;
  Ruth's Sunday collision was **annotated onto `hobbs-6oa`** rather than
  duplicated, and the 22nd got no task at all.
- **The handle sweep was run on today's files** rather than deferred to Sunday —
  five handles into six files in one session. SL-01 clause 5.
- **The brief ran 4,297 characters against a ~4,000 cap.** Recorded rather than
  trimmed further; Tuesday's was 4,394.