RFCs (Requests for Comments)
Design decisions in RegelRecht are documented through RFCs. Each RFC captures the problem, considered alternatives, and the chosen approach.
Index
| RFC | Title | Status |
|---|---|---|
| RFC-000 | RFC Process | Accepted |
| RFC-001 | YAML Schema Design Decisions | Accepted |
| RFC-002 | Authority Roles and Relationships | Accepted |
| RFC-003 | Inversion of Control | Accepted |
| RFC-004 | Uniform Operation Syntax | Accepted |
| RFC-005 | Standoff Annotations | Accepted |
| RFC-006 | Language Choice | Accepted |
| RFC-007 | Cross-Law Execution | Accepted |
| RFC-008 | Bestuursrecht / AWB Procedures | Accepted |
| RFC-009 | Multi-Organisation Execution | Proposed |
| RFC-010 | Federated Corpus | Accepted |
| RFC-012 | Untranslatables | Proposed |
| RFC-013 | Execution Provenance | Draft |
| RFC-014 | Engine Conformance | Draft |
| RFC-015 | Engine Policy | Proposed |
Writing an RFC
See RFC-000 for the process. RFCs are warranted for:
- Law representation format changes
- Execution engine architecture changes
- Cross-cutting design patterns
- Integration patterns between components
The template is at docs/rfcs/template.md in the repository.