Balyze — Technical documentation
This documentation describes the technical foundations, domain rules, and architectural decisions behind Balyze.
Balyze is currently in a private ALPHA phase, focused on validating the core domain and workflows before opening the product to external users.
Project status
- Phase: ALPHA (private, personal usage)
- Target: v0 / BETA (limited external testing)
- Scope: backend-first, domain-driven
- Audience: developers and maintainers of the project
This documentation reflects the current state of the project and may evolve as the product matures.
What this documentation covers
This documentation focuses on:
- architectural choices and technical stack
- naming conventions and structural guidelines
- domain concepts and business rules
- lifecycle and editability rules
- security principles (authentication, roles, permissions)
The goal is to make decisions explicit, not to document implementation details.
What this documentation does NOT cover
At this stage, the documentation does not include:
- end-user guides
- UI documentation or screenshots
- public API documentation
- deployment or infrastructure setup guides
These topics will be introduced progressively as the product reaches BETA and v1.
How to read this documentation
- Start with Architecture to understand how the project is structured
- Continue with Domain to understand the business rules
- Refer to Security for access control and permissions
- Use tags to identify content relevant to a specific phase or concern
Guiding principles
- domain rules are defined before implementation
- documentation explains why, not how
- simplicity is preferred over premature optimization
- technical debt is avoided through explicit decisions
Contribution and evolution
This documentation is a living artifact. It evolves alongside the codebase and reflects intentional design choices made during development.
Unstable or speculative features are intentionally excluded.