Skip to content

Recent Decisions

Last refreshed: 2026-05-18

2026-05-17: Rebuild Core And State Docs

Decision: Move the working documentation baseline to docs/core and docs/state, following docs/CoreAndStateDocs.md.

Reason: Existing docs were moved under docs/_stale; future implementation work needs fast, current orientation docs tied to code paths.

2026-05-17: Treat Stale Docs As Historical

Decision: Do not treat docs/_stale as source of truth.

Reason: Stale docs include useful historical product and architecture material, but current behavior must be verified against code, active .env, tests, and scripts.

2026-05-17: Keep Upgrade State Explicit

Decision: Describe the Anuva v1 upgrade as partially implemented unless code proves a path is productized.

Reason: Current code includes v1 contracts, workflow scaffolding, stage gates, source adapters, and collections, while legacy presentation actions still carry substantial production behavior.

2026-05-17: Prefer Maps Over Long Narratives In State Docs

Decision: docs/state should remain path-oriented and operational.

Reason: State docs are meant to get future implementation work started quickly. Durable product/system explanations belong in docs/core.

flowchart TD
  decision["Decision record"] --> date["📅 Date"]
  decision --> choice["✅ Decision"]
  decision --> reason["💡 Reason"]
  decision --> links["🔗 Links"]

Template For Future Entries

## YYYY-MM-DD: Decision Title

Decision: What changed or what was chosen.

Reason: Why the decision was made.

Links: Related change folder, PR, issue, or source file.