Skip to content

Documentation: System Architecture & Monorepo Flow #363

@OSEH-svg

Description

@OSEH-svg

Difficulty: Difficult

NOTE: This is a high-level documentation task requiring full-stack understanding.

Task Description

Create a root-level ARCHITECTURE.md that explains the high-level system flow and the monorepo structure, helping developers understand how the three main pillars (Web, Server, Contract) interact.

Implementation Details

File Path: ARCHITECTURE.md (root)
Content:

  • Monorepo Structure: Explain the purpose of /apps/web, /server, and /contract.
  • System Flow Diagram: Use a Mermaid diagram to visualize:
    • Frontend (Next.js) -> Backend (Axum).
    • Backend (Axum) -> Database (PostgreSQL).
    • Frontend (Next.js) -> Blockchain (Soroban Contracts).
    • Backend (Axum) -> Blockchain (Stellar SDK).
  • Ticketing Flow: Document the "Ticket" metaphor implementation across the stack (how a ticket goes from a Soroban registry to a PostgreSQL transaction).
  • Communication Protocol: REST APIs vs. Smart Contract calls.

Acceptance Criteria

  • ARCHITECTURE.md contains at least one Mermaid sequence or flow diagram.
  • Clear distinction between "On-chain" and "Off-chain" data storage is made.
  • Folder responsibilities are accurately described.

When opening your PR, ensure you link this issue. Include: Closes #issue_number.

💡 Questions?
Reach out on Telegram: @divine_oseh

Metadata

Metadata

Assignees

Labels

ETA 24 hurgently neededStellar WaveIssues in the Stellar wave programdocumentationImprovements or additions to documentation

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions