sage-architecture

What problem does it solve?

This Sage architecture guide provides a cohesive blueprint to structure large Sage projects, reducing fragmentation and enabling scalable collaboration across teams.

Core Features & Use Cases

• Module boundary enforcement: Every module should be kept under 200 lines unless split into submodules for clarity.
• Layered responsibilities: Define clear responsibilities for cli, sdk, core, and tools to reduce cross-cutting concerns.
• Naming and governance: Enforce consistent naming, RFC-compliant module schemas, and documentation of design decisions to aid onboarding.
• Use Case: When planning a major refactor, apply these guidelines to decompose the project into smaller, coherent modules with explicit interfaces.

Quick Start

Start by auditing modules for boundaries, then codify layer responsibilities and naming conventions in the repo docs. Use this guide during planning and reviews to keep Sage architecture coherent.