Rules Reconciler

Roster name: recon. See also Rule governance.

What it does

It checks that the business rules your governance board approved are the rules the CapEx engine actually enforces, rule by rule, with citations.

What it reads

• The tenant’s governance rule book: each rule’s status, the decision behind it, its owners, approved thresholds, and approved free-text new rules.
• The rules the engine evaluates, with the thresholds it uses and where each is raised.

What it produces

One verdict per rule, each citing what exists: the governance record, the engine rule, or both (a Shadow rule has no governance record; a Missing rule has no engine rule):

• Aligned: the engine applies the rule as approved.
• Drift: same control, different condition or threshold.
• Shadow: logic runs with no governing rule. A fresh workspace is mostly Shadow, by design.
• Missing: an approved rule nothing enforces.

The report appears in the console, and in the “Rules reconciliation status” issue when that sink is configured.

Human oversight

A person fixes the rule or the engine, through the four-eyes rule workflow. The reconciler changes neither.

Model

Qwen3.6-35B-A3B, by Qwen, licensed Apache-2.0 (the general tier), for one question only. Everything else is deterministic code. Runink domain adaptation for this agent is planned; this release uses the base model.

Where it runs and data handling

On your Runink TIDE deployment’s own inference, on your Server or in your cloud. Rule text goes to that model plane and to no third-party AI service.

Guardrails

• Deterministic first: every engine rule is reconciled by code.
• The model answers only “is this approved free-text rule already implemented by one of these engine rules?” with a rule, none, or unclear. Unclear is preferred to a guess, and it gives no confidence score.
• Anything it could not read is listed, and the report is marked incomplete.
• Rule text that tries to dictate the answer is treated as data.

Limitations

• It reconciles the CapEx engine’s rules, not other systems.
• It does not score rules.

Evaluation

No published evaluation scores yet.

Illustrative example

Invented rules. The board approved “flag any capital purchase line above 750 per unit.” The engine flags above 500. Verdict: Drift, “same unit-price check at 500, not 750.” The engine also runs a split-invoice check with no rule-book entry: Shadow.