22 行
825 B
Markdown
22 行
825 B
Markdown
# TRELLIS2 Design
|
|
|
|
## Decision
|
|
|
|
Use the official Trellis task directory as the single execution contract for
|
|
new work. Issue CSV remains available as historical evidence or an optional
|
|
export format when a tabular external audit packet is needed.
|
|
|
|
## Contract Shape
|
|
|
|
- `task.json`: metadata, status, scope, related files and optional commit/PR.
|
|
- `prd.md`: goal, scope, out-of-scope, acceptance and test plan.
|
|
- `design.md` or `implement.md`: required for complex process, API, migration,
|
|
permission, deployment or workflow-governance changes.
|
|
- `implement.jsonl` / `check.jsonl`: stable spec or research context only.
|
|
|
|
## Compatibility
|
|
|
|
Existing Issue CSV files stay in place. Existing Trellis tasks can mention
|
|
their old Issue CSV bindings as historical metadata, but new task validation
|
|
must not require those bindings.
|