---
kind: proposal
id: PROP-YYYY-MM-DD-SLUG
title: "Proposal Title"
liveness: n/a
tags: []
---
# Proposal Title
## Summary
One paragraph for a reader unfamiliar with the area. This template adapts
Lore proposal practice for agent-spec.
## Motivation
The problem, limitation, user need, incident, or external pressure that makes
this proposal necessary now.
## Goals
- Goal 1.
## Non-Goals
- Explicitly out-of-scope item.
## Proposed Design
Describe the design at the level needed to evaluate the goals.
## Compatibility
- CLI and public API:
- File formats:
- Existing specs and KLL artifacts:
## Migration Plan
Use `N/A -- no migration required` only when no existing user, artifact, or
workflow needs a transition.
## Security Considerations
Describe trust-boundary and abuse implications, or explain why there are none.
## Privacy Considerations
Describe paths, metadata, user data, logs, or telemetry implications, or explain
why there are none.
## Risks and Assumptions
### Assumptions
- Assumption. Invalidated if: ...
### Risks
- Risk. Mitigation: ...
## Alternatives Considered
- Alternative and concrete reason it was rejected.
## Prior Art
- Relevant project, paper, tool, or standard.
## Unresolved Questions
- Question to resolve before acceptance.
## Produces
- ADR- or REQ- id created if this proposal is accepted.