Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@ Thanks for your interest. Tracecore is in early development and we welcome focus

- Read [`PRINCIPLES.md`](PRINCIPLES.md) for *why* we make the choices we make. Read [`STYLE.md`](STYLE.md) for *what* the rules are.
- Skim [`AGENTS.md`](AGENTS.md) for the load-bearing lessons every change should respect, and the topic index pointing into `docs/notes/` for deeper per-area guidance.
- **Keep the tracking docs current.** Any PR that starts, advances, ships, or re-scopes work tracked in [`MILESTONES.md`](MILESTONES.md) or [`docs/FOLLOWUPS.md`](docs/FOLLOWUPS.md) updates the corresponding entry (and, for milestones, the lane table) in the same PR — see [`MILESTONES.md` § "Keeping this document current"](MILESTONES.md#keeping-this-document-current) for the exact transitions covering both files. Status drift is a review blocker.
- File an **RFC** in `docs/rfcs/` for load-bearing decisions you want documented for future contributors — architectural calls with non-obvious alternatives, policy changes, deprecations. Not gated. Small architectural choices can land via a clear commit message + a code comment. Judgment-called; over-RFC beats under-RFC at this stage, but velocity beats both.
- Check open issues to avoid duplicate work.

Expand Down
Loading