Regulatory compliance & delivery methodology

Compliance as architecture

What sets our agent products apart is that regulatory compliance is built into the product architecture. Every requirement maps to an engineering mechanism, and the products ship with six go-live red lines — cross any one, and it does not go live.

Six regulatory gates, each engineeredSix go-live red linesA0–A4 action autonomy scaleA 90-day roadmap
Regulatory basis

Three regulations, six gates

Our products provide an engineering answer to each of the six gates these regulations establish: human oversight, explainability, review of customer rights, training-data red lines, high-risk approval, and filing and accountability. In FMCG, pharmaceuticals and other industries, the same mechanisms also carry general requirements such as the Personal Information Protection Law, as well as industry rules.

  • Interim Measures for the Administration of Generative AI ServicesIn force since 2023
  • Measures for Labeling AI-Generated Synthetic ContentIn force since 2025
  • NFRA Jin Fa [2026] No. 8: Guidelines on the Safe Development and Application of AI in Banking and Insurance32 articles
01 · Human oversight02 · Explainability03 · Customer-rights review04 · Training-data red lines05 · High-risk approval06 · Filing & accountability
Engineering mapping

Every regulatory requirement lands on an engineering mechanism

01
Human oversightTiered approval gates and a suspendable state machine
02
Explainability & traceabilityEnd-to-end tracing and a unified case file in which every conclusion points back to its source
03
High-risk admissionDual go-live thresholds, shadow runs and emergency-stop drills
04
Data red linesOn-premises deployment, field-level permissions and training isolation
05
SecurityGuardrails, sandboxes and red-team testing
06
Lifecycle accountabilityApplication registry, version-bound approvals and tamper-proof audit logs
The products also ship with six go-live red lines. Crossing any one of them blocks go-live.
Delivery methodology

One principle, four planes, ten components

The principle is “trade control for autonomy”. Four planes form a bank-wide shared foundation; each scenario is simply a tenant on that foundation.

  1. Plane 01Business process plane
  2. Plane 02Agent runtime plane
  3. Plane 03Capability & integration plane
  4. Plane 04Control & evidence plane

How scenarios are prioritized

We follow a priority matrix of “scalable augmentation first, reversible, well-evidenced” — an irreversible scenario never enters the priority zone, however valuable it is.

Two scales

L levels govern applications. A levels govern actions.

L0–L5 and A0–A4 do different jobs and work together. The L scale asks how much autonomy an agent application may have, for tiered admission of applications and scenarios. The A scale asks how far a single action may be automated, as a bank-wide measure for every action. New scenarios define the domain, then the level, then start work.

L levels govern applications. A levels govern actions.
LevelMeaningTypical actions
A0 Retrieve / read-onlyRead-only retrieval, citing sources and summaries; no source, no answerPolicy Q&A, clause lookup
A1 AdviseGenerates advice, scores and drafts; writes to no business systemFirst-draft credit opinions, red-flag alerts
A2 Pre-fillWrites drafts and to-dos that stay “unsubmitted” and can be withdrawn in fullApplication pre-fill, draft reports
A3 Execute after approvalAfter an authorized signature, calls allow-listed deterministic commandsSubmitting for approval, sending notices
A4 No autonomyMay never be triggered or decided by an agent; supporting material onlyFunds transfers, regulatory filings, account freezes
90-day roadmap

Each phase ends in an accepted deliverable — the ticket to the next

  1. Days 1–15

    Decide and map

    Review how the core principles fit your bank; map the first scenario’s real process to roles and systems, and mark every step that needs a human signature.

    DeliverableScenario selection report + human checkpoint list
  2. Days 16–45

    Build the hub, fix the contract

    Stand up the minimum viable Harness: admission, planning, state machine, tool gateway, policy gate, validator; lock in the task contract and mandatory stop conditions.

    DeliverableTask contract + control-module list + test set
  3. Days 46–90

    Run end to end, pass the gates

    Run the full chain from read-only assistance to draft write-back, pass dual go-live threshold tests and emergency-stop drills, and produce a complete audit trail.

    DeliverableValidation report + admission decision + go-live plan
Where this ends up
Let AI take on roughly 80% of cognitive and operational work — while fact-finding, exception judgment, major risk decisions, customer-rights decisions and accountability stay firmly inside a controlled governance system.
  1. The modelthinks
  2. The agentdoes
  3. Rulesdecide whether it may be done
  4. Harnessmakes sure it is done safely
  5. Peoplehold final accountability
Get started

Start with one business question. Let SAM deliver a model you can sign off.

Whether you are in banking, FMCG and marketing, pharmaceuticals or another industry, try SAM online first — or talk to our modeling experts about your use case.