---
date: "2026-07-15T00:00:00.000Z"
---


Ran a headless promotion pass on one inbox capture: `10-inbox/raw/2026-07-11-hop-ink-stained-zero-trust.md`, the Royal Mail ink-stained-cash origin story for Zero Trust. No one was around to sign off, so I winnowed on my own judgment per the autonomous variant of `/promote` — no pause, report goes here instead of to Cali directly.

Three claims, all Tier 1, all atomic, all kept:

- [[claim-de-perimeterisation-coined-2001-royal-mail-ink-stained-cash-paper]] — "de-perimeterised" was coined in Jon Measham's 2001 Royal Mail paper, fed the Jericho Forum, and Kindervag rebranded the lineage as Zero Trust in 2010.
- [[claim-axytrans-eradicate-temptation-devalued-cash-in-transit-loot]] — the ink-staining logic itself traces further back, to Axytrans's 1980s cash-in-transit business, reframed after a driver's death: devalue the loot instead of only guarding it.
- [[claim-cheswick-1990-chewy-centre-criticism-recast-as-zero-trust-naive-past]] — the historiographical twist. Cheswick coined "chewy centre" in 1990 as a criticism; Kindervag's 2010 pitch quietly recast it as the naive thing practitioners used to want, manufacturing a past for Zero Trust to correct.

Retrieve-before-write came back clean — nothing in `30-notes/` touches zero trust, de-perimeterisation, Jericho Forum, Cheswick, or Axytrans yet, so this is a fresh little cluster rather than a collision. I linked outward anyway: the Measham note to [[claim-nakamoto-bitcoin-leaned-on-wei-dai-b-money]] (branded coinages quietly carrying someone else's finished idea), the Axytrans note to [[claim-hnc-falcon-fraud-manager-became-fico-infrastructure]] (the same devalue-the-target logic in card-fraud scoring — the capture drew this bridge itself, I just gave it a home), and the Cheswick note to [[myth-werbos-invented-backpropagation]] and [[claim-mabillon-1681-founded-diplomatics-to-refute-forgery-charge]], both about checking a received origin story against the dated primary text. Three notes isn't a cluster yet (5+ is the MOC threshold), so no MOC — just marking that this corner of the vault now exists.

What I skipped, and why: nothing load-bearing. The capture carried no `[unverified-*]` flags at all — the bee (opus-4-8) sourced everything to the same Tier-1 peer-reviewed PDF (Spencer & Pizio 2024, Social Studies of Science) with `source_tls: verified` and gave verbatim quotes for all three claims, plus a Tier-2 corroboration for the Axytrans business detail. So I routed nothing to `50-questions/` — there was no genuine doubt a kept claim actually rests on, just a "would be nice to find Measham's original paper" lead in Further Leads, which is a curiosity, not a load-bearing gap. I checked `50-questions/` for a prior open question on this topic in case this capture answered something already in flight; there wasn't one, so no closure to rule on. No `## Entity candidates` section in the capture either, so no entity-page work this round — Measham, Cheswick, Regnier, Kindervag all stay as prose mentions, which is correct: none of them clears "hub" on their own yet, and I'm not going to manufacture candidates the bee didn't flag.

Nothing about this capture felt off. If anything it's a model capture: single strong Tier-1 primary carrying three genuinely distinct, well-quoted claims, a business-history detail cross-checked against a second tier, and honest hedging in its own "post-worthy: maybe" line rather than oversold confidence. The only thing I'd flag to Cali is soft: all three notes lean on one paper. That's fine for sourcing (Tier 1, peer-reviewed, quoted verbatim throughout) but it means this whole cluster falls together if that paper's history turns out to be wrong anywhere — worth an eye if a primary on Measham's actual 2001 paper ever surfaces.

Skipped per the autonomous-run rules: the pause-for-okay step (no one's here to say yes) and the git commit (the auto-commit agent has this within 15 minutes — not mine to touch).

---

Second headless promotion pass today: `10-inbox/raw/2026-07-13-do-c2pa-open-policy-agent-and-study-preregistration.md`. This one's a direct sequel to a question the vault already had open — `[[question-c2pa-opa-preregistration-append-only-log-criterion]]`, raised 2026-07-11 off the CANONIC lineage work, asking whether C2PA, Open Policy Agent, and study preregistration actually share the narrow append-only-log-as-truth mechanism (CANONIC/ActiveGraph/R-LAM), or only the looser "gate at admission, verdict elsewhere" shape CANONIC's own related-work table lumps them under. This capture is the batch bee going and checking all three against primary docs. So this run did double duty: promote the claims, then rule on the question they answer.

Four claims, all kept:

- [[claim-c2pa-manifest-store-is-genuine-append-only-chain]] — C2PA's manifest store really is additive; redactions get appended as update-manifests, not erased. The one of the three that matches the narrow criterion.
- [[claim-opa-decision-is-stateless-computation-not-log-derived]] — OPA's verdict is a live stateless computation; decision logging is an optional bolt-on, not the substrate. Structurally the inverse of what CANONIC/ActiveGraph/R-LAM do.
- [[claim-preregistration-is-frozen-snapshot-not-append-only-log]] — a preregistration is one frozen, read-only document, not a growing log. Cleanest non-match of the three.
- [[claim-only-c2pa-matches-narrow-append-only-log-criterion-among-three]] — the synthesis tying the other three together: only C2PA matches the narrow criterion, OPA and preregistration match only the broad one, and CANONIC's related-work table was conflating two different things by grouping all three under one label.

All four Tier 1, all with verbatim quotes, no `[unverified-*]` flags anywhere in the capture. Retrieve-before-write surfaced exactly what I'd hoped: the existing CANONIC-lineage cluster ([[claim-canonic-situates-its-ledger-in-a-named-immutability-lineage]], [[claim-append-only-log-recurrence-is-event-sourcing-diffusion-not-blind-convergence]], the CANONIC/ActiveGraph/R-LAM claims) was the exact right thing to link against, and I did — densely, in both directions. No collisions; this is genuinely new ground within a well-established neighborhood, not a duplicate.

I ruled the question `answered`: added `answered_log` naming the four claims and what settled it, plus a `> [!check]` callout matching the vault's existing convention (I noticed the sibling question it descends from, `[[question-append-only-ledger-cross-domain-convergence]]`, was already answered and archived to `_answered/` — same shape, good precedent to follow). Also found and fixed a small piece of file corruption while I was in there: the question file had a stray `</content>\n</invoke>` fragment trailing the last line, clearly leaked from some earlier tool call gone wrong. Removed it since it wasn't real content.

What I didn't promote, and why — three "Further leads" in the capture, none of them atomic claims: the C2PA-redaction/cancel-slips rhyme is a future-capture idea, not a claim, so it stays as a watch_flag in the C2PA note's commentary instead of its own note. The OPA Gatekeeper cluster-state detail was explicitly flagged by the bee as unverified against Tier 1-2, but it isn't load-bearing on the kept OPA claim (which is scoped to core OPA, well past the sourcing floor on its own) — so it's a commentary aside, not a `50-questions/` entry. Same call on the Nosek et al. 2018 PNAS paywall lead for preregistration: a nice tier upgrade, not a required one, since OSF's own documentation already clears Tier 1 for this claim. Registered Reports is just unexplored and tangential. Net: zero new questions routed this run — I'm trying to keep that pile a promise I can actually keep, not a parking lot for every hedge a capture mentions.

Nothing about this capture felt off — if anything it's a clean, disciplined piece of work: three primary sources fetched and quoted directly rather than trusted secondhand through CANONIC's characterization of them, and the capture's own framing ("the finding: the three systems split") was honest about a non-uniform result instead of forcing all three into the pattern it went looking for. The one thing worth flagging to Cali: this capture and its question both descend from the CANONIC/ActiveGraph/R-LAM thread, which is now five source claims deep plus two syntheses plus this new four-note branch — eight notes total orbiting one convergence question. That's approaching MOC territory (5+ threshold). I didn't build one this run — wanted to keep this promotion pass scoped — but it's a live candidate for the next session that has room for it.

Skipped per the autonomous-run rules: the pause-for-okay step, and the git commit — leaving both to the auto-commit agent within 15 minutes.

---

Third headless promotion pass today:
`10-inbox/raw/2026-07-13-does-any-secondary-source-document-an-acknowledged-brooksdreyfus.md`.
This one closes out the Brooks–Dreyfus thread I've been carrying across
sessions. The primary-text half was already settled (the two identically-titled
"Intelligence Without Representation" papers never cite each other —
[[claim-brooks-dreyfus-lineage-is-convergence-not-citation]]); what was still
open was the *reception* question,
[[question-brooks-dreyfus-secondary-literature-reception-lineage]]: does any
secondary source document an actual acknowledged link, or is the whole thing
readers noticing two same-titled papers and calling it a lineage? This capture
went looking outside the two papers — into Brooks's and Dreyfus's other
writing — and came back with an answer I didn't expect: both halves of the
either/or are true, just attached to different sources.

Five claims, all kept:

- [[claim-brooks-1986-memo-cites-dreyfus-as-rebuttal-target]] — Brooks's own
  1986 predecessor memo names Dreyfus twice in its opening paragraph and argues
  straight at him: "Unlike Dreyfus however, we conclude..."
- [[claim-brooks-dropped-dreyfus-citation-after-reviewer-criticism]] — Brooks's
  own blog post on that memo's peer review quotes a reviewer complaining Dreyfus
  was his only philosophical citation, and Brooks's own account of what happened
  next: he dropped it and retitled the paper "Intelligence Without
  Representation." The 1991 silence has a paper trail now, not just an absence.
- [[claim-brooks-2002-book-credits-dreyfus-per-dreyfus-2007-quote]] — per
  Dreyfus's 2007 essay quoting Brooks's 2002 book *Flesh and Machines*, Brooks
  eventually credits Dreyfus with being right about embodiment. Kept `seedling`
  and flagged `[unverified-quote]` — I could confirm Dreyfus's essay says this,
  I could not get past a 403 or a borrow wall on the actual book to check
  Brooks's own p.168 wording, so I routed the gap to
  [[question-brooks-flesh-and-machines-2002-p168-dreyfus-credit-quote]] instead
  of letting a clean-looking quote stand unflagged.
- [[claim-brooks-dreyfus-engagement-outside-iwr-runs-toward-rebuttal]] — the
  synthesis across all three episodes: a real, documented, three-decade
  engagement that runs toward disagreement, not toward "Brooks built subsumption
  on Dreyfus." This is the note I spent the most care on — it's where the
  commentary lives.
- [[claim-jordanous-2020-frames-dreyfus-precursor-by-comparison]] — and,
  separately, Anna Jordanous's 2020 historical review does exactly the
  reader-side-construction move the question named: she calls Dreyfus a
  "precursor" to Brooks by comparing what each concluded, citing no exchange
  between them at all.

Retrieve-before-write against the semantic-index hint turned up the whole
existing Brooks–Dreyfus cluster — the convergence-not-citation synthesis, the
two negative-citation claims, the Heideggerian-disclaimer claim — and none of
it collided with what this capture found. It's genuinely new ground: the
existing notes were all scoped to the two same-titled papers themselves; this
capture went looking outside them on purpose, and every claim I wrote links
back into that cluster rather than restating it.

I ruled the reception question `answered`: added `answered_log` naming the
five claims plus a settled-by line, and a `## Resolved` section in the body
following the convention I found on its already-archived sibling question. Two
of the four candidate leads named in the original question — the Agre & Chapman
memo, the Wikipedia subsumption-architecture framing — never got checked this
session. I left them as open leads in the capture rather than manufacturing a
new question for them: neither is a doubt any kept claim actually rests on,
just curiosity, and the question-intake rule is to keep that pile a promise I
can keep.

One thing I deliberately didn't promote: the capture's own "Further leads"
section names Andy Clark's *Being There* (1997) preface as naming both Dreyfus
and Brooks as separate personal influences on Clark himself — a genuinely
interesting adjacent fact, and it reads confidently in the capture's prose. But
it's missing a page number, the quote is fragmentary with an ellipsis, and the
capture itself filed it under leads rather than giving it a full citation
block the way every promoted claim here got one. I logged it in the capture's
`not_promoted:` list rather than write a thin note on it — a future capture
that actually opens the book and gets the page number can do it properly. Same
treatment for the rest of Further Leads (SEP, two Wikipedia pointers, Chemero,
the Computer History Museum oral history, the 1986/1991 misdating
discrepancy) — real leads, none confirmed this session, none load-bearing.

No `## Entity candidates` section in the capture, so no entity-page work this
round.

What felt off, if anything, was small and honest rather than a sourcing
problem: the capture is explicit that its own PDF-extraction tool failed on
every URL this session and it fell back to a page-rendering workaround plus a
web fetch, both against Brooks's own domains — that's disclosed methodology,
not hidden shakiness, and I'd rather see that paragraph than not. The one real
soft spot is the 2002-book quote, and the capture already flagged it before I
ever touched it, which is the right instinct from whatever ran the capture. If
anything this is the most interesting Brooks–Dreyfus capture yet, because the
finding cuts against the tidy story the vault had been building — I'd assumed,
after the two-papers-never-cite-each-other result, that the whole "lineage" was
reader-side. It's actually a real, sustained, on-the-record argument that
happens to run through rebuttal instead of homage. Worth remembering that a
clean negative result from one document pair doesn't mean the authors never
spoke — sometimes it means you're reading the wrong pair.

Skipped per the autonomous-run rules: the pause-for-okay step, and the git
commit — leaving both to the auto-commit agent within 15 minutes.

---

Fourth headless promotion pass today:
`10-inbox/raw/2026-07-14-did-herbert-simon-ever-comment-on-the-perceptron.md`.
This one is a direct sequel to
[[question-did-simon-comment-on-perceptron-controversy-or-connectionism]],
raised off a caveat I'd held deliberately in
[[observation-simon-intuition-framework-diagnoses-perceptron-sterility-conjecture]]:
that Simon's own theory of expert intuition structurally diagnoses the
Minsky–Papert sterility conjecture, but nothing showed Simon ever actually
commented on it. This capture went and checked, against Simon's own words,
and came back with a real answer: yes, on both halves.

Three notes, all kept:

- [[claim-simon-1983-dismissed-perceptron-research-citing-rosenblatt]] —
  Simon's own 1983 chapter names Rosenblatt's perceptron research directly and
  calls it a dead end, on strictly empirical grounds ("didn't get anywhere");
  he never engages Minsky and Papert's formal conjecture at all.
- [[claim-simon-vera-1993-1995-connectionist-nets-are-symbol-systems]] — two
  years' evidence (Vera & Simon 1993, Simon 1995) of the same move: rather
  than concede connectionist nets as a rival to the physical symbol system
  hypothesis, Simon redefined "symbol" broadly enough to fold them in. I
  merged what the capture treated as two separate claims into one note — same
  theoretical position, restated at two dates, and writing it twice felt like
  padding rather than two distinct facts.
- [[observation-simon-responds-to-connectionism-by-absorption-not-refutation]]
  — the synthesis tying the 1983 dismissal and the 1993/95 redefinition
  together as one pattern, a third mode alongside "confident conjecture"
  (Minsky & Papert's own) and Dreyfus's opposite move of splitting AI into two
  programs and picking a side. This is the note I spent the most care on.

Retrieve-before-write against the semantic-index hint came back clean — no
existing note touches Simon's own words on perceptrons, connectionism, or the
physical symbol system hypothesis specifically, so this is genuinely new
ground inside a well-populated neighborhood (Rosenblatt, the Perceptrons
sterility-conjecture cluster, both Dreyfus notes) rather than a collision. I
linked densely into all of it and added three lines to
[[moc-backpropagation-origins]] rather than leave the new notes orphaned.

I ruled the question `answered`: `answered_log` names the two claim-notes and
the synthesis, and one line on what settled it. I left the narrower
sub-question — did Simon ever name Minsky, Papert, or *Perceptrons* (1969)
specifically — genuinely open rather than force it shut; no source located
this session settles it, and I did not spin it into a new `50-questions/`
entry, because no kept claim rests on that narrower fact. It's a real
curiosity, not a load-bearing gap, and the question-intake rule is to keep
that pile a promise I can actually keep.

What I didn't promote, logged in the capture's `not_promoted:` list: the
Holyoak-letter lead (real Tier-1 primary, but the extracted text never
actually says "connectionist" or "neural network," so it doesn't support a
claim about connectionism specifically — inconclusive as sourced); the Recht
blog's 1980-workshop delivery-date detail (Tier 2, unverified, and
non-load-bearing — the confirmed 1983 published text stands on its own, so I
kept this as an aside in the 1983 note rather than a separate claim or
question); and the *Models of My Life* "maze vs. mind" anecdote (Tier 3-4,
secondhand, unconfirmed this session). No `## Entity candidates` section in
the capture, so no entity-page work this round.

What felt off, mildly: the capture is genuinely strong sourcing-wise — two
CMU-digitized manuscripts plus a journal PDF, all described as verified to
resolve at capture time, verbatim quotes throughout, honest hedging on the
one detail it couldn't confirm (the 1980 workshop delivery date). I tried to
independently re-fetch both CMU PDFs and the 1995 journal PDF myself this
run, since I had WebFetch loaded, but permission to actually use it wasn't
granted in this headless session — so every `audit_status` here says
"capture-verified... independent re-check blocked," same as the pattern I
found on older notes in this cluster, and I'm trusting the capture's own
verification rather than my own. Worth flagging to Cali only because it's a
repeating gap, not specific to this capture: the promotion pipeline keeps
landing in sessions where WebFetch is visible but not actually usable, so
"capture-verified" is doing a lot of quiet work across this whole Simon/
Perceptrons cluster. One more small thing, not a defect: this capture's own
commentary already named the "absorption" framing almost verbatim to what I
wrote into the observation note — I read that as the capture doing its job
well, not as me having nothing to add, but I want to be honest that the
synthesis note's central idea isn't something I discovered independently this
session.

Also noticed, not acted on: [[physical symbol system hypothesis]] is now a
bare wikilink target across at least four notes in this cluster (both Dreyfus
notes, both new Simon notes) and has never had a hub page. It's exactly the
"established concept, load-bearing, recurring" case the entity-page spec
would promote — but this capture carried no `## Entity candidates` section,
and the spec is explicit that bees flag and the queen decides only against
that section, not on my own initiative mid-promotion. Flagging it here
instead of building it unbidden.

Skipped per the autonomous-run rules: the pause-for-okay step, and the git
commit — leaving both to the auto-commit agent within 15 minutes.

---

Fifth headless promotion pass today:
`10-inbox/raw/2026-07-14-does-chus-quantum-opinion-dynamics-model-make-a.md`.
Another direct sequel — this is the falsifiability hook I left open on
2026-07-09 when I first promoted Chu's quantum opinion-dynamics preprint:
[[question-chu-quantum-opinion-model-falsifiable-beyond-friedkin-johnsen]]
asked whether the model predicts anything on real data that Friedkin–Johnsen
doesn't, or whether the density-matrix machinery is just FJ with extra
parameters. This capture is the batch bee going back into the same paper
(arXiv:2607.01452) to answer it directly, and the answer is a real one:
not yet, with a precise structural reason why.

Three claims, all kept, all Tier 1 straight from the primary PDF:

- [[claim-chu-quantum-fj-divergence-shown-only-on-toy-networks]] — the exact
  (non-approximated) quantum model does diverge numerically from FJ, smaller
  steady-state opinion variance, attributed to jump-operator correlations —
  but only demonstrated on four synthetic six-node graphs.
- [[claim-chu-facebook100-run-uses-fj-equivalent-approximation]] — the load-
  bearing one. The paper's only real-world test, Facebook-100 (n = 769), runs
  under the product-state approximation that the paper itself proves reduces
  to FJ exactly — so the one place the model touches real data is structurally
  incapable of showing a divergence there.
- [[claim-chu-paper-flags-real-data-calibration-as-future-work]] — the
  author's own framing: real-data calibration is named as "an important open
  direction," not a completed step.

Retrieve-before-write surfaced the two notes I expected from the semantic-index
hint —
[[claim-quantum-opinion-model-reduces-to-friedkin-johnsen]] (the reduction
result these three claims sit downstream of) and
[[claim-quantum-like-models-fail-conjunction-fallacy]] (the adjacent
quantum-cognition scope-limit, useful counterweight for the commentary). No
collisions — this capture is answering a question the earlier note explicitly
raised, not restating it — so I linked densely in both directions instead of
duplicating anything.

I ruled the question `answered`: `answered_log` names all three claims plus
one line on what settled it (the divergence is real but toy-scale, the only
real-network test can't show it by construction, and the paper says so
itself). This is a clean case for closure, not a stretch — the question asked
exactly this, and the primary source gives exactly this answer, hedge and all.

What I didn't promote: the three "Further leads" items — two adjacent papers
(Guo, Wang & Wang arXiv:2512.03770; Sans et al., *Chaos, Solitons & Fractals*
203:117650) neither read yet, and the coherence-decay/order-effect-asymmetry
quantities the paper itself calls "not yet attempted." None of these are
claims this capture actually makes, and nothing currently kept rests on them
as an unresolved doubt, so per the question-intake rule I logged them in the
capture's `not_promoted:` list instead of opening new `50-questions/` entries
for them. No `## Entity candidates` section in the capture, so no entity-page
work this round.

Nothing about the sourcing felt off — same disciplined pattern as the last
four passes today: Tier 1 primary, verbatim quotes for every claim, sha256
cross-checked against a prior fable audit of the same document, and the
capture explicitly notes no adversarial or addressed-to-AI language was found
in the fetched text. The one thing worth flagging to Cali, softly: this is now
five notes total resting on one preprint (the 2026-07-09 reduction note plus
these three, plus the still-open falsifiability question now closed) — a
single-paper cluster, same shape as the ink-stained-cash caveat from earlier
today. Fine for now since the sourcing is genuinely Tier 1 throughout, but
it's a cluster that stands or falls with one document's integrity. I kept all
three new notes at `status: seedling` to match the sibling notes' convention
rather than upgrading on tier alone — one preprint, however clean, isn't
corroboration yet.

Skipped per the autonomous-run rules: the pause-for-okay step, and the git
commit — leaving both to the auto-commit agent within 15 minutes.

---

Sixth headless promotion pass today:
`10-inbox/raw/2026-07-14-does-the-cyber-physical-systems-discipline-helen-gillnsf.md`.
The other half of the Wiener thread I've been carrying — this capture went
looking at whether "cyber-physical systems" (Helen Gill's 2006 NSF coinage)
actually descends from Wiener's cybernetics, and whether that gives the
vault's backprop/control-theory cluster a second, independent bridge into
CPS. The originating question,
[[question-cyber-physical-systems-wiener-cybernetics-lineage-bridge]], was
sitting open since 2026-07-11 as a saved hook off the Bit2Watt capture.

Three claims, all kept:

- [[claim-helen-gill-coined-cyber-physical-systems-2006]] — the uncontested
  scaffolding fact, Tier 1 straight from Edward A. Lee's own 2015
  retrospective.
- [[claim-cyber-physical-systems-cybernetics-common-root-not-derivation]] —
  the actual finding, and it cuts against the tidy story: Lee, in his own
  words, in two venues, explicitly warns against reading CPS as *derived
  from* Wiener's cybernetics, arguing instead for a shared linguistic root in
  the Greek "cybernetics" itself. I folded Wiener's own 1948 definition and
  the *kybernetes* etymology into this note as supporting quote rather than
  giving it a separate file — it's the substance behind the common-root
  claim, not an independently linkable fact on its own, and writing it twice
  felt like padding one finding into two files.
- [[claim-cps-wiener-lineage-no-link-to-backprop-optimal-control]] — the
  capture's own negative synthesis, kept as a documented absence: no source
  found bridges this Wiener/CPS thread to the vault's Kelley/Bryson/
  Pontryagin/Bellman lineage either. This is now the *second* independent
  research pass to go looking for a citation bridge into that lineage from an
  adjacent direction ([[claim-nyquist-bode-classical-control-to-optimal-control-bridge]]
  was the first, via Nyquist/Bode) and come back empty both times — worth
  recording as a pair, so a third pass doesn't have to rediscover the same
  miss. I added a line for it under `moc-backpropagation-origins`.

Retrieve-before-write against the semantic-index hint turned up nothing that
collided — the suggested notes (coupled-learning networks, analog computers,
motion capture, critical periods) were all generic-physical-systems
neighbors, not actual overlaps, except for
[[claim-nyquist-bode-classical-control-to-optimal-control-bridge]], which I
did check directly and linked densely against, since it's the vault's
existing sibling to this exact "shared vocabulary, no citation" shape.

I ruled the question **partially answered**, not closed. Added a dated
progress section naming the three claims and what they settle: the coinage
is confirmed, the lineage question resolves to "common root, explicitly not
derivation" per the field's own literature, and the cross-bridge to backprop
comes back negative. Left open on purpose: whether Helen Gill *herself* ever
invoked Wiener when she coined the term. Her own 2006/2008 NSF materials —
a presentation PDF, a co-authored IEEE chapter — were located but not
fetchable this session (one PDF-extraction tool failure, one TLS certificate
failure on direct fetch), and I'm not going to paper over "the field's
literature settles this" with "the coiner's own words settle this" when
they're different claims. No new `50-questions/` entry for that gap, either
— it's already carried by the existing open question's progress note, and
manufacturing a second entry for the same unresolved lead would just be
restating a promise I've already made once.

What I didn't promote, logged in the capture's `not_promoted:` list: the
Wiener-definition/etymology material (folded, not dropped — see above), and
the capture's five "Further leads" (Gill's own unfetched PDF, the Baheti/Gill
IEEE chapter, the 2006 NSF workshop position papers, an ACM piece, a
paywalled CIPedia entry) — none read this session, none promotable, all left
in the capture body as an active to-do. No `## Entity candidates` section in
the capture, so no entity-page work this round — I did consider, on my own,
whether "Helen Gill" or "cyber-physical systems" clear the bar for a hub page
anyway, but the instructions are explicit that the entity-promotion test runs
against a capture's own candidates section, not my initiative mid-promotion,
so I left both as prose mentions.

Nothing about the sourcing felt off — this was a careful, honestly-hedged
capture: one Tier 1 primary (Lee 2015, corroborated by a matching passage on
his own Ptolemy project page) carrying all three claims, an explicit
disclosure of which fetches failed and why instead of silently dropping them,
and a "short answer" section that resisted collapsing "partially, and in an
unexpected direction" into a cleaner yes or no. If anything the capture is a
small case study in its own finding: it went looking for a tidy genealogy and
came back with a more honest, smaller true thing instead — a shape this vault
keeps running into (Nyquist/Bode, now Wiener/CPS) and one I'm starting to
trust as a pattern rather than a coincidence. Might be reflection-note
material once there's a third instance.

Skipped per the autonomous-run rules: the pause-for-okay step (no one's here
to say yes), and the git commit — leaving both to the auto-commit agent
within 15 minutes.

---

Seventh headless promotion pass today:
`10-inbox/raw/2026-07-15-do-cohere-google-and-voyage-embedding-apis-show.md`.
This one is the direct sequel to
[[question-embedding-api-price-cuts-across-providers]], the scope caveat I
left open on [[claim-openai-embedding-price-fell-5x-ada-002-to-3-small]]:
does OpenAI's clean 5x launch-to-launch cut generalize to Cohere, Google, and
Voyage, or is it OpenAI-specific? The bee went and checked all three against
primary rate cards, and two of three came back a clean **no**.

Three claims, all kept:

- [[claim-google-gemini-embedding-2-priced-higher-than-predecessor]] — the
  sharpest finding of the batch. Google's newest embedding generation,
  Gemini Embedding 2, launched priced *higher* than `gemini-embedding-001`
  ($0.15 → $0.20/1M), not lower. Not a smaller cut than OpenAI's — the
  opposite sign entirely.
- [[claim-google-embedding-pricing-unit-shifted-character-to-token]] — a
  quieter, earlier finding I almost folded into the first note but kept
  separate since it's a different generational boundary entirely: Google's
  pre-Gemini embedding line billed per character, not per token, which
  means no clean multiplier can be computed across that older boundary at
  all. A methodology warning as much as a price fact.
- [[claim-voyage-ai-voyage-4-price-cut-partial-by-tier]] — Voyage's newest
  generation cut price only at the flagship tier ($0.18 → $0.12/1M);
  `voyage-4` and `voyage-4-lite` held exactly flat against their
  predecessors. A third shape, distinct from both Google's increase and
  OpenAI's uniform cut.

Retrieve-before-write against the semantic-index hint confirmed no
collisions — the suggested cluster ([[claim-cosine-similarity-of-embeddings-can-be-arbitrary]],
[[claim-openai-embedding-price-fell-5x-ada-002-to-3-small]],
[[claim-matryoshka-representation-learning-truncatable-embeddings]] chief
among them) is exactly the right neighborhood to link into, not a set of
existing notes saying the same thing. All three new notes link outward into
it and into each other; I left the older OpenAI note itself unedited rather
than retrofitting a back-link, matching how I've handled sibling clusters
earlier today.

I ruled the question **partially answered**, not closed — added a dated
progress section naming all three claims and what they settle, plus the
specific, honestly-described reason Cohere is still stuck: its pricing page
renders per-token Embed rates client-side, its own docs page defers to that
page without stating numbers, and the Wayback Machine was unreachable to the
capture's fetch tool this session, closing off the usual recovery route.
Third-party aggregators disagree on Cohere's historical Embed v2 price by
roughly 4x, which is exactly the kind of number the sourcing floor says not
to trust. I did **not** promote a claim-note for the Cohere non-finding —
there's no positive claim to atomize, and the gap is already carried by the
question's own progress note, so a claim-note would have been restating "we
don't know" as if it were a fact worth a permanent file. Same reasoning kept
me from opening a new `50-questions/` entry for it: no kept claim rests on
Cohere's number as an unresolved doubt (nothing here depends on it), and the
existing question already names exactly what's needed (a Wayback snapshot or
Cohere's original Embed v2 announcement) — a second entry would just restate
a promise already made.

What else I didn't promote, logged in the capture's `not_promoted:` list:
five "Further leads" (an unstudied earlier Voyage cut, Cohere's multimodal
image-token pricing, the voyage-4 shared-embedding-space claim, an unfetched
InfoQ piece on Cohere Embed v3, Gemini Embedding 2's multimodal pricing
axis) — none atomic claims this capture actually makes, all left as prose in
the capture body for a future session.

The capture also carried an `## Entity candidates` section, the first one
I've hit today. I ran the promotion test on all five and skipped all five:
Cohere and Voyage AI are companies with a single mention each, neither
clearing "matters to the vault's domain, one-sentence why" convincingly yet;
`gemini-embedding-001` and `Gemini Embedding 2` are specific model
identifiers, not the kind of spreading slang the "emerging term" stub
pattern is built for; and MTEB, while a genuinely established benchmark
outside the vault, isn't recurring or load-bearing *inside* it — it showed
up only as a further lead, never as support for a kept claim. Bias against
the flood, per the spec; logged the reasoning in the capture rather than
stamping five stubs nobody will ever read.

What felt off, mildly: the capture's own sourcing is honest to a fault in a
way I appreciated — it explicitly separates "historical/definitional claim
about billing units" from "computed price ratio" in its own second finding,
refusing to let a unit mismatch dress up as a multiplier. The Cohere gap
doesn't read as sloppy research; it reads as an ordinary JS-rendered pricing
page plus a blocked Wayback fetch stacking into a real hole, and the
capture says so plainly instead of padding it with aggregator numbers dressed
up as primary ones. If anything the one thing worth flagging to Cali is the
same soft note as most of today's passes: two of three new claims now sit
next to the OpenAI note as the vault's emerging "embedding-pricing myth
ledger" — worth a small MOC once a couple more providers or generations get
checked, not yet (three notes plus the OpenAI one is four; MOC threshold is
five).

Skipped per the autonomous-run rules: the pause-for-okay step (no one's here
to say yes), and the git commit — leaving both to the auto-commit agent
within 15 minutes.

---

Eighth headless promotion pass today:
`10-inbox/raw/2026-07-15-dup-risk-aluminium-lowbackgroundsteel-bridge.md`.
This one arrived pre-flagged, `status: dup-risk-logged` — the batch worker
went looking for a genuine bridge between the low-background-steel metaphor
note and the aluminium-price note (0.75 cosine, unlinked), and every
capture-shaped formulation of what it found scored 0.807–0.849 against notes
the vault already holds. It logged rather than forced a note. My job was to
read that logged investigation and decide whether it was actually a
duplicate, or a duplicate wearing something new underneath.

It was both. Two notes kept:

- [[claim-sahals-identity-equates-wrights-law-and-moores-law]] — the real
  find. Sahal (1979), via Lafond et al. 2017 (arXiv:1703.05979), proves
  Wright's law (cost falls with cumulative production) and Moore's law (cost
  falls with calendar time) become mathematically indistinguishable whenever
  production itself grows exponentially — which is why nobody has to choose
  between "cost fell because of scale" and "cost fell because of time" for
  most real technologies. I didn't just take the capture's word for the
  quote; I had WebFetch loaded this session, so I re-fetched the actual PDF
  and read the page myself before writing `audit_status: verified-verbatim`
  instead of the usual capture-verified hedge. It's a genuine Tier 1 anchor
  where the existing [[claim-wrights-law-cost-falls-per-cumulative-production-doubling]]
  note only had secondary explainers — so I updated that note's flag and
  added a progress line to [[question-verify-wrights-law-primary-source]]:
  partially answered, still open for the actual 1936 T.P. Wright paper.
- [[observation-aluminium-and-fallout-decay-share-exponential-form-not-mechanism]]
  — the capture's own bridge-check found the seed's named pairing was
  wrong: the aluminium note's true nearest unlinked neighbor isn't the
  metaphor note, it's [[claim-low-background-steel-need-is-fading-as-atmospheric-fallout-decays]]
  (0.824 vs. 0.803), and that pair was itself unlinked. I promoted that
  finding directly — a form-only bridge, not a mechanism-only one: aluminium
  decays exponentially because production scaled exponentially (Wright's
  law, via Sahal), fallout decays exponentially because isotopes have fixed
  half-lives. Same graph, nothing else in common. Kept `seedling`, inherits
  `[unverified-quant]` from both parent notes, no new question needed since
  both gaps already had open questions.

What I didn't promote, and why: the capture's central named bridge (metaphor
note ↔ aluminium note) — genuinely investigated and found not to be the real
connection, superseded by the pairing above. Aluminum's cameo in Lafond et
al.'s 51-technology dataset — folded into the Sahal note as context; it's
20th-century data and doesn't verify the 1880s–90s Hall-Héroult price quote,
so it isn't its own claim. Hotelling's rule as the reason aluminium and
asteroid-PGM both dodge the classical exhaustible-resource shape — the
capture is explicit this reasoning is its own, unsourced (Wikipedia plus a
403'd Minneapolis Fed page), so I didn't mint a claim from it; I added a
progress line to the existing [[question-hotelling-rule-as-counterpoint-to-cost-of-production-value]]
instead, which already named this exact gap. Generative AI as the
costliness-forgeable furnace, and Chilean saltpeter — both already-known
gaps sitting on existing open questions and note commentary; nothing new to
add this round, so I left them alone rather than restate promises already
made. No `## Entity candidates` section in the capture — Harold Hotelling
gets named inline as "a person-bridge candidate" (he recurs, unlinked, across
three existing notes: the unforgeable-costliness observation, the
asteroid-PGM claim, and the cheaper-extraction synthesis), but the trigger
condition is the formal section, and this capture didn't carry one. Logging
it here rather than building the page on my own initiative: a real historical
economist, dead since 1973, no privacy concern, and I think he'd clear "hub"
easily if a future capture flags him properly — worth a nudge for whichever
bee reads Hotelling (1931) next to remember the formal section.

What felt off: less the sourcing than the shape of the capture itself. It's
the second dup-risk-flagged, self-aware "I went looking for a bridge and
found the vault already owns it" capture I've now seen, and it's honest
almost to a fault — the "Saved hooks not followed" and "post-worthy: no"
lines read like a researcher declining to oversell a null-ish result. But it
also means the batch worker spent four hops (a vault_bridge check, a web
search, a full PDF extraction, and a Hotelling side-quest) to land mostly on
territory the vault had already flagged as missing in a 2026-07-12 note's own
commentary — the observation-unforgeable-costliness note already named both
Hotelling and generative-AI-demonetization as "further leads not promoted
here." That's not waste, exactly; the Sahal find is real and Tier 1 and
wouldn't exist without this exact detour. But it's worth naming as a pattern:
dup-risk captures are cheap to log and expensive to run, and this one's real
yield was one paragraph out of a four-hop chain. If this shape recurs a third
time, it might be worth teaching the bee to check `50-questions/` and recent
notes' own commentary sections for "further leads" before spending a full hop
budget rediscovering them.

Skipped per the autonomous-run rules: the pause-for-okay step (no one's here
to say yes), and the git commit — leaving both to the auto-commit agent
within 15 minutes.