Technology overview

Where does LimFlex sit in the stack?

Insert LimFlex between the model draft and material-action calls such as executeRefund(), updateRecord(), or publish().

Model draft→LimFlex check→Decision artifact→Host decision

Product sends

Draft + context + evidence refs + policy id.

Workflow config

Vendor-defined action type, evidence, authority, and policy constraints.

LimFlex evaluates

Apply configured checks at the action boundary.

Decision artifact

Allow / Hold / Review / Block.

Host decides

Execute, withhold, or route. LimFlex does not execute.

What LimFlex evaluates

Config, evidence, authority, policy fit, and the returned decision artifact.

Configure

Vendor-defined checks

Define action type, required evidence, approval authority, and policy constraints.

Evaluate

Before action

Review draft, context, evidence refs, and policy id at the action boundary.

Return

Decision artifact

Return decision, reason, missing evidence, and next route.

Authority

Decision artifact ≠ execution authority

LimFlex returns the artifact. The host product executes, withholds, or routes.

What builders need to know

Policy ownership, failure mode, scope, and uncertainty routing.

Config

Vendor-controlled policy.

Policy IDs point to vendor-controlled workflow policy/config. LimFlex checks against that configured boundary; the host product keeps business and execution authority.

Failure

No silent approval.

When required evidence is missing, LimFlex should return Hold or Review with a reason and next route.

Scope

Not a text guardrail.

Text guardrails shape output. LimFlex focuses on the action boundary: evidence, authority, reason, and escalation route before your product executes, withholds, or routes.

PoC

Separate uncertainty.

Deterministic checks, model-assisted checks, and uncertainty routing can be separated by PoC scope.

Where LimFlex sits in the stack

Between model draft and material-action calls, return a decision artifact before host execution.

API-ish builder example

Illustrative schema. Actual schema may vary by implementation and PoC scope.

Model draftAI proposes text or action intent.

LimFlex checkEvidence, authority, policy, risk.

Decision artifactAllow / Hold / Review / Block.

Host decisionExecute, withhold, or route.

Input

{
  "draft": "I refunded $149 to your card.",
  "action_call": "executeRefund",
  "action": {
    "type": "money.refund",
    "amount": 149
  },
  "context": {
    "workflow": "support_refund",
    "actor": "support_ai"
  },
  "evidence_refs": [
    "order_record",
    "payment_record"
  ],
  "policy_id": "refund_policy"
}

Output

{
  "decision": "hold",
  "reason": "Duplicate charge evidence is missing.",
  "missing_evidence": [
    "matching_payment_event"
  ],
  "next_route": "human_review",
  "safe_reply": "I need to verify the charge before processing a refund."
}

Configpolicy_id refers to vendor-controlled workflow policy/config.

FailureMissing required evidence should route to Hold or Review, not silent approval.

DeterminismPoC scope should separate deterministic checks, model-assisted checks, and uncertainty routing.

Decision states

A tiny state machine for one-scan buyer review.

AllowRequired evidence and policy checks pass.

HoldEvidence is missing or uncertain.

ReviewHuman approval is needed.

BlockPolicy, authority, or action risk fails.

Public boundary

This page shows public connection concepts, not patent-sensitive internal mechanisms.

Technology boundary: public schema examples only; internal mechanisms and patent-sensitive details remain out of scope.

Technology Contact