THE PROBLEM
Most business software remembers. Someone still has to manage.
Software often stores
- customers
- orders
- inventory
- payments
- staff
- messages
- reports
Someone still has to decide
- what matters
- who should act
- what depends on what
- what should be escalated
- what happened afterward
UniQ Flow explores a different model: software organised around the management structure of the business itself.
BUSINESS OPERATIONS ORGANISM
Each tenant is treated as a Business Operations Organism.
Each business has its own operating world. Client businesses do not share one global AI brain.
- operating state
- hierarchy
- departments
- permissions
- customers
- jobs / orders
- inventory
- finance context
- workflows
- evidence
- business-specific extensions
HUMAN AUTHORITY
Owners keep the decisions that change the business.
Owners / managers retain
- strategy
- policy
- financial authority
- meaningful customer commitments
- high-impact exceptions
- business-level priorities
The brain may
- maintain a whole-business model
- understand owner priorities
- assign work across departments
- resolve cross-department conflicts
- reason over outcomes
- escalate decisions
The brain must not
- micromanage routine specialist work
- directly mutate authoritative stores
- hold unrestricted credentials
- approve its own high-risk actions
HOW WORK MOVES
Direction is part of the architecture.
Example: an order exception rises from service operations, the brain coordinates inventory and finance, and a customer commitment returns to a manager.
DOWN
Work moves down
to the most specialised competent layer.
UP
Evidence and exceptions move up.
Outcomes return to the layer that must know.
LATERAL
Ordinary dependencies move laterally.
Departments can coordinate without becoming a single executive.
HUMAN
Strategy and meaningful conflict move to human authority.
The system escalates what it is not permitted to decide.
Example: an order exception rises from service operations, the brain coordinates inventory and finance, and a customer commitment returns to a manager.
SPECIALIST SUBAGENTS
Temporary workers. Bounded tasks.
- temporary
- bounded
- task-specific
- minimum-context
- minimum-permission
They may be created for
- follow-up preparation
- inventory analysis
- invoice reconciliation
- customer-response drafting
- job / order inspection
- report preparation
They cannot
- spawn unrestricted recursive agent trees
- grant themselves new authority
- change policy
- approve their own high-impact actions
- directly bypass deterministic business services
CURRENT DEVELOPMENT SCOPE
Foundations in development — not a claim of full deployment.
Current development scope includes foundations for:
- multi-tenant organisation structure
- industry templates
- lead management
- customer management
- orders / job cards
- inventory
- payments and invoices
- customer tracking
- team management
- communications
- analytics
- Super Admin / security controls
This is a development scope, not a statement that every capability is fully production deployed.
ILLUSTRATIVE OPERATING DOMAINS
The architecture is intended to adapt across service and inventory businesses.
- automotive workshops
- repair businesses
- jewellery
- electronics service
- tailoring
- general service operations
- inventory-driven businesses
These are illustrative operating domains. They are not presented as clients.
SECURITY / CONTROL
Control is part of the operating model.
- tenant separation
- scoped permissions
- controlled integrations
- validated commands
- secret isolation
- auditability
- human approval boundaries