RFCs
Request for Comments documents record significant design decisions before implementation. Each RFC has a number, a status, and a rationale section. Once an RFC is accepted, the design is binding unless superseded.
| Number | Title | Status | Source |
|---|---|---|---|
| ARCH-102 | Kythe Corpus Naming Convention | Accepted | View |
| RFC-001 | MVP Scope (Phase 1) | Accepted | View |
| RFC-002 | VName Signature Format Versioning | Accepted | View |
| RFC-003 | Multi-Language Indexer Architecture | Accepted | View |
| RFC-004 | MCP Tool JSON Schema Contracts | Accepted | View |
| RFC-005 | Cross-Language Edge Resolution Protocol | Accepted | View |
| RFC-006 | Graph RBAC Session Model | Accepted | View |
| RFC-007 | MCP SSE Transport | Accepted | View |
Writing an RFC
Create a file docs/rfcs/RFC-NNN-short-title.md in the main travsr repository using the template below. Open a pull request and tag it rfc. The RFC is accepted when the pull request is merged.
# RFC-NNN: Title
## Summary
One paragraph.
## Motivation
Why is this change needed? What problem does it solve?
## Detailed Design
The full specification.
## Alternatives Considered
What else was evaluated?
## Drawbacks
What are the costs of this approach?
## Unresolved Questions
What is left open?