Business Decisions Documentation
When making or discussing business decisions, rules, or logic for this application:
- Always document business decisions in the
/internaldocs/business_decisions folder
- Use markdown files with the naming convention:
YYYY-MM-DD-decision-title.md
- Include the following sections in each decision document:
- Date: When the decision was made
- Status: Proposed, Accepted, Deprecated, or Superseded
- Context: What is the issue or situation that prompted this decision?
- Decision: What was decided? Include specifics, rules, and implementation details
- Rationale: Why was this decision made? What alternatives were considered?
- Consequences: What are the positive and negative implications?
When to Create a Business Decision Document
Create a new document when:
- Defining new business rules or logic
- Making architectural decisions that affect business functionality
- Choosing between competing approaches for business features
- Establishing patterns for handling business data
- Defining user-facing policies or behaviors
- Accepting risks or trade-offs that should be documented
- Making decisions that future developers need to understand
Optional Sections
For complex decisions, consider adding:
- Implementation Notes: Code examples, database changes, API patterns
- Migration Considerations: How to transition from current state
- Review Schedule: When to revisit this decision
- Action Items: Outstanding tasks related to the decision
- References: Links to related docs, external resources, or prior decisions
Template
# [Decision Title]
## Date
YYYY-MM-DD
## Status
[Proposed | Accepted | Deprecated | Superseded]
## Context
[Describe the problem, situation, or need that prompted this decision]
## Decision
[Describe what was decided, with enough detail for implementation]
## Rationale
[Explain why this approach was chosen over alternatives]
## Consequences
### Positive
- [Benefit 1]
- [Benefit 2]
### Negative
- [Trade-off 1]
- [Trade-off 2]