AR-XXXX: Title

Field	Value
Status	Proposed
Opened	YYYY-MM-DD
Last reviewed	YYYY-MM-DD
Scope	Core storage / relational layer / adapter / consumer / cross-cutting
Trigger	Concrete implementation, corpus, compatibility, or consumer pressure
Related ADRs	None
Related evidence	Tests, CRs, diagnostics, audits, or design documents

Architectural Question

State one decision-shaped question.

Context

Describe the current architecture and why review is needed now.

Evidence

Separate observed behavior from architectural guarantees.

• Tests or fuzzing:
• Independent consumers:
• Diagnostics or audits:
• Repeated implementation friction:
• Missing evidence:

Ownership And Dependency Analysis

Identify who owns the meaning, who owns the mechanism, the current dependency direction, and the state or semantics Tosumu must not absorb.

Alternatives Considered

Alternative A: Name

• Benefits:
• Costs:
• Failure mode:

Alternative B: Name

• Benefits:
• Costs:
• Failure mode:

Include continued incubation and doing nothing when they are real choices.

Findings

Record what the evidence supports, what it does not support, and uncertainty.

Disposition

Choose Accepted, Incubating, Deferred, Rejected, No Change, or Superseded and state the result directly.

Required Follow-Up

• [ ] ADR or documentation work
• [ ] Focused implementation slice
• [ ] Tests, fuzzing, or independent-consumer evidence
• [ ] Compatibility or migration work

Reopening Triggers

Name observable evidence that justifies reopening.

Review History

Cycle 1 -- YYYY-MM-DD

• Status entering review: Proposed
• New evidence:
• Findings:
• Disposition:
• Resulting ADR or documentation change: