Payment, device and CRM signals are joined into one case.
Each finding links to its source, so people can check it.
Options are tested, then checked against policy and authority.
Actions, approvals and the outcome are saved with the trace.
Decision trace
A clear record of how every decision was made.
Every POLARIS IQ decision leaves a trace you can read: the signals, the business context, the evidence, the options tested, the policy checks, the approvals, the actions and the outcome.
What you get
01Evidence you can checkEvery finding links back to the system it came from, so people can verify it.
02Approvals on recordThe trace shows which policies were checked, who approved and on what authority.
03Ready for auditDecisions and actions are stored with their evidence and outcome, ready for review.
How we deliver
Four stages, each ending with something you can see and review before the next one starts.
01
Signal
Signals from payments, devices, CRM or market data are linked into one case.
02
Reason
Context and evidence are gathered, each tied to its source, and the options are tested.
03
Authorise
The control plane checks budget, policy and authority, and routes the case to the right approver.
04
Record
Agents carry out approved work, and the outcome is tracked against what was expected.
What we buildOur decision trace capabilities
Signals linked into one case
Signals from inside and outside the organisation are joined into a single case to look at.
Discuss thisBusiness context
Relationships, history and policies come from across the organisation, not from one system.
Discuss thisEvidence with sources
Each finding names the system it came from, such as payments, CRM or the distributor portal.
Discuss thisOptions tested
Each option is scored on what matters most, such as cost, risk or customer impact.
Discuss thisPolicy and authority checks
The trace shows the budget, policy and approval checks applied before anything ran.
Discuss thisActions by each agent
Every action lists the agent that carried it out and the system where it happened.
Discuss thisOutcome against expectation
What actually happened is set beside what was expected when the decision was made.
Discuss thisSaved to decision memory
The full trace becomes context for the next similar case.
Discuss thisWhy an unusual transfer was held
A long-standing business client of a bank sends a large transfer to an overseas payee for the first time, from a phone the bank has not seen before. The bank must decide quickly whether to release it.
ExampleAnimated illustration
A first phase could cover
We agree scope with you before work starts. For this kind of request, a first phase usually covers:
- Link payment, device and CRM signals into one case, with each source named
- Test releasing, holding or blocking against loss, client experience and risk
- Record the policy check, the fraud team lead sign-off and the final outcome
A typical project, described to show the shape of the work. It is not a specific client.
Scope something similarFrom the Hoki portfolio
The technology we build with
We pick tools around your existing systems, your team and how the product will be run.
Each trace records
SignalsBusiness contextEvidenceOptions testedPolicy checksApprovalsActions and outcome
Evidence comes from
CRMERPPaymentsDocumentsSensorsMarket data
Read by
ManagersApproversRisk and compliance teamsAuditorsIT and security teams
Where this applies
The same engineering, shaped by the rules and realities of each sector.
Financial services
Showing why a payment was held, which fraud policy applied and who signed off.
Healthcare
Recording why overflow beds were opened and which clinical policy allowed it.
Energy and utilities
Keeping the reasoning behind a repair decision, from sensor data to approval.
Manufacturing
Explaining why a second shift was added, with capacity, cost and margin checks.
Media and broadcast
Recording why extra stream capacity was booked before a live event.
Public sector and education
Giving reviewers a full account of how a recommendation was reached.
Frequently asked questions
Can people outside IT read a trace?
Yes. A trace is written as a sequence of plain steps: what was noticed, what it is connected to, the evidence, the options, the checks, who approved, what was done and what happened.
What if a piece of evidence is wrong?
Every finding links back to its source, so a person can check it before approving. Where evidence is wrong, the trace shows where the error came from, which helps fix the source.
Is a trace kept for every decision?
Yes. Every POLARIS IQ decision leaves a trace, including those that run within limits without a person. That record is what makes it possible to allow more autonomy safely.
Where are traces stored?
Traces are kept with the rest of the system, which can run in your cloud, on-premise or at the edge. How long they are kept and who can read them is agreed with you.
Another question? Email hello@hoki.co
See a decision trace on your own case
We can walk your team through a trace built from one of your real business problems.
Start a project
Tell us what you want to build.
Share a few details about your decision trace project. We will reply with questions and a suggested next step.
- What problem you want solved
- What you already have in place
- Any timing or budget you are working to
Start a project
Tell us what you want to build
A few details help us bring the right people to the first call.
Thank you.
Your enquiry is with our team. Here is what happens next.
1We read your enquiry and bring in the people best placed to help.
2We reply by email to arrange a call at a time that suits you.
3On the call, we agree a clear next step, with scope and cost.
More in POLARIS IQ
How it works
POLARIS IQ connects your systems, keeps a live picture of your busines
OpenGraduated autonomy
POLARIS IQ does not need approval for everything, and it does not act
OpenControl and security
The POLARIS IQ control plane governs how intelligence, agents and mode
OpenFor IT teams
POLARIS IQ is designed to sit inside your architecture, security model
OpenUse cases
Market, Revenue, Finance, Operations, Knowledge, Media and Vision Inte
OpenMarket Intelligence
Market Intelligence follows markets, industries, competitors and compa
OpenRevenue Intelligence
Revenue Intelligence connects customers, pipeline, pricing and commerc
OpenFinance Intelligence
Finance Intelligence reads invoices, payments, spending and cash in th
OpenOperations Intelligence
Operations Intelligence follows your processes, resources, schedules a
OpenKnowledge Intelligence
Knowledge Intelligence connects your documents, records, manuals and t
OpenMedia Intelligence
Media Intelligence connects content, audiences, assets, engagement and
OpenVision Intelligence
Vision Intelligence uses images, video and camera feeds to see what is
OpenGetting started
Nobody deploys the whole architecture on day one
Open