- 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
Agentic architecture — 3 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
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