7590a7a2ff
* feat(context): Add project intelligence system - Add project-intelligence.md standard (what & why) - Add project-intelligence-management.md guide (how to manage) - Add project-intelligence/ folder with 6 context files: - navigation.md (quick overview & routes) - business-domain.md (business context, users, value) - technical-domain.md (stack, architecture, decisions) - business-tech-bridge.md (business → technical mapping) - decisions-log.md (decision history with context) - living-notes.md (active issues, debt, questions) - Update standards navigation with new entries - Register all new contexts in registry.json This enables projects to document and maintain business + technical context for quick onboarding and lasting project understanding. * fix(registry): Add project-intelligence to profiles - Add context:project-intelligence/* to developer, business, full, and advanced profiles - Ensures project intelligence contexts are included when these profiles are selected This complements commit c731328 which added the context entries. * docs(core): refine project intelligence system and deprecate legacy context
3.2 KiB
3.2 KiB
Decisions Log
Record major architectural and business decisions with full context. This prevents "why was this done?" debates.
Quick Reference
- Purpose: Document decisions so future team members understand context
- Format: Each decision as a separate entry
- Status: Decided | Pending | Under Review | Deprecated
Decision Template
## [Decision Title]
**Date**: YYYY-MM-DD
**Status**: [Decided/Pending/Under Review/Deprecated]
**Owner**: [Who owns this decision]
### Context
[What situation prompted this decision? What was the problem or opportunity?]
### Decision
[What was decided? Be specific about the choice made.]
### Rationale
[Why this decision? What were the alternatives and why were they rejected?]
### Alternatives Considered
| Alternative | Pros | Cons | Why Rejected? |
|-------------|------|------|---------------|
| [Alt 1] | [Pros] | [Cons] | [Why not chosen] |
| [Alt 2] | [Pros] | [Cons] | [Why not chosen] |
### Impact
**Positive**: [What this enables or improves]
**Negative**: [What trade-offs or limitations this creates]
**Risk**: [What could go wrong]
### Related
- [Links to related decisions, PRs, issues, or documentation]
Decision: [Title]
Date: YYYY-MM-DD Status: [Status] Owner: [Owner]
Context
[What was happening? Why did we need to decide?]
Decision
[What we decided]
Rationale
[Why this was the right choice]
Alternatives Considered
| Alternative | Pros | Cons | Why Rejected? |
|---|---|---|---|
| [Option A] | [Good things] | [Bad things] | [Reason] |
| [Option B] | [Good things] | [Bad things] | [Reason] |
Impact
- Positive: [What we gain]
- Negative: [What we trade off]
- Risk: [What to watch for]
Related
- [Link to PR #000]
- [Link to issue #000]
- [Link to documentation]
Decision: [Title]
Date: YYYY-MM-DD Status: [Status] Owner: [Owner]
Context
[What was happening?]
Decision
[What we decided]
Rationale
[Why this was right]
Alternatives Considered
| Alternative | Pros | Cons | Why Rejected? |
|---|---|---|---|
| [Option A] | [Good things] | [Bad things] | [Reason] |
Impact
- Positive: [What we gain]
- Negative: [What we trade off]
Related
- [Link]
Deprecated Decisions
Decisions that were later overturned (for historical context):
| Decision | Date | Replaced By | Why |
|---|---|---|---|
| [Old decision] | [Date] | [New decision] | [Reason] |
Onboarding Checklist
- Understand the philosophy behind major architectural choices
- Know why certain technologies were chosen over alternatives
- Understand trade-offs that were made
- Know where to find decision context when questions arise
- Understand what decisions are pending and why
Related Files
technical-domain.md- Technical implementation affected by these decisionsbusiness-tech-bridge.md- How decisions connect business and technicalliving-notes.md- Current open questions that may become decisions