Files
stack/docs/3-architecture
Jason Woltje 8c8d065cc2
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
feat(arch): Add Guard Rails capability-based permission system design
Guard Rails complement Quality Rails by controlling what agents can do:
- Capability-based permissions (resource:action pattern)
- Read/organize/draft allowed by default
- Execute/admin require explicit grants
- Human-in-the-loop approval for sensitive actions

Examples: email (read/draft , send ), git (commit , force push )

Also:
- Add .admin-credentials and .env.bak.* to .gitignore

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-02-01 00:25:53 -06:00
..

Architecture

Technical architecture and design principles for Mosaic Stack.

Chapters

  1. Overview — System design and component architecture
  2. Authentication — BetterAuth integration and OIDC flow
  3. Design Principles — PDA-friendly patterns and UX guidelines

Architecture Principles

  • Type Safety First: Shared types prevent frontend/backend drift
  • Multi-Tenant Ready: Row-level security with workspace isolation
  • PDA-Friendly: Calm, stress-free language and visual design
  • Modular: Plugin architecture for extensibility

Technology Decisions

Key architectural choices and their rationale:

  • BetterAuth over Passport.js for modern authentication
  • Prisma ORM for type-safe database access
  • Monorepo with pnpm workspaces for code sharing
  • PostgreSQL + pgvector for AI-ready data storage

Next Steps

  • Review API for implementation details
  • Check Development for workflow standards