Use Cases
These sixteen scenarios show how AuraBoot's six concepts — Model, Page, Command, Permission, Process, Plugin — compose against real industry problems. Each page documents the data model, the key commands, a representative permission policy, the BPM flow, and the AI-agent integration points. They are not feature demos — they are runtime templates you can lift, adapt, and extend through plugins.
If you are evaluating AuraBoot, start with the use case closest to your domain. If you are building, treat each page as a contract sketch — the underlying models and commands live in plugins under auraboot/docs/use-cases/ and the broader open-source distribution.
Foundational scenarios
| Scenario | Why it is here | Core models touched |
|---|---|---|
| PCBA Manufacturing | Cross-plugin solution touching 10 plugins from RFQ to shipment; lot traceability + IPC compliance | RFQ / quotation / BOM / work order / lot / inspection / NCR |
| Manufacturing | Discrete and process manufacturing baseline: routing, MRP, work order, inspection | Routing / work order / operation / material movement |
| CRM | Lead → opportunity → quote → order with org-scope visibility and field-level pricing controls | Lead / contact / opportunity / quotation / account |
| Procurement | RFQ → PO → ASN → GRN with supplier scorecard and approval matrix | Supplier / RFQ / PO / ASN / receipt / invoice |
| Quality Management | IQC / PQC / FQC with SPC charts and NCR escalation | Inspection plan / inspection record / SPC sample / NCR |
| Compliance & Risk | Audit-trail-first risk register, control library, and SoD enforcement | Risk / control / audit case / SoD policy |
| Asset Management | Asset master + depreciation + maintenance plan with cross-org delegation | Asset / location / maintenance order / depreciation schedule |
Extended scenarios
| Scenario | Why it is here | Core models touched |
|---|---|---|
| AI Agent Platform | Multi-agent workspaces, skill registry, mission orchestration anchored to Command Pipeline | Workspace / agent / skill / mission / task |
| AuraBot CI Workbench | Competitive intelligence pipeline: signal capture → tagging → briefing publication, all auditable | Target / signal / briefing / source |
| Finance | GL / AR / AP / invoice / payment with SoD; not a country-specific accounting compliance suite | Journal / invoice / payment / period |
| HR Leave Management | Multi-level approval, balance tracking, manager-scoped visibility | Employee / leave request / leave balance |
| Logistics | Shipment dispatch, carrier integration, tracking events with SLA escalation | Shipment / carrier / tracking event |
| Project Management | Project / task / milestone / timesheet with contributor-scoped visibility and budget masking | Project / task / milestone / timesheet |
| Sales | Picks up from CRM at sales-order; shipment, RMA, price list, credit memo | Sales order / quotation / shipment / RMA / price list |
| Warehouse | Inbound / putaway / pick / pack / outbound + stock count, SoD for adjustments | Location / stock / inbound / outbound / pick / count |
| BOM Standardization | Clean customer BOMs and match to standard material codes — a Workbench page-type example | Conversion task / standard line / material master / candidate |
How to read these pages
Each use case follows the same structure:
- Why this is a runtime problem — what makes it more than a CRUD app
- Data model summary — the core models without exhaustive field tables
- Key commands — three to five representative commands with risk / idempotency / agent-hint properties
- Permission example — one real role crossing three or more permission layers
- Process orchestration — the BPMN flow with each task bound back to a command
- Agent integration — what is intentionally exposed to AI agents, and what is not
- How to get it — Community / Standard / Professional / Enterprise paths, no feature comparison
- Next steps — links into the architecture and core-concepts reference
The pages do not compare AuraBoot to specific vendor products. Where the language "data-app builders" or "packaged business suites" appears, treat them as category descriptions, not pointers to any one brand.
Next
- System overview — how the runtime is structured
- Command pipeline — the execution contract every use case relies on
- Pricing — which edition gives you what