# Robert DeLanghe
> AI agents ship code. I write the contracts that keep them in check.

I'm a senior engineer at Aura, where I built the controls for shipping AI-written code after unreviewed agent commits reached main. I open-sourced the approach as prx: agent changes land as merged PRs, each git write checked against the capability the agent holds.

Senior Software Engineer · Brooklyn · Aura · Recurse Center · Bennington

## Links
- [GitHub](https://github.com/bounded-systems)
- [LinkedIn](https://www.linkedin.com/in/rdelanghe/)
- [Résumé](https://robertdelanghe.dev/resume)

## Selected work
- [prx](https://github.com/bounded-systems/prx): The agent-run work-unit CLI: capability-scoped agents whose privileged effects are verified against a signed owner, driving a work unit through one signed pipeline to a merged PR.
- [guest-room](https://github.com/bounded-systems/guest-room): Guest-agnostic room+door capability runtime — an agent reaches the outside world only through the door references it's handed.
- [claude-box](https://github.com/bounded-systems/claude-box): A capability-secured box for agent sessions — its authority is the door references it holds (keeper/scout/concierge/net), parent-agnostic.
- [door-kit](https://github.com/bounded-systems/door-kit): In-box door-client SDK for claude-box's capability doors (keeper/scout/concierge/spawn), over the guest-room protocol.
- [ocap-provenance](https://github.com/bounded-systems/ocap-provenance): Capability-use provenance — a schema + SLSA mapping binding each privileged effect to a signed owner and an auditable chain.
- [string-audit](https://github.com/bounded-systems/string-audit): Cost-aware, grounded content auditor — typed string symbols, type-scoped audits, CAS-memoized LLM calls.

## Writing
- [How I build my résumé — and how mapping it to Google Docs got my account disabled](https://robertdelanghe.dev/blog/resume-pipeline-google-docs-incident): A JSON Resume source of truth renders to a site, a PDF, and a native Google Doc for review. The Google Docs leg's publish cycle looked enough like a bot to get the account behind it disabled.
- [How to keep agent-authored code from drifting](https://robertdelanghe.dev/blog/agent-authored-code-drift): When agents write modules in parallel, the modules stop agreeing with each other. That is a contract-enforcement problem, and you can make CI catch it.

## Markdown
- [Robert DeLanghe — Senior Software Engineer](https://robertdelanghe.dev/index.md)
- [Résumé](https://robertdelanghe.dev/resume.md)
- [Writing](https://robertdelanghe.dev/blog.md)
- [Conformance](https://robertdelanghe.dev/conformance.md)
- [Provenance](https://robertdelanghe.dev/provenance.md)
- [Colophon](https://robertdelanghe.dev/colophon.md)
- [How I build my résumé — and how mapping it to Google Docs got my account disabled](https://robertdelanghe.dev/blog/resume-pipeline-google-docs-incident.md)
- [How to keep agent-authored code from drifting](https://robertdelanghe.dev/blog/agent-authored-code-drift.md)