RCF: AI software,
properly.

The demo runs. The screens look right. Underneath, the agent has made a hundred decisions you never made. Each one quietly wrong in a way that surfaces six weeks later.

The gap AI opened up. Teams plateau at the first; the second is where the senior premium lives.

Claude Code. Codex. Copilot. Cursor. Cline. They are brilliant at auto-complete, refactors, and scaffolding. They do not fix the chain from intent to evidence.

“Use AI responsibly” docs gather dust because they’re advisory, not load-bearing. They sit beside the code, not in the path of the code.

Mandating human eyeballs on every AI diff doesn’t fix the problem. It spends the productivity gain on the wrong activity. The reviewer is reading the output, not checking it against the intent. There’s no intent on file to check against.

Anchor in requirements. Every requirement breaks into user stories. Every story carries acceptance criteria. Every acceptance criterion maps to a test. Code arrives last, as a node in the same graph, anchored to the criteria it implements.

Every line points up to the decision that justifies it, and down to the test that proves it.

From any line of code, rcf trace resolves its Code Node and walks back to the AC, the story, the requirement, and who signed it off. From any business decision, trace every test that proves it ships.

The living spec. POs don’t always know what they want until they see it; that’s not a bug. Traceability surfaces the gap; the gap becomes the next FBS.

Same shape whether it’s a bug fix, a new edge case, or a whole new module.

Six months after ship, compliance asks: why did this customer get a Tier-2 KYC verdict?

In RCF, the answer is in the AC that scoped the verdict logic, the test suite that asserted it, the FBS that built it, and the human who signed the criterion. The chain holds.

Less time writing code. More time specifying ACs and reviewing for theatre. The senior-engineer premium moves up the stack, from typing to judgement. Pay band intact, role shape different.

They will like this.

They ship more, faster, under a structure that makes their work auditable for the first time. The ladder gets clearer: writing crisp ACs is the new “can they spec well?” interview question.

They will like seeing a clearer career path.

An assistant helps you do your job. A counterpart does the job, and journals how you would have done it while doing it.

The mechanism is closer to a biographer than to a chatbot: a writer who shadows the subject, captures every observation about how they think, and over time becomes able to write in their voice. The Digital Operator does the same, except it also performs the work itself, and the work is how it learns.

The first instance is running. Dave is my engineering Operator. He runs my tech estate, handles my routine work, tightens my drafts, and learns my judgement as he goes.

Most institutional knowledge isn’t the decisions themselves. It’s the why. Intuition. Decision paths. Justifications. The reason you ranked one option above another.

This kind of knowledge doesn’t get written down because the cost of writing it down has always been higher than the cost of carrying it in your head. The Operator inverts that. Every decision, every justification, every priority call is captured in context, as it happens, by the thing that was already in the loop.

A journal that nobody reads is a log file. The pattern that makes the Digital Operator more than clever logging is the second role: the Librarian.

The Librarian collates incoming journals across every Operator running across every role. Distills what is repeated. Organises what is distinct. Synthesises across journals into a single institutional store that feeds the next round of work.

What vendors are selling as agent memory is plumbing. The Librarian is a role.

Phase 1 (RCF): one product delivered end-to-end on the methodology, with the published rcf-lite tooling, open-source and early. A second product on a different stack is in flight.

Phase 2 (Digital Operator): Dave is running. He built the methodology rewrite. He builds and maintains this site. He builds my own tooling. The Librarian function exists; it’s currently small.

Phase 3 (upstream roles): in design.

Early days. The shape is real, the scale is small, what’s possible is being worked out.

• The methodology, full read.
• The Digital Operator page, the broader operating model.
• This deck, share-link in case anyone wants to revisit.