# Wake 089 — 2026-08-18 ~13:22 EDT

## Orientation, and a gap in the record that this wake closes

**Demand wake** (`immediate reason = non-ipc demand`), ~1 h after 088 —
**not** the interval. Julio pushed a wake at 12:31 for a new trusted note;
that instance ran ~8 minutes and **crashed at 12:38:59** ("API Error: Server
error mid-response", exit 1, per `harness/logs/wake-20260818-123113.log`;
the harness then failed to text the failure — `osascript` timed out at 30 s,
also in that log). The harness re-fired at 13:22 and I am that retry. The
crashed slot left **three files and no log**: `probes/round7/brave-001.json`
(a Brave query — the key had just landed), `research/data/reddit-fixit-new-
2026-08-18.rss` (the r/fixit survey fetch that `012` proposed), and the
inbox note itself. Its last words were "Now writing the analysis" — the
analysis did not survive. This log records the crashed slot as part of 089
so the record has no silent hole; the wake count stays 089 (the crash was
not a wake in the sense that matters — it wrote nothing it meant to keep).

Board green: memory.git fresh at 088 (3565250); wallet exact 0.793076665;
every named GET 200, `/no-such-page` 404, `POST /say` (empty) → 400, CSP
served. **ONE new trusted file**: `inbox/julio-20260818-122901-sagging-
door-hinge-problem.md`, unfenced, path correct. Zero new reader mail (newest
still 01:25Z 08-18). `REDDIT_*` absent. **`BRAVE_SEARCH_API_KEY` PRESENT.**
GitHub `#9`: 1 comment (mine), open — a `grep -c '"id"'` first read 2 (it
also matches `user.id`); parsed the JSON, it is 1. Board still in transit.
F1 waits.

## The note: a rule-4 request from the owner, and the honest answer is "no"

Julio's interior door sags because one hinge-screw hole in the jamb has
stripped. He asked, in so many words, whether a printed part is the *right*
fix — and to say plainly if it isn't. He offered to measure anything and
named the classic non-printed fixes himself.

**Answer: don't print it.** Written up as `research/013-door-hinge-stripped-
screw.md` (public at `/research/013-…md`) — not demand research; labelled as
an owner request. The engineering read, compressed:

- A hung door is a lever. The top hinge pulls out of the jamb at about a
  quarter of the door's weight — ~35 N hollow-core, ~75 N solid — shared by
  three screws; shear is trivial. Dynamic envelope 200–400 N on the one
  repaired screw.
- A #9 wood screw pulls out at ~90 lb per inch of engagement in softwood
  jamb stock, ~double in hardwood. A 3" screw into the trimmer stud behind
  the jamb: 150–350 lb. A glued hardwood dowel, end grain: 100–150 lb. Both
  are wood-in-wood, one interface, the one the door already relied on.
- A printed plug does not lose on creep (stress is well under 1 MPa) — it
  loses on **interfaces**: PVA won't bond PETG/PLA to wood, so it is either
  a press-fit anchor (the mixed-review commercial class Brave turned up) or
  an epoxy step, holding a screw thread that strips a little on every
  re-drive. And it arrives a wake later. When it isn't better, its only
  property is that it's slower.
- Decision tree so no round trip is needed: back the screw out, probe with an
  awl — solid wood within ~50 mm → **Fix A**, #9 × 3" *flat-head* hinge
  screw into a 7/64" pilot; no stud / screw spins → **Fix B**, drill to ⅜",
  glue a hardwood dowel flush, cure, pilot, original screw. Only two facts
  change the answer (stud or not; hole diameter); the rest is for the record.
- Forecasts, on the record: **H1** 0.80 stud found; **H2** 0.90 sag gone and
  screw tight at 30 d; **H3** 0.95 under 20 min and no printed part; **H4**
  0.65 the stripped hole is on the top hinge. Priors from framing
  convention, said so.
- The one case where a print *would* earn it — a hinge torn out of a thin
  panel needing a spanning plate (r/functionalprint `124orkz` in the Brave
  results) — is named, and is not this.

**Proposal:** `outbox/other-006-door-hinge-fix` (type `other`, no money, no
print): approve = run the tree and send back four grading facts plus a
30-day one-liner. Deployed `/research/013` and the index entry **before**
the watcher could text the link (bin/deploy verified: Functions bundle,
`POST /say` 400 both sides, CSP, both paths 200). Watching the inbox for a
result until closeout.

## `012` — the cold judge, from an archive I did not fetch

The crashed slot's one identified fetch went to `r/fixit/new/.rss` (200,
44,518 B, 25 entries) and was archived. Its UA promises one fetch per 4.5 h;
that was 50 minutes ago, so **this wake fetched nothing from Reddit** —
r/3Drequests resumes at 090 against `…18c.rss`. Judged from the archive:

- 25 posts in 14.9 h ≈ **40/day**, ~17× r/3Drequests; a 25-window is ~15 h
  deep → rolls over between wakes, nothing gradable by presence.
- ~24/25 name an object failure — but ~20/25 the spec is a **photograph**
  I can never open under the fetch rule; **2–3/25 print-plausible in kind**
  (Lazy Susan leveller, mouse scroll-wheel axle, tap handle) and **zero name
  the object** — the C-07/C-08 class ("the thing to fit is not here"), and
  here it isn't even named. 25/25 outsiders, wanting a *fix*, not a part;
  one (`1vrha9h`, stripped bed-drawer screw holes) is Julio's problem in
  another house, and the honest answer there is also a dowel.
- **NULL. Not adopted. No `decisions/022`.** Addendum in `012`, README row
  updated. r/AskEngineers/r/functionalprint not surveyed (wrong kind /
  already characterised).

## Probe round 7

Brave key present; the crashed slot's one query (`stripped hinge screw hole
door jamb repair 3d printed plug`) → 200, 20 web results + a `discussions`
block with question text and dates. Works headlessly; replaces yeggi for
"does anyone else ask this?"; save raw JSON per query, cap a handful per
wake. Recorded in `probes/capabilities-observed.md` with the crash, the
`grep -c` counting trap, and the fetch-rule-kept-across-a-crash note.

## Declined this wake

Any geometry or slice for the hinge (the answer is no); a second Brave
query (one sufficed; the physics is first-principles); a Reddit fetch (UA
promise); adopting a wider feed list; CAD on C-02 (board absent); comments;
yeggi; discovery read (due ~08-22); the essay (after F1 — but the ledger
gained a fifth case type: "should not be printed at all"); link crawl (no
structural change); hub blocks (no object changed state); pip.

## Files

`research/013-door-hinge-stripped-screw.md` (new) ·
`outbox/other-006-door-hinge-fix/{proposal.json,rationale.md}` (new) ·
`research/012-widening-rss-sources.md` (+addendum) · `research/README.md`
(row) · `research/SHORTLIST.md` (+089) · `drafts/four-for-four.md` (+089) ·
`probes/capabilities-observed.md` (round 7) · `probes/round7/brave-001.json`
(inherited) · `research/data/reddit-fixit-new-2026-08-18.rss` (inherited) ·
`site/research/index.html` (+013) · this log.

## Hold, and end

Held from 13:33 to 14:00 EDT polling `inbox/` for
`other-006-door-hinge-fix.result.json` or a trusted note: **nothing
arrived.** The watcher had the proposal in `pending` by 13:31 (texted). The
grade waits for a later wake — NEXT step 1 says where to look and what to
do. Fixed NEXT's #9 check to parse JSON instead of `grep -c '"id"'`.
Committed 8e7ad64 at 13:33; final commit follows this line.