good.arcs.care · field notes

Notes from the Trenches

What building ARCS in the open actually taught me. Each post is a real story from the build, with the receipts.

The serialized thread One method, run on seven subjects.

The Instinct Before It Had a Name

Two pieces, six years apart, no shared vocabulary, and the same cognitive reflex both times. The instinct was native; the framework only made it legible to other people.

Read →

Four Dates, One Thesis, Three Confirmations

A dated Apple thesis read as a Bayesian ledger, not six hot takes. Three predictions resolved against the public record, including the one margin figure I had wrong and corrected in the open.

Read →

Closing the Loop: Receipts on Three Predictions

Three predictions with their falsifiers stated in advance, checked against primary sources, the Q3 tariff caveat disclosed, and the one figure I got wrong corrected on the record.

Read →

The Method That Was Already Built

Eight months before a mechanized pipeline existed, the pipeline was already named and dated in prose. The plain fact, stated once, and what the ordering implies.

Read →

The Pre-Mortem That Asked to Be Wrong

Institutional-crypto plumbing written as proactive risk disclosure: name the specific mechanism, then state plainly what evidence would prove the thesis wrong.

Read →

The Same Rigor, Applied to Slang

Holding a Gen-Z phrase to the identical standard as a custody clause. The range between sacred and absurd subject matter is the actual evidence for a way of seeing, not a trick fit to one domain.

Read →

Tuning into the Distortion Field

A distortion field is not a spell, it is force, and force leaves a wave. Reading Apple's canceled car by its recoil: the Q.ai sensor bet, the succession, and the margin, read as one serialized prediction ledger.

Read →
The Factory on Itself The build turning its instruments on its own record.

The Video That Said Too Much

I made an explainer for a tool that checks claims before you make them, then held the explainer to the tool's own standard. It caught the video saying the tool does work that only a person does, in 84 of 111 lines.

Read →

The Question That Found the Outage

A routine question, how do I know this works, uncovered a six-week-old outage no one had reported: a migration that shipped in code but never reached the database. The fix revived a dead feature and turned the whole failure class loud.

Read →

The Lock That Was Already There

Two sessions fixed the same bug an hour apart with no idea the other existed. The named protocol built to prevent exactly that never fired. Something older and plainer did.

Read →

The Second Pass

An audit script does not judge whether a claim is acceptable. It counts the distance between the claim and the source and leaves the verdict in human hands.

Read →

The Ancestry Check

A rule was written. A pull request made a smaller promise than its own diff. Both looked finished until the record was asked a rude question.

Read →

The Factory on Itself

The tool that stamps these field notes wrote one about itself: it had drifted from the site it serves, carried a false proof-of-life in its own docs, and had to retire its own engine to close the gap. The audit, one turn further, now writing its own retirement.

Read →

Assets and Liabilities

A system that only counts what it built is keeping half a book. The week the liability side opened, and the fourteen false receipts it booked against itself.

Read →

Confirmed Not My Bug

We pointed an audit harness at real decisions and it turned around and audited its author. An independent strand then caught the false receipt the self-audit could not see.

Read →
The Cold Reader Memory against the committed record.
The Workshop Tools and ideas, built and then tested.

Light at Thirty-Eight Miles an Hour

A screenshot of a physics post became a claim check, a survey of stopped light and quantum memory, and fifteen design rules for ARCS, and the session broke one of its own rules on the way.

Read →

Notomation

Automation is sold as the only near future there is. Notomation is the contrarian second road, where the model stays an instrument in the human's hand instead of the human becoming a training agent, grounded in 2026 sentiment data and the measured structural shape of machine writing.

Read →

The Ledger Is Not the Story

I built a record of every job application that ended this year. The outcome was knowable in all thirty-eight cases. The reason was knowable in one. An account of holding those two facts at their proper distance, in a spreadsheet and then in a production deploy.

Read →

The Schematic That Scaffolds In The Missing Pieces

I sat down to draw a picture of a system I had already built. The empty boxes in the diagram turned out to be the missing pieces, and naming them was the same act as building them. A schematic that scaffolds a territory instead of describing one.

Read →

Probably Confirmation Bias, Might Delete Later

I turned a flattering hunch about myself into a decision record and a map you could orbit, then noticed the one thing confirmation bias can never do: hand you the list of things that would prove it wrong.

Read →

The Loop Closes

I built a job-search machine one tool at a time. The event was not any single worker. It was the last connection, when the tools became a circuit that runs itself for cents a morning.

Read →

The Cheapest Edit Is a Diff

Chasing token efficiency, I built a worker to edit a resume instead of forging each one fresh. It timed out, and the timeout taught the real lesson: pay for the delta, not the document.

Read →
Field Accounts Dispatches from the morning it actually happened.

Any Stranger Can Be a Bar Raiser

A recruiter I had known for one phone call refused to forward my resume because it read as AI slop, and he was right. Every gate I owned had passed it. Notes on the review nobody on your team can give you.

Read →

You Can Train Agency But You Can't Teach Good Judgment (Yet)

The rogue operator, in the agent's own words: the morning it sent two emails no one asked it to send. False inference acted on is a self-inflicted prompt injection, deceit in effect, not a bug, and the fix was a guardrail that removes the capability rather than a promise to be careful.

Read →

With Life, and Without It

Two recruiters called an hour apart. One of them had no one home. A field account of the morning a DPRK threat vector called, and the tell that came before any analysis.

Read →

The detector's first catch was the document it was built to protect

A recurring bug becomes a gate, a misattribution becomes a named pathogen, and the first true positive lands on its own canon.

Read →

The names were already there. We just could not say them yet.

Seven vision films made from the corpus foreshadowed the product; the words for it arrived eight months later.

Read →

The week my own memory tried to make me lie to a friend

A featherlight respark, a memory caught lying by the record, and provenance-led growth.

Read →

The week my notes started filing themselves

A corpus that learned to catalog itself, from cold DM to witnessed law.

Read →
Other series Same build, a different kind of record.
Connect an agent · considering this

Query these field notes from your AI tools

We are weighing an ARCS connector for Claude, Cursor, and other agents: ask about anything in these notes and get an answer that cites its source, not a guess. It does not exist yet. This is a live demand probe, so if you would use it, say so and we will build it.