- All
- Riteangle 17
- Decision systems 10
- Agent architecture 8
- Operations 8
- Context engineering 6
- Guardrails 6
- Data platform 5
- Agent evals 4
- Agentic architecture 3
- Advertising 2
- Marketing 2
Operations — 8 posts
Automating my job hunt outreach with an agent that finds, researches, and drafts — and leaves sending to me
A director/VP-level job search runs on outreach nobody automates safely, because the risky part is the send. This system automates finding, researching, and drafting end to end, and keeps the one irreversible step out of its code entirely. Underneath it, memory is split three ways: a table store for quantities, an embedding index for meaning, a graph for relationships. The question is no longer how to store data for a human to read, but how to organise it so an agent retrieves the right slice before a model call it pays for. The retrieval half gave the more surprising results: indexing each document's own title bought nearly what the vector index did, four employers' near-identical policies could only be separated by file path rather than by any retriever, and a negative result about rank fusion did not survive re-running it on a larger corpus.
44 min read
Forward-deployed engineering under five job titles, and the handoff test that decides if it worked
A company that embeds an engineer inside one operation is buying a specific kind of work, and almost never writes down the part that decides whether it paid off. I did that work under five different titles before I had a name for it. Here is the defect that showed up in every one of them, and the test I never once wrote into a handover document.
9 min read
Enforcement was version one, fairness was version four
I built a productivity measurement system for a distributed team, with a five-step consequence ladder ending in exit. The ladder worked from the first day. The component that would have made the comparisons fair was version four, and its design was never written.
10 min read
Governance was the first thing to stop paying for itself
I was asked to hit a cost target across three functions. The plan I came back with removed my own seat, on the grounds that it was buying governance at the price of three times the execution capacity. Here is the arithmetic and the argument, including the part I never got to verify.
8 min read
Routing decisions without a model in the loop
Before riteangle I ran an allocation system with revenue attached. It had the same shape — a language model at the ingestion edge, arithmetic in the middle — and in two respects it was better than what I have now. Here is the precedent, and the thing I should port back.
9 min read
The curriculum was the incident log
I had four weeks to move one person's operational knowledge into a team's heads. So I built the syllabus backwards out of three real incidents, organised around one question. The question mattered more than any of the content.
8 min read
The same grid, three kinds of evidence
I used one instrument to assess my team, myself, and the market I wanted to move into. All three produced a capability grid that looked identical. Only one of them had evidence underneath it, and nothing in the presentation said which.
9 min read
Designing global talent systems
The spreadsheet always shows the wage differential. The coordination, leadership, and redesign taxes are what it leaves out — and they are where the cost actually lives.
7 min read