Kekulé · the dream cycle · 1 Sep 2026
A dream journal, not a dashboard.
Four passes run as one scheduled job: replay and consolidation, remote association, pruning, speculation. The pass that justifies it crosses the graveyard with capability tracking — when a constraint moves, every dead experiment depending on it is re-checked.
seven a week, capped
30% of offered — accepting is cheap
8% — two weeks of two people
3% — the number that justifies the slot
The yieldAccepting is cheap and running is not, so the two rates are reported apart. A pass that offered nothing anybody ran would be a reading list; a pass that offered nothing anybody published would be a hobby. Both are counted from the ledger rather than estimated.
- 1
Expiring delegated credentials are a backpressure signal the orchestrator is not using
Remote association·Auth Broker × Backpressure
Signalin the wildcard lanePairs of fields with cosine similarity > 0.72 and graph distance > 3 — no shared claim, citation, experiment or person. Ranked by the gap between the two.
auth-broker and backpressure sit close in embedding space and have never shared a claim, a citation or a person. The broker's short-lived, task-scoped credentials already encode a bound on how long and how wide an agent may act; the bounded-fanout queue enforces a similar bound by a separate mechanism, and the two could share one budget. Accepted as a join hypothesis because the shared constraint is structural, not lexical — David and Travis to draft a thought experiment.
4 rows behind it
- clusterAuth BrokerSimilarity 0.78, graph distance 4. No shared claim with backpressure.
- clusterBackpressureBounded-fanout claims cite queueing literature; the broker cites authorisation. No overlap in either direction.
- libraryBackpressure defaultsThe recommendation bounds concurrency by a queue depth, with no reference to credential lifetime.
- libraryDelegated authorityBounds a credential by scope and TTL, with no reference to concurrency.
- 2
A compiled skill wiki as the retention policy for citizen-developer artefacts
Remote association·Personal Wiki × Citizen Developers and Org Slop
- 3
Summarise-before-store beat store-then-retrieve in three unconnected experiments
Replay·Agentic Memory System × Personal Wiki × Learning Agents × Non-Weight-Bound Continuous Learning
- 4
Three claims in cyber-cold-war have had no supporting signal added since April
Pruning·Cyber Cold War
- 5
Calibrate sensing-agent anomaly alerts against a human panel the way judges are calibrated
Speculation·Eval Harnesses × Sensing Agents
- 6
Run the token cost ledger method on realtime voice sessions
Speculation·Cost redux on tokens × Voice and Vision
- 7
Argus: AU-channel inference-card pricing moved; g-onprem-h100-cluster depends on that constraint
Graveyard × capability·On-Prem Inference × US Non-Dominance
How this is madeEach pass is a scheduled query over the graph — embedding proximity minus graph distance, claim decay against supporting signal, a method never tried on another problem class — and the paragraph is written afterwards to explain what came back. That order is the defence: generated connections are fluent, confident and mostly spurious, so every item shows the rows it was derived from and an item you cannot check is an item to reject. Accepted items land in the proposal queue, so the cycle produces work rather than a report.