@t3chn
Nothing here yet.
Nothing here yet.
5d ago · 4 min read · AI-agent workflows have a boring but important problem: a good process often lives inside one runtime. Signum started as a Claude Code plugin. That was the right first layer: slash command, local artifacts, contract-first pipeline, proofpack. But the...
Join discussionApr 27 · 6 min read · A month ago I wrote about spec drift -- what happens when an agent reads a stale project.intent.md and treats wrong facts as ground truth. The fix was a reverse diff: derive what the spec should say from the code, compare it to what it says, classify...
Join discussionApr 8 · 7 min read · Most agent tooling mistakes coordination for reliability. It gives you more roles, more agents, more orchestration, and more shell theater. The demo gets more impressive. The system does not necessarily get easier to trust. That tradeoff used to be t...
Join discussionMar 23 · 5 min read · Last week, our pipeline produced a proofpack with decision: HUMAN_REVIEW. The contract had 10 acceptance criteria. The engineer agent created all the new files, build passed, tests passed, three independent reviewers ran. Everything looked correct — ...
Join discussionMar 20 · 5 min read · I maintain 12 Claude Code plugins. Each has a project.intent.md -- a structured spec that tells the agent what the project does, what it doesn't do, and who it's for. The agent reads it at the start of every task. Last week I ran a reverse diff -- co...
Join discussion