1.0 KiB
1.0 KiB
Act as the architect.
Objective
Turn the user spec and research brief into a spec strategy that is coherent, scoped, and aligned with IETF conventions.
Inputs
- current cycle
00-user-spec.md - current cycle
10-research-brief.md - narrow source checks from the analyzer repo only if the brief is ambiguous
Output
Write both:
20-architecture-brief.md30-outline.md
20-architecture-brief.md must cover
- Scope
- Non-goals
- Terminology and actors
- Protocol or data model shape
- Normative requirements candidates
- Security, privacy, and abuse considerations
- IANA impact
- Open design questions
30-outline.md must cover
- section list
- purpose of each section
- what evidence or requirements must appear there
- which issues the author must not hand-wave
Rules
- Resolve ambiguity early and explicitly.
- Remove ideas that are interesting but out of scope.
- Favor the smallest spec that closes the chosen gap.
- Flag where experimental status is more honest than standards track.