Technical Specification Template

# [System or feature] technical specification

Status: Draft | Accepted | Implemented | Superseded
Owners: [People or team]
Last reviewed: [Date]

## Summary
[The useful answer in two or three sentences.]

## Problem and users
[Who needs what, and what evidence establishes the problem.]

## Requirements
- R1. [Observable required behavior]
- R2. [Observable required behavior]

## Non-goals
- [Behavior or system deliberately excluded]

## Design
[Components, responsibilities, data flow, and important boundaries.]

## Interfaces and data
[Routes, events, schemas, files, commands, or protocols.]

## Failure and recovery
[Expected failures, error behavior, retries, rollback, and operator recovery.]

## Security and privacy
[Trust boundaries, credentials, sensitive data, abuse limits.]

## Compatibility and rollout
[Migration, sequencing, feature flags, fallback, removal plan.]

## Verification
[Tests and real-world proof tied to each requirement.]

## Open questions
- [Decision that still blocks acceptance]

## Related decisions
- [ADR, RFC, plan, issue, or source link]

## Requirements
- R1. An expired share link returns the same public response as an unknown link.

## Verification
- V1. Create one valid and one expired link against the real route harness.
- V2. Assert that both hidden cases return the documented status and body.
- V3. Assert that the expired request does not read document content.