Free-first, modular infrastructure and AI-assisted engineering.
FlossWare builds reusable engineering foundations and reference implementations using open standards, explicit configuration, and loosely coupled architectures.
| Repository | Purpose |
|---|---|
| engineering-standards | Architecture decisions, engineering principles, and development standards |
| commons-java | Shared Java foundation libraries |
| tftp-os | Reference implementation for infrastructure provisioning and automation |
FlossWare systems follow these core ideas:
- Configuration is the source of truth
- Minimal behavior by default; capabilities are explicitly enabled
- Components are modular and composable
- Open standards over vendor lock-in
- Loose coupling through stable contracts
Clients / Agents
|
REST APIs / MCP Tool Interfaces
|
Service Boundaries
|
+--------------+--------------+
| |
Stored Procedures Message Bus
| |
v v
Databases Event Consumers
- REST provides synchronous service contracts.
- MCP provides AI agent and tool integration contracts.
- Message buses provide asynchronous workflows and event-driven integration.
- Stored procedures provide database abstraction where they add value.
- ADRs preserve architectural decisions.
The canonical architecture documentation lives in:
See the repository ADRs for detailed architectural decisions.
Contributions should align with the FlossWare engineering standards. Projects should favor clarity, composability, and maintainable open designs over unnecessary complexity.
