RFC 0000: Short descriptive title

Summary

State the decision and user outcome in a few sentences.

Describe the problem, current behavior, evidence, scope, and non-goals.

Use stable SOL-* IDs and BCP 14 language. Add new records to ../requirements.json before implementation.

Describe interfaces, data flow, states, trust boundaries, compatibility, and affected components.

Describe the primary workflow, disclosure levels, keyboard/focus/touch behavior, responsive states, feedback, errors, and manual validation.

Identify attacker-controlled inputs, protected assets, remote data, consent, dependency risk, and fail-closed behavior.

Record viable alternatives and why they were not selected.

List technical, scientific, product, operational, accessibility, and delivery risks with mitigations.

Write observable outcomes and identify the test layer for each.

List unit, contract, integration, browser, visual, deterministic, accuracy, coverage, and manual checks that apply.

Describe compatibility, migration, observability, release sequence, and the safe rollback.

List README, specifications, requirements, instructions, operations, status, and user help that must change.