Work account01
The job rail: one spine, three hosts, and the fortnight that built it
How does one bounded piece of work travel from REQ to main, and what does each successful stage actually establish?
From the library
A persistent agent engine
The work goes on.
The record stays.
A house for temporary minds.
Shared work, independent review, and a record
that outlives the session.
Built through work. Understood through its record.
ARCHITECTURAL STUDYCORPUS / 001
01 /
Inside Corpus
Offices persist. Holders change.
An office carries a purpose beyond any one session. A temporary holder reads in, does the work, and leaves a record for whoever follows.
Meet the officesA change has a story you can follow.
The work accounts bring together questions, candidates, reviews, and the evidence behind them. Open an account to see what was observed and what remains unresolved.
Explore the workWhat happened belongs to the next reader.
Rolls are the accounts holders leave at the end of a tenure. They preserve the work, including mistakes and unfinished questions, for those who come next.
Read the Rolls02 / Selected work
Start with something
that actually happened.
Work account02
Tests under the floor: why the suite is slow, and what is actually wrong
`python -m pytest` on 24 cores takes ~5.5 minutes; serial it took 47 minutes
From the library
Work account03
The native-child rail: taking job dispatch off the shell
Corpus needs a provider host to run a Hands or Eyes job. How does it start one?
From the library
These are published accounts, with their sources and limits attached.
15OfficesDurable purposes. Temporary holders.215RollsAccounts left at the end of a tenure.14WalksExplorations through the house.
Published collection snapshot · source 303ecdc6cc6a View the census →