Remediation

Each of the three domain twins has a detail screen that shows what it assessed:

Compliance Remediation (/compliance_remediation)
Finance Remediation (/finance_remediation)
Operations Remediation (/operations_remediation)

To open one, go to Twins and select the chevron beside COMPLIANCE, FINANCE or OPERATIONS under ACTIONABLE TWIN STATUS. The tooltip reads Open COMPLIANCE, and so on. Plan remediation on Reconcile also opens the compliance screen. The back arrow (Go back) returns you to Twins.

The twins analyse the findings of your session fetch. The analysis runs automatically when a fetch completes, so these screens usually show a result already. Refresh runs the analysis again. It stays disabled until a session fetch has run, and its tooltip explains why.

What each screen shows

The verdict banner: the status the server reported, and how many violations or findings it counted.
The live-data note: the server’s statement of which data the verdict rests on, word for word.
The spoken summary.
VIOLATIONS ({count}) or FINDINGS ({count}). Each item shows a severity word, its category and description, Remediation:, and the rule it was checked against (Rule:).
AUDIT TRAIL: the systems that were checked, each with a status word and when it was last checked.

The verdict banner has three kinds. Each has its own glyph, so the difference never depends on colour:

Banner	Glyph	Meaning
Clear	verified shield	Assessed, with nothing to act on.
Action required	shield with a question mark	Assessed, with violations or findings to act on.
Unable to Assess (or another status that says it could not assess)	question mark	Not a verdict. Nothing could be assessed. The spoken summary gives the reason and says plainly that this is not a finding of compliance.

Could not look, or found nothing?

You see	Meaning
Compliance analysis failed: {error} or Analysis failed: {error}	The request failed.
Unable to Assess, zero violations, and a grey banner	The server answered, but it could not produce an assessment, for example because no connected data source was read. Connect a data source and run it again.
No violations detected. or No findings detected.	The twin assessed and found nothing.
No compliance analysis available.	No analysis has run yet.
Run a session fetch first — this twin analyzes that instance’s real findings.	No session fetch has run yet. Run one from Fetch.

Work orders

Findings can become work orders. On the finance and operations screens, each finding is followed by its order card, or by No work order was derived for this finding. What the records supported is the line above. The compliance screen tells you how many orders were derived. You work those orders under Remediation orders on Twins.

The routing table

On Compliance Remediation, Routing table holds your own map from finding category to department. FACE holds no org chart and proposes no route. A rule applies to future orders only. It sends nothing, and it does not re-address an order somebody already assigned by hand.

### Open Routing table Select the **Routing table** button in the title bar. ### Set or clear a rule Each category shows **RULE SET** or **NO RULE**. Enter a **DEPARTMENT**, a **CONTACT**, or both, then select **Save rule**. The server refuses a rule that names neither. **Delete rule** removes the rule, and findings in that category then arrive unrouted. A category marked **NOT IN THIS ANALYSIS** has a rule but no finding in the current analysis. You can still see and remove its rule here. ### Read the result **Rule saved.** or **Rule deleted.** confirms the change, and the rule records who set it and when. A message starting **NOT saved** or **NOT deleted** means nothing changed, and it gives the reason.

RPCs behind these screens

ComplianceService.AnalyzeCompliance.
FinanceService.AnalyzeFinance.
OperationsService.AnalyzeOperations.
ComplianceService.AssignRemediation, DecideRemediation.
ComplianceService.ListRemediationRoutes, SetRemediationRoute, DeleteRemediationRoute.

See the API reference.

Twins Simulate