Self-dev customizations: capture intent, provenance, rationale, and validation metadata
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 19.9k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 30
Description
Split from #32.\n\nAdd the rich metadata needed so future agents can preserve user intent across updates.\n\n## Scope\n- capture original request / clarified goal summary\n- capture touched files/modules/symbols and patch/diff provenance\n- capture rationale/tradeoffs and validation commands or smoke checks\n- store migration hints and incompatibility handling preferences\n\n## Success criteria\n- customization records can store intent, provenance, rationale, validation, and update hints\n- metadata schema is documented and versioned if needed\n- tests cover partial and full metadata cases\n- records remain backward-compatible with the minimal schema from #35\n\nBlocked by: #35\nParent: #32
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin by resolving the dependency on #35, then identify where customization records and their schema are defined; this issue names no files or test entry points. Done means records support partial and full intent, provenance, rationale, validation, and update metadata, with documented versioning, backward compatibility, and tests for both metadata cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100