MANSOQ Knowledge
← Knowledge library

Security & governance

Explain why a financial decision was made

Read the configuration package, selected rules, rejected candidates and evidence behind an amount.

Current source · source reviewed · 6 min read

Before you begin

1. Open the decision trace

Use Decision Traces or the corresponding trace/explain view for the subject. Confirm the subject and decision time.

One source-backed synthetic remittance trace records900 SAR and an immutable teaching package; the evidence label derives from the deliberately fictional response fixture.
Select the immutable remittance decision trace · 2026-10-18. Current audited MANSOQ application in an isolated local synthetic training environment. One source-backed synthetic remittance trace records900 SAR and an immutable teaching package; the evidence label derives from the deliberately fictional response fixture.

2. Read package and open gates

Inspect configuration package label, sequence and content hash, then blocking gates recorded at the decision time. Compare package versions first when decisions disagree.

The teaching package retains 25 open gates. Its passed test explicitly covers local engine-policy construction and database constraints only, not production qualification.

The expanded trace shows its immutable package hash, distinct teaching publisher/approver and 25 open gates. The passed fixture test explicitly covers database/policy construction only, not production qualification.
Inspect the package and qualification limits · 2026-10-18. Current audited MANSOQ application in an isolated local synthetic training environment. The expanded trace shows its immutable package hash, distinct teaching publisher/approver and 25 open gates. The passed fixture test explicitly covers database/policy construction only, not production qualification.

3. Read outcome and value state

Review the coverage outcome and paired amount/value state. Unknown is a different fact from an established zero.

4. Inspect the selected chain and alternatives

Follow contract, agreement, assignment, pricing date, tariff, benefit, exclusion, exception, components and consumed buckets. Read reason_trace for losing candidates and why each was rejected.

For the remittance trace shown, read the remittance-specific claim_match step and its claim_number precedence rule. Empty generic tariff-chain candidates do not mean the advice matching decision lacked its own recorded reason.

The remittance-specific chain preserves600reported paid,300reported adjustment and the explicit claim_number match at precedence 10. Empty generic tariff candidates are unrelated to this remittance matching decision.
Read the remittance claim-match reason · 2026-10-18. Current audited MANSOQ application in an isolated local synthetic training environment. The remittance-specific chain preserves600reported paid,300reported adjustment and the explicit claim_number match at precedence 10. Empty generic tariff candidates are unrelated to this remittance matching decision.

5. Assess evidence and reproducibility

Read weakest_evidence, engine_version and decided_at. Use decision_package when the immutable configuration behind the decision is required.

A correct amount still needs a correct reason

A coincidentally right number selected through the wrong contract or rule is a defect. The trace supports correcting the actual selection rather than changing the visible total.

Historical access

Published packages and traces are append-only. Corrections create new sequences; historical explanations remain linked to the earlier package.

What the current screenshots demonstrate

These are current captures from an isolated Polyclinic training environment, using explicitly fictional insurance, response, authorization, remittance and policy fixtures. They demonstrate the displayed controls and scoped observations only. They do not establish live payer connectivity, a genuine insurer approval, regulatory qualification, production tax filing, a complete role/facility matrix or a cleared financial estimate.

Troubleshooting

A decision has no usable explanation

Record its subject and package identifiers and escalate to the RCM/engineering owner. Do not reconstruct a supposed source from current configuration alone.

Source evidence

References are pinned to the private MANSOQ source repository. Repository access is required to open these links.