Example Output
What a governed decision looks like.
Nexure outputs a workflow verdict and stores a defensible record. This page shows the exact artifacts buyers ask for: Decision Log, Decision Detail, and Policy Definition.
1) Decision Log (system of record)
| Decision ID | Entity | Outcome | Timestamp |
|---|---|---|---|
| dec_a13f9c | Opportunity • $180k Renewal | ESCALATE | 2026-01-03 19:12:44Z |
| dec_92bd11 | Deal • Discount 22% | BLOCK | 2026-01-03 18:41:09Z |
| dec_7c10aa | Account • New (7d) | ALLOW | 2026-01-03 18:05:21Z |
2) Decision Detail (why view)
OutcomeESCALATE (manual review required)
PolicyRevenue Gate v1
Top signalsNew account • anomalous login pattern
ControlOwner approval + manager sign-off
Rule hits (explainability)
| Rule | Delta | Reason |
|---|---|---|
| new_account | -20 | account_age_days=7 < 30 |
| suspicious_login_activity | -30 | failed_logins=4 > 3 |
3) Policy Definition (read-only)
| Policy | Version | Condition | Outcome |
|---|---|---|---|
| Account Trust | v1 | account_age_days < 30 | -20 |
| Account Trust | v1 | failed_logins > 3 | -30 |
| Geo Risk | v1 | country in RU/IR/KP | -40 |
In the pilot MVP, policies may be YAML/JSON-backed and rendered read-only. Editable policy tooling comes after wedge validation.