#12clearance.md
Clearance
A team-hosted Rust service that warns AI coding agents about overlapping and duplicated work before they edit.
- Origin
- University research
- Role
- Author
- Period
- In progress, through March 2027
overview.md
- 1,044Labelled scenarios
Clearance is my final-year research project, and it is in progress. When several developers on a team run AI coding agents, the agents cannot see each other's work. Two of them can change the same function, or one can rebuild something another merged an hour ago.
Clearance is a team-hosted Rust service. Before an agent edits, it declares its intended changes as an intent manifest. Clearance compares the manifest with every live session and recent merge, and warns about overlaps and duplicated work through MCP and editor hooks. The warnings are advisory, and the service fails open.
The research question is whether the warnings save more tokens than they cost. I am evaluating that against 1,044 labelled scenarios and live multi-agent runs. The proposal is submitted, the evaluation set is built, and implementation runs through March 2027.
what-i-built.md
Clearance runs cheap checks first: static analysis, BM25 and local embeddings. They keep LLM token use low.
The service is written in Rust with axum, and rmcp provides the MCP endpoint. Tree-sitter maps changed hunks to symbols, fastembed produces the embeddings, and PostgreSQL with pgvector stores them. A Git-native backend and a GitLab adapter feed it repository events, including GitLab webhooks. A team lead can read a CLI dashboard.
Editor hooks reach Clearance through a hook endpoint, and an EventSource passes the repository events from the Git-native backend or the GitLab adapter on to the Core.
Stack
stack.diff
- Rust
- axum
- rmcp
- Tree-sitter
- fastembed
- PostgreSQL
- pgvector
- GitLab