docs: establish integrated project memory

This commit is contained in:
2026-08-12 19:33:12 +08:00
parent 50ac5bddc4
commit 1eb36645e4
31 changed files with 872 additions and 0 deletions

View File

@@ -0,0 +1,15 @@
# Evidence Index
Use this index for searchable, traceable evidence records.
| Date | Topic | Status | Source | Detail |
|---|---|---|---|---|
| 2026-08-11 | Public display API contract used by the native app | Verified | Source code and tests | [Evidence](topics/20260811-native-display-f2456ea9__public-display-api.md) |
| 2026-08-12 | Embedded Mandarin WAV provenance, mapping, format, and acceptance | Verified with known licensing gap | Git history, WAV inspection, ASR, tests | [Evidence](topics/20260811-native-display-f2456ea9__embedded-audio-assets.md) |
| 2026-08-12 | Batch range endpoint clipping and fitted-text fix | Verified in host tests; target-TV acceptance pending | Production snapshot, code, Robolectric, APK checks | [Evidence](topics/20260811-native-display-f2456ea9__range-display-fit.md) |
## When To Add Evidence
Add a topic file when a task depends on logs, commits, test output, external docs, bug reproduction, experiments, or postmortem-level reasoning.
Keep task progress in `30-worklog/`; keep reusable workflow lessons in `60-reflection/`.

View File

@@ -0,0 +1,35 @@
# Evidence Topic: {short title}
## Metadata
- Date:
- Status: Active | Resolved | Superseded | Stale
- Scope:
- Confidence: Fact | Inference | Hypothesis
- Source:
- Last verified:
- Stale trigger:
## Question
What needed evidence?
## Evidence
- Commit:
- Files:
- Commands:
- Logs:
- External source:
## Finding
What does the evidence support?
## Impact
What future planning or implementation should this affect?
## Open Items
-