Explainable scoring
The score breakdown panel is one of LiftIQ's strongest current assets because it makes the recommendation reviewable under pressure.
Module layer
LiftIQ's current module story is strongest when it stays explicit.
Some modules are visibly demonstrated in the governed demo. Some are only partially represented. Others exist as specifications or names. The table below keeps those states separate so the commercial story stays credible.
| Module | Status | Current truth | Commercial boundary |
|---|---|---|---|
| SmartRank | Demonstrated | Weighted ranking and explainable score breakdown are visible in the governed demo. | Safe to present as rule-based recommendation logic on seeded data. |
| FatigueGuard | Demonstrated | Monitor and block thresholds are implemented in the demo with consistent policy treatment. | Safe to present as visible fatigue logic, not full compliance automation. |
| CredentialGate Internal continuity name: ComplianceAI |
Partially demonstrated | The truthful current behaviour is visible hard-blocking for missing required credentials. | Unsafe to position as broad automated compliance software. |
| SwapEngine | Partially demonstrated | Replacement ranking is shown in preview form using the same underlying seeded logic. | Safe as swap preview logic. Unsafe as live dispatch orchestration. |
| FairLift | Partially demonstrated | Light fairness weighting is represented in the current demo logic. | Safe as a weighting influence, not as formal fairness governance. |
| AuditIQ | Partially demonstrated | The demo shows a preview event log only. No persistence or export exists. | Unsafe to describe as immutable audit reporting. |
| RiskScore | Specified | Conceptual scoring layer only. Not independently implemented. | Do not market as a live module. |
| PredictLift | Named only | Name exists. No demonstrated predictive model exists. | Do not imply forecasting capability. |
| LiftIQ Chat | Deferred | No current chat interface, live assistant, or conversational workflow exists. | Do not promote until there is a real product surface. |
Credential language
The demo can show missing mandatory requirements clearly. It cannot yet claim full compliance automation, expiry evidence handling, or regulatory reporting.
Integration architecture
The module story becomes stronger if operational source access and later Xero or MYOB field alignment can be verified during real partner discovery.
Commercial use
Use the demonstrated layer to start the conversation. Keep the named-only layer out of the headline.
The strongest current commercial movement still starts with the Dispatch Blind-Spot Diagnostic or the executive design-partner briefing, not a long list of module names.