1. Use Case Lifecycle
| Stage | Code | Description |
|---|---|---|
| Active | UC-A | Deployed, revenue-generating or in UAT |
| Development | UC-D | Implementation in progress, assigned |
| Planned | UC-P | Scoped, not yet assigned |
| Research | UC-R | Under investigation, feasibility TBD |
2. Active Use Cases
2.1 Pyrometrix TCO (UC-A1)
| Aspect | Detail |
|---|---|
| ID | UC-A1-BASELINE-v3.0 |
| Domain | Infrastructure / Data Centre |
| Market | Enterprise data centre operators, cooling technology vendors |
| Nodes Used | ValidateNode, StoreNode, ReportGenerator |
| Rule Types | capex (65), opex (148), power (8), infrastructure (3), energy (4), tco (10) |
| Total Rules | 238 |
| Runtime | Local Python, Docker |
| Status | Production -- deployed, 4 technology comparisons functional |
| Validation | VB-edr-pipeline-0.2.0 (VL-4), CT-RULE passing |
2.2 Freelance Pipeline (UC-A2)
| Aspect | Detail |
|---|---|
| ID | UC-A2-FREELANCE-v1.0 |
| Domain | Freelance / Job Automation |
| Market | Internal (CreativeAnswer operations) |
| Nodes Used | WebhookTrigger, AiTransform, LeadScoreNode, ConditionBranch |
| Rule Types | scoring (10), policy (11), assignment (4) |
| Total Rules | 25 |
| Runtime | Local Python |
| Status | Production -- active job scoring |
| Validation | VB-freelance-pipeline-0.1.0 (VL-2) |
2.3 PFP Product Fit (UC-A3)
| Aspect | Detail |
|---|---|
| ID | UC-A3-PFP-v2.0 |
| Domain | Product Selection / Compliance |
| Market | Technology vendors, procurement |
| Nodes Used | ValidateNode, ConditionBranch, StoreNode |
| Rule Types | pfp_clearance (537), pfp_selection (9), pfp_validation (17) |
| Total Rules | 563 |
| Runtime | Local Python, Docker |
| Status | Production -- clearance evaluation functional |
| Validation | VB-pfp-pipeline-0.2.0 (VL-4) |
3. Development Use Cases
3.1 Nesto Worker Compliance (UC-D1)
| Aspect | Detail |
|---|---|
| ID | UC-D1-NESTO-v1.0 |
| Domain | HR / Worker Compliance |
| Market | UAE/KSA/BH labour market, construction, hospitality |
| Nodes Used | FormNode, ValidateNode, HumanGate, StoreNode, EmailForward |
| Rule Types | nesto_compliance (17) |
| Total Rules | 17 |
| Target Runtime | Local Python -> Power Platform (Phase 4) |
| Status | Phase 1 -- rules implemented, flow assembly in progress |
| Roadmap | WP-1.1 through WP-1.5 |
| Assigned | TBD (cooperator) |
| Dependencies | HumanGate webhook completion (WP-1.2) |
3.2 ARC Lead Pipeline (UC-D2)
| Aspect | Detail |
|---|---|
| ID | UC-D2-ARC-v1.0 |
| Domain | CRM / Lead Management |
| Market | Sales teams, marketing automation |
| Nodes Used | WebhookTrigger, AiTransform, LeadScoreNode, MatchNode, ConditionBranch, EmailForward |
| Rule Types | scoring (custom) |
| Target Runtime | Local Python, AWS Lambda |
| Status | Phase 2 -- nodes implemented, integration pending |
| Roadmap | WP-2.3, WP-2.4 |
| Assigned | TBD (cooperator) |
| Dependencies | Phase 1 HumanGate webhook |
4. Planned Use Cases
4.1 EDR Entity Data Registry (UC-P1)
| Aspect | Detail |
|---|---|
| ID | UC-P1-EDR-v1.0 |
| Domain | Engineering / Industrial Data Quality |
| Market | Oil and gas, petrochemical, power generation, EPC contractors |
| Problem | Engineering entities (valves, pipelines, instruments) have inconsistent data across systems. Tag formats differ, material codes are non-standard, safety classifications are missing or wrong. Manual QC costs millions per project. |
| Nodes Used | IngestNode, ValidateNode, ConditionBranch, StoreNode, ReportGenerator, DashboardNode |
| Rule Types | edr_validation (19), validation (12) -- to be expanded to 50+ |
| Target Rules | 80-120 (tag format, material standard, pressure rating, safety class, completeness) |
| Target Runtime | Docker on-prem (data residency), AWS Lambda (cloud option) |
| BDT Types Required | Tag format (IMMUTABLE_IDENTITY), pressure rating (REFERENCE_CONSTANT), material code (MUTABLE_STATE), safety class (IMMUTABLE_IDENTITY), inspection date (OPERATIONAL_EVENT) |
| Entity Classes | Valve, Pipeline, Equipment, Electrical, Instrument, Safety Device |
| Status | Planned -- 31 rules exist, entity classes defined, pipeline proven |
| Roadmap | WP-2.1, WP-2.2, WP-2.5, WP-2.6 (Phase 2) |
| Assigned | TBD (cooperator -- domain expert + Python backend) |
| Dependencies | AtlasOCR integration (WP-2.5) for P&ID drawing extraction |
| Revenue Model | Per-project licensing, SaaS per-entity pricing |
| Competitive Advantage | Rule-driven (not ML black-box), auditable, deterministic |
4.2 AES Assessment Engine Service (UC-P2)
| Aspect | Detail |
|---|---|
| ID | UC-P2-AES-v1.0 |
| Domain | Education / Certification / Assessment |
| Market | Training providers, certification bodies, corporate L&D, schools |
| Problem | Assessment creation is manual. Grading is inconsistent. Adaptive difficulty requires custom development. No platform combines rule-based scoring with AI-powered evaluation. |
| Nodes Used | FormNode, ValidateNode, AiTransform, ConditionBranch, StoreNode, DashboardNode, LeadScoreNode |
| Rule Types | New: assessment_scoring, assessment_routing, certification_criteria |
| Target Rules | 30-50 per assessment template |
| Target Runtime | AWS Lambda (SaaS), Docker (on-prem for universities) |
| BDT Types Required | Assessment score (DERIVED_METRIC, unit: points), Question response (OPERATIONAL_EVENT), Certification status (MUTABLE_STATE), Pass threshold (REFERENCE_CONSTANT) |
| Flow Pattern | Form(questions) -> Validate(format) -> AI(evaluate) -> Branch(pass/fail) -> Score(aggregate) -> Store(record) -> Dashboard(results) |
| Status | Planned -- all required node types exist, flow pattern proven |
| Roadmap | WP-3.1 (Phase 3) |
| Assigned | TBD (cooperator -- AI/ML + React) |
| Dependencies | GPU batch processing (WP-3.2) for large cohort evaluation |
| Revenue Model | SaaS per-assessment, enterprise licensing |
| Competitive Advantage | AI + Rules hybrid (AI grades, rules enforce consistency), full audit trail, adaptive branching |
4.3 ENDO Document Processing (UC-P3)
| Aspect | Detail |
|---|---|
| ID | UC-P3-ENDO-v1.0 |
| Domain | Document Intelligence / Back-office Automation |
| Market | Insurance, legal, financial services, government |
| Nodes Used | GmailIngest, AtlasOcr, AiTransform, ValidateNode, StoreNode, PdfGenerator |
| Rule Types | document_validation, extraction_rules |
| Target Runtime | AWS Lambda, Docker |
| Status | Planned -- node executors exist, OCR integration needed |
| Roadmap | Phase 2-3 |
| Dependencies | AtlasOCR integration (WP-2.5) |
5. Chameleon Extensions (Not Use Cases)
The following are NOT standalone Nexus use cases. They are extensions to the Chameleon system and their requirements belong in the Chameleon repository.
5.1 ChameleonBI (Osiris Heritage)
| Aspect | Detail |
|---|---|
| Type | Chameleon extension -- NOT a Nexus use case |
| Target Repo | Chameleon (requirements to be pushed as feature spec) |
| Origin | Osiris prototype (archived) -- PowerBI analysis/reconstruction tool |
| Capability | Rule-driven dashboards that enforce business logic and trigger actions |
| Osiris Findings | Form generation from data structures, multi-format output (HTML, React, PowerBI), template system. PowerBI PBIX extraction and reconstruction. |
| Next Action | Extract requirements from Osiris archive, write ChameleonBI feature spec, push to Chameleon repo |
| Nexus Integration | Consumes DashboardNode, ListViewNode, NavMenuNode outputs -- does NOT run as a Nexus pipeline |
6. Use Case Cross-Reference Matrix
This matrix shows which Nexus platform capabilities each use case requires. Values indicate requirement status:
| Symbol | Meaning |
|---|---|
| REQ | Required -- this use case needs this capability to function |
| OPT | Optional -- enhances the use case but not blocking |
| -- | Not applicable -- this capability is not used |
Column definitions:
| Column | Platform Capability | Implementation |
|---|---|---|
| Rule Engine | Wormwood core rule evaluation | Python (production) |
| BDT | Business Data Type validation and lifecycle enforcement | Python (wormwood/core/business_data_types.py) |
| Orchestration | Multi-node pipeline execution with state management | Python (wormwood/core/pipeline_runner.py) |
| AI | Claude/LLM integration for text analysis, scoring, generation | Python (AiTransformNode) |
| OCR | AtlasOCR document/drawing extraction | Python (AtlasOcrNode -- scaffold) |
| Forms | ChameleonV2 user-facing data entry | React (Chameleon repo) |
| Approval | Human Gate nodes requiring RBAC-gated manual decisions | Python (HumanGateNode) |
| Dashboard | DashboardNode/ListViewNode visual output | React (Chameleon repo) |
Capability Requirement Matrix
| Use Case | Rule Engine | BDT | Orchestration | AI | OCR | Forms | Approval | Dashboard |
|---|---|---|---|---|---|---|---|---|
| Pyrometrix (UC-A1) | REQ | REQ | -- | -- | -- | -- | -- | -- |
| Freelance (UC-A2) | REQ | REQ | REQ | REQ | -- | -- | -- | -- |
| PFP (UC-A3) | REQ | REQ | -- | -- | -- | -- | -- | -- |
| Nesto (UC-D1) | REQ | REQ | REQ | -- | -- | REQ | REQ | -- |
| ARC (UC-D2) | REQ | -- | REQ | REQ | -- | OPT | -- | -- |
| EDR (UC-P1) | REQ | REQ | REQ | -- | REQ | -- | -- | REQ |
| AES (UC-P2) | REQ | REQ | REQ | REQ | -- | REQ | -- | REQ |
| ENDO (UC-P3) | REQ | REQ | REQ | REQ | REQ | -- | REQ | -- |
7. Version History
| Version | Date | Changes |
|---|---|---|
| UC-1.0 | 2026-05-02 | Initial register: 3 active, 2 development, 3 planned, 1 research use cases. |