Category building · 5 artifacts
Agent Systems
Published work collected in the Agent Systems building.
Artifacts in this building5 published
LETowards Automating Eval EngineeringI read [Viv’s “Towards Automating Eval Engineering”](https://x.com/Vtrivedy10/status/2079976006644072796), about a skill that builds evals from an agent repository and its traces.
What stands out is that it does not try to one-shot the eval. It interviews the user, builds a Harbor task, and then checks both the agent and verifier trajectories for shortcuts. I like the idea of turning real failures into durable tests; I just want the loop to stay small enough that the eval system does not become another thing to constantly maintain.LearningEval EngineeringAutomated EvaluationLEWhy We're BuzzingI read [jack’s “why we’re buzzing”](https://x.com/jack/status/2080056638820450400), about Buzz, an open-source workspace that keeps people, agents, conversations, code, and approvals in one signed record.
The part I keep thinking about is the context problem. Agents can only help with what they can see, and we lose a lot between chat, code, CI, and review tools. I am curious how much of Buzz requires replacing the whole workspace versus making the seams between the tools I already use more coherent.LearningAgent ContextCryptographic IdentityVIAgent Swarms — Model EconomicsMy dylanmccavitt/skills repo was relatively close to this proposed structure in the sense that routing agents correctly, was the focus for an autonomous loop. I''m taking pieces of this article and implementing it in to my skills repo with some missing gaps that this currently brought up.Visualmodel economicsAI agentsNOCleaning my agent configurationsA reflection on simplifying Codex agent configuration to reduce hidden context, improve predictability, and measure whether customization is actually helping.NoteCodexskillsPRCodex Orchestration SkillsA visual model of the dylanmccavitt/skills repository and its evolving Codex delivery system.
Four constrained roles move tracked repository work from research to verified integration: Gepetto coordinates; Pinocchio implements one approved leaf; a reviewer validates the exact pull-request head; Jiminy rechecks merge gates and verifies the combined result. Checkpoint preserves role and ownership when a long-running task moves into a fresh Codex task.
The repository has evolved from written role contracts into a machine-readable workflow with typed packets, single-writer worktrees, exact-head proof, atomic state transitions, content-addressed context, continuation journals, heartbeats, pressure monitoring, and restart budgets.
Current work on July 22, 2026 continues that hardening: PR #19 atomically accepts orchestration events and PR #21 invalidates stale delivery proof. The attached visual links directly to the GitHub repository and live work.ProjectCodex skillsdelivery systems