[Proposal Title]

The Context

Describe the circumstances that led to this proposal. Give enough background that someone unfamiliar with the area can understand why the work matters. State what you were trying to accomplish, not what solution you reached for first.

The Problem Statement

State the specific problem, limitation, or gap being addressed. Be concrete. A reader should be able to confirm whether a proposed solution actually solves it.

Design

Detail the proposed solution precisely enough that it could be implemented without improvising the design. Include code, diagrams, or examples where they reduce ambiguity. Vague or underspecified proposals cannot be acted on.

CRIS Score

Factor	Score	Evidence
Complexity	0–10	[10 = simple, well-understood; 0 = novel or high-risk — why]
Reach	0–10	[10 = affects everyone; 0 = affects almost no one — why]
Impediment	0–10	[10 = total blocker with no workaround; 0 = trivial to work around — why]
Stakeholder	0–10	[10 = critical dependency for a major project; 0 = no project depends on it — why]
Total		[Average of four factors (0–10); 8–10 = build now, 6–8 = schedule soon, 4–6 = evaluate, 0–4 = defer]

The Downsides

Describe the costs, risks, or trade-offs. Every proposal has them.

The Road Not Taken

Describe the alternatives considered and why this approach was chosen over them.

Status

Status: Draft

Decision Makers

• [Name or role]

Tags

• [relevant-tag-1], [relevant-tag-2], YYYYMMDD-this-filename-without-extension, present-proposal-template

Further Reading

@misc{v_sekai_2026,
  title = {V-Sekai},
  year  = {2026},
  url   = {https://v-sekai.org/}
}