ProficientNowTechRFCs
RFC Standards/RFC Kinds/Specification/RFC RFCSTD 0003

RFC-RFCSTD-0003: RFC Kind — Specification

RFC-RFCSTD-0003DraftstandardsstandardsStandards Trackv1.1.0
Created: 2026-02-10
Updated: 2026-02-10
RFC-RFCSTD-0003                                                   Section 0
Category: Standards Track                                             Index

RFC-RFCSTD-0003: RFC Kind — Specification


Abstract

This RFC defines the Specification kind—implementation-focused RFCs that define how to implement an architecture without containing code. Specification RFCs bridge the gap between Architecture RFCs (conceptual design) and actual implementation.

Specification RFCs define the "how" of implementation through:

  • Prerequisites (required and optional dependencies)
  • Phased implementation plans (task → test → iterate)
  • Resource definitions (tabular, not code)
  • Validation criteria (deterministic verification)
  • Test requirements (categories and acceptance criteria)
  • Risk documentation (features, caveats, loopholes, mitigations)

Specification RFCs do NOT contain working code. They provide sufficient detail for an implementer to build the system correctly without embedding implementation artifacts.


Scope Boundaries

AspectIn ScopeOut of Scope
ContentImplementation requirements, validation criteriaWorking code, configuration files
FocusHow to implementWhat to implement (Architecture)
AudienceImplementers, operatorsArchitects (see Architecture RFCs)
FormatTabular resource definitionsYAML, JSON, shell scripts

Table of Contents

Core Sections

SectionFileDescription
0. Index00-index.mdThis file — metadata, abstract, navigation
1. Scope01-scope.mdApplicability and what Specification RFCs cover
2. Normative Requirements02-requirements.mdRules for writing Specification RFCs
3. Structure Definition03-structure.mdRequired and optional sections
4. Formatting Standards04-formatting.mdStyle and presentation
5. Validation Criteria05-validation.mdHow to verify compliance
6. Examples06-examples.mdSample prerequisites, phases, resources, validation

Appendices

AppendixFileDescription
A. Glossaryappendix-a-glossary.mdTerm definitions
B. Referencesappendix-b-references.mdCitations and version history

Reading Paths

For Specification RFC Authors

  1. Start with Scope to understand what Specification RFCs cover
  2. Read Normative Requirements for mandatory rules
  3. Follow Structure Definition for section organization
  4. Review Examples for practical guidance on tabular formats

For RFC Reviewers

  1. Use Validation Criteria as review checklist
  2. Reference Normative Requirements for compliance
  3. Check Structure Definition for completeness

For Implementers Reading Specification RFCs

  1. Start with Prerequisites to understand what you need
  2. Follow Phases sequentially (task → test → iterate)
  3. Use Resource tables as implementation guides
  4. Validate using Validation Criteria

End of Index — RFC-RFCSTD-0003

On this page