This directory contains Architecture Decision Records documenting significant technical decisions made in the Tokenized Fractional RWA Marketplace project.
An Architecture Decision Record (ADR) is a document that captures an important architectural decision made along with its context and consequences.
Each ADR follows this structure:
- Context: The issue we're addressing and forces influencing the decision
- Decision: What we decided and why
- Consequences: Benefits, drawbacks, and tradeoffs
- Alternatives Considered: Other options evaluated
| Number | Title | Status |
|---|---|---|
| 0001 | Use Soroban Smart Contracts for RWA Marketplace | Accepted |
| 0002 | File-Based Asset Storage (data.json) for Metadata | Accepted |
| 0003 | Use React + Vite for Frontend Development | Accepted |
- Create a new file:
000X-short-title-in-kebab-case.md - Use the template as a starting point
- Ensure the ADR has clear context, decision, and consequences
- Add to this README's table
- Submit as a pull request for team review
Write an ADR when you need to document:
- Technology choices (frameworks, databases, platforms)
- Architectural patterns or approaches
- Major refactoring decisions
- Trade-offs between competing solutions
- Decisions that have long-term impact on the codebase
- Proposed: Under discussion, not yet accepted
- Accepted: Decision made and approved by the team
- Deprecated: Superseded by a newer ADR
- Superseded by ADR-XXXX: Replaced by a newer decision