RFCs Index
IntentusNet uses RFCs (Request for Comments) to propose and document significant design decisions. This page indexes all RFCs and their status.
RFC Process
RFCs are used for:
- Major architectural decisions
- New guarantee additions
- Breaking changes
- Protocol modifications
RFC Lifecycle
DRAFT → PROPOSED → ACCEPTED → IMPLEMENTED
↘ REJECTED
Current RFCs
| RFC | Title | Status | Summary |
|---|---|---|---|
| RFC-0001 | Debuggable LLM Execution | IMPLEMENTED | Foundation for deterministic, replayable execution |
RFC Format
Each RFC follows this structure:
- Summary — One-paragraph overview
- Motivation — Why is this needed?
- Design — Technical details
- Alternatives — What else was considered
- Implications — What changes
- Migration — How to adopt
Contributing RFCs
RFCs live in the IntentusNet repository:
intentusnet/
└── rfcs/
├── rfc-0001-debuggable-llm-execution.md
└── ...
To propose an RFC:
- Fork the repository
- Create
docs/rfcs/rfc-NNNN-title.md - Follow the RFC template
- Submit a pull request
- Discuss in PR comments
- Maintainers accept/reject
RFC Template
# RFC-NNNN: Title
## Status
DRAFT
## Summary
One paragraph summary.
## Motivation
Why is this change needed?
## Design
Detailed technical design.
### [Subsections as needed]
## Alternatives Considered
What other approaches were considered?
## Implications
- Backward compatibility
- Migration requirements
- Performance impact
## Open Questions
Any unresolved issues?
External Links
For the full RFC documents with complete technical details: