Twins

Twins is the human-in-the-loop decision queue. The digital twins propose actions, and nothing on this page goes out until an operator approves it. The page title is Actionable Twins. Open it with Twins in the bottom navigation (/twins).

The compliance, finance and operations twins run automatically each time a session fetch completes (see Fetch), so this page shows what they produced without you having to start anything.

What is on the page

From top to bottom (on a wide screen, the right-hand cards sit beside the queue):

Section	What it shows
IMPACT POTENTIAL	The figure the server reports for the last 7 days, in USD. It reads `…` while loading and `—` when the server reported no figure.
ACTIONABLE TWIN STATUS	The filter chips (below).
PRIORITY ACTIONS	The action cards waiting for a decision.
Shadow Stealth Analysis	Shown only when there are results: the Query and its Relevance.
Remediation orders	Work orders derived from compliance findings.
Findings and Measures to take	The posture assessment’s findings, worst first, and the measures that answer them.

Under the page header, Refresh re-reads the queue once. While a session fetch is running, the page also shows Updating with the latest results… and re-reads the queue by itself until the fetch ends.

Filter the queue

The chips under ACTIONABLE TWIN STATUS are All, COMPLIANCE, FINANCE, OPERATIONS, S&OP, SAVINGS, ESG and PROCUREMENT. Tap a chip to ask the server for that domain only. A selected chip shows a check mark as well as its colour.

While a filter is on, a notice titled Filtered to {filter} explains that cards filed under another chip are not in the list. Show all removes the filter.

The last chip, Today’s Command, doesn’t filter anything. It opens the Today’s Command view.

COMPLIANCE, FINANCE and OPERATIONS each have a chevron button (tooltip Open COMPLIANCE, and so on). The chevron opens that twin’s remediation screen.

Review an action card

A card shows its type (or ACTION), a priority chip with the priority word (or NORMAL), a deadline mark, and the stage and run that produced it, for example RECONCILE, FETCH or SIMULATE. Below those come the title and description. Tap the card to expand it and see its artifacts: the email draft (TO:), the calendar invite and the ERP change (ERP: / Action:).

The header buttons are:

Review Action (pencil) opens a dialog that summarises the decision, with Cancel, Reject and Approve.
View full decision artifact opens the decision artifact for this card.
Reject Action — records a decision (✕) starts a rejection.

Cards are grouped by deadline: Dated — soonest first, Date not established and No deadline applies. A date marked This date is behind this device’s own date. is compared against your device’s clock.

Approve

### Expand the card Tap the card and read the artifacts it will produce. ### Select Approve The card leaves the queue at once. The decision is queued on your device and sent to the server as soon as there is a connection, so an approval made offline is not lost. ### Read the outcome If the card has artifacts, the cockpit opens its decision artifact in the approved state. Otherwise it shows **Action approved — queued for execution.**

When the server records an approval but a part of it could not run, a notice titled Recorded, but not executed lists each part with its reason. For example, an email is not sent when no Google connector is configured for the account.

Reject

Every rejection asks for a reason first, because the reason is the only record of why the card was refused.

### Select Reject or the ✕ button The dialog **Why are you rejecting this?** opens and names the card. ### Write your reason Type it in **Your reason**. The counter below the field shows how much room is left. An empty reason is refused, and so is a reason too long to keep word for word. Long text is never cut short. ### Select Reject with this reason The card leaves the queue and the rejection is kept in the card's decision record. If you change your mind later, the new decision is added to that record. It doesn't replace the old one. **Cancel** leaves the card where it was.

Analyze a document

The upload button (Analyze document) sends a csv, txt, tsv or json file of up to 3 MB to the twins. Each agent’s progress shows in a dialog (Waiting for this agent…, Running, Reported), and the queue is re-read when you close it.

Remediation orders

Each compliance finding can become a work order: the procedure, the specifications it must meet, and who it is addressed to. FACE sends no order anywhere. Approving records a decision, and then a person sends the order and marks it sent. Orders are grouped under WAITING FOR A PERSON and DECISION ON RECORD.

On an order card:

NOTE is your reason in your own words. A rejection needs one.
CHANNEL is how you sent it (email, ticket, phone, and so on).
Assign opens Address this remediation, with the fields DEPARTMENT, SERVICE PROVIDER and CONTACT, and the buttons Save assignment and Cancel.
Approve and Reject record a decision.
Mark sent — records that you sent it; FACE sends nothing records that you sent it.

An order’s state chip reads DRAFT, APPROVED, REJECTED or SENT. An order with no decision yet shows NOBODY HAS DECIDED, and one with no recipient shows ADDRESSED TO NOBODY YET.

The orders section tells a failed request apart from an empty answer:

Heading	Meaning
ANALYSING	A compliance analysis is running.
THE ANALYSIS FAILED	The request failed. This is not an estate with nothing to do.
NOTHING HAS BEEN ASKED YET	No compliance analysis has run here.
NO ORDERS WERE DERIVED	Either no finding came back, or none could be turned into a procedure. Neither means the estate is clear.

What the states mean

You see	Meaning
Digital twin reasoning…	The queue is loading.
Failed to fetch action queue: {error}	The cockpit could not read the queue. This is not an empty queue.
No priority actions	The twins have nothing waiting for you. New decisions appear as fetches and simulations complete.
NOTHING WAS REPORTED (Findings)	The assessment returned no findings. That describes the response. It is not a verdict that the estate is clean.
Nothing is connected yet	No data source is attached to the instance. The instance’s own reply is shown under What this instance replied, in English:, and Connect a data source opens Connections.

RPCs behind this page

TwinsService.GetActionQueue, TwinsService.ExecuteAction (sent from the offline queue), TwinsService.UploadAnalyze (server stream), TwinsService.GetSavingsSummary, LandingService.GetDashboardStats, PostureService.GetHealthScore, and ComplianceService.AnalyzeCompliance, AssignRemediation and DecideRemediation. See the API reference.

Reconcile Remediation