01 · THE GOVERNED RUNTIME

A governed runtime forregulated operations.

A regulated action does not move through Senbert as an unbounded request. The runtime resolves context, establishes identity and entitlement, applies configured policy, executes the appropriate service and preserves the resulting state and evidence.

AUTHORITY / JURISDICTION CONTEXTThe execution boundary is resolved first.
RulesPermissionsApproval gatesDecision boundaries
REGULATED ACTIONOne governed execution path
RegisterApproveAssignListTransferSettle
SENBERT SOVEREIGN INFRASTRUCTUREGoverned runtime
CONTEXT → CONTROL → EXECUTION → EVIDENCE
01
RESOLVE

Jurisdiction context

Establish the Authority, jurisdiction and operating context before the action is evaluated.

02
ESTABLISH

Identity & entitlement

Resolve who is acting, what they represent and what they are entitled to do.

03
ENFORCE

Policy & permissions

Apply configured rules, permissions, approval gates and decision boundaries.

04
EXECUTE

Workflow / market service

Route the action into the appropriate lifecycle, operational or market service.

05
PRESERVE

State & evidence

Commit the resulting state and retain the material decision and evidence trail.

06
CONNECT

Approved estate sync

Synchronise through the agreed integration boundary using the interfaces available.

APPROVED EXTERNAL BOUNDARYAuthority estate & connected ecosystem

Registries · identity · payments · finance · licensing · compliance · partner systems

RUNTIME PRINCIPLEOne action. One governed execution path. One defensible evidence trail.
02 · JURISDICTION CONFIGURATION

Reusable architecture.Authority-specific runtime.

Senbert is engineered as a reusable core that can be configured for different Authorities. Each Authority runtime carries its own jurisdiction rules, lifecycle, permissions, terminology, market conventions, data boundaries and integrations.

The architecture is reusable. Each Authority runtime is separately configured and governed. Engineering is added where genuinely local requirements demand it.
REUSABLESenbert core architecture
CONFIGURED FORThis Authority / jurisdiction
RESULTAuthority-specific runtime
THIS AUTHORITY'S CONFIGURATIONDefine how this Authority's runtime must behave.
AUTHORITY-SPECIFIC
01OPERATING LOGIC
01

Policy & rules

Jurisdiction rules, eligibility and decision logic.

02

Lifecycle states

Local states, transitions, approvals and exceptions.

02CONTROL & EVIDENCE
03

Permissions

Roles, participant access and Authority decision rights.

04

Evidence requirements

Documents, attestations and validation requirements.

03LOCAL CONVENTIONS
05

Fees & currency

Local fee logic, currency and settlement conventions.

06

Terminology

Jurisdiction-specific language, labels and classifications.

04MARKET & ESTATE
07

Market conventions

Permitted activity, listing, assignment and market rules.

08

Integration adapters

Interfaces mapped to the Authority estate and approved ecosystem.

APPLIES TO THIS RUNTIMEApplies this Authority's configuration to the reusable Senbert core.
REUSABLE SENBERT COREReusable product architecture beneath each Authority runtime.
REUSABLE CORE
01Identity & entitlement02Workflow runtime03Market services04Settlement orchestration05Audit & evidence06Integration services
AUTHORITY-SPECIFIC RUNTIMEConfigured for this Authority without duplicating the core architecture.

The runtime applies this Authority's configured rules, states, permissions and interfaces to the reusable Senbert core.

SOVEREIGN BOUNDARYAuthority boundaries remain explicit.

Policy, data and integration boundaries remain explicit to the relevant Authority environment.

CONFIGURATION PRINCIPLEReuse the architecture. Configure the Authority runtime. Keep sovereign boundaries explicit.
03 · INTEGRATION FABRIC

Meet the estatewhere it is.

Senbert can connect through the authoritative interfaces an Authority has today and support deeper integration later without changing the governed operating model above the boundary.

Integration depth can evolve. The runtime contract above it remains stable.
AVAILABLE INTEGRATION PATTERNSUse the lightest authoritative interface appropriate to the operating case.
AUTHORITATIVE INPUT
01

Structured batch / file

Controlled extracts, imports and synchronisation.

02

Existing APIs

Use interfaces already available in the Authority estate.

03

Events / messages

Consume or publish governed operational events.

04

Real-time APIs

Deeper validation and update interfaces where available.

05

Approved gateways

Connect approved participants and external services.

GOVERNED INTEGRATION FABRICOne controlled boundary across multiple interface types.

Validation, mapping, orchestration, synchronisation and evidence remain governed at the integration edge.

ValidateMapOrchestrateSynchroniseEvidence
AUTHORITY ESTATE & APPROVED ECOSYSTEMConnect to the systems that remain authoritative in their domain.
AUTHORITATIVE SYSTEMS REMAIN AUTHORITATIVE
01Registries
02Identity
03Payments
04Finance
05Licensing
06Compliance
INTEGRATION EVOLUTIONDepth can increase without re-platforming the operating model.
01STARTControlled batch / structured exchange
02DEEPENExisting interfaces & APIs
03EVOLVEEvents & real-time integration
◇
INTEGRATION PRINCIPLEMultiple interface patterns. One governed operating boundary.
04 · AGENTIC SOVEREIGN OPERATIONS

Automation is boundedbefore it acts.

Senbert can use automation to support configuration and operations, but that automation remains inside configured permissions, policy, approval points, exception handling and evidence controls.

Automation supports the operating model. It does not replace sovereign decision rights.
CONTROL PLANEAuthority-defined boundaries surround automation.
BOUND BEFORE ACTION
01

Permissions

Automation can act only within configured roles and entitlements.

02

Policy guardrails

Configured rules constrain what may proceed and under what conditions.

03

Human approvals

Defined sovereign decisions remain explicit human approval points.

04

Exception handling

Ambiguity or policy exceptions are routed for controlled intervention.

05

Evidence

Material automated actions remain attributable and reconstructable.

06

Intervention / rollback

Where the process allows it, authorised users can intervene or reverse.

AGENTIC OPERATIONS LAYERAutomation executes only inside the approved control envelope.

Policy, permissions and human decision points remain upstream of automated action.

PermissionedPolicy-boundHuman-gatedAuditable
BUILD & ASSUREAssist configuration and test the operating model.
01
CONFIGURE & DEPLOYApply approved rules, boundaries and deployment context.
02
OPERATE & OPTIMISESupport runtime monitoring, exceptions and bounded operational tasks.
03
01
HUMAN DECISION RIGHTSDefined approvals remain explicit.
02
ATTRIBUTABLE ACTIONMaterial automated activity remains evidenced.
03
CONTROLLED INTERVENTIONExceptions can be surfaced for authorised action.
◇
AGENTIC PRINCIPLEAutomation operates within configured permissions, policy, human approvals and audit.
05 · TRUST & EVIDENCE CHAIN

Every material actionleaves a defensible trail.

Senbert links actor, entitlement, policy, approval, state change and evidence so a material action can be reconstructed from origin to outcome.

Trust is part of execution — not a separate log added afterwards.
MATERIAL ACTIONIdentity, authority, policy, decision and outcome remain bound together.
EXECUTION → EVIDENCE
CHAIN OF TRUSTEach material stage contributes to one defensible record.
01
ESTABLISH

Actor

Establish who performed the material action.

02
AUTHORISE

Entitlement

Resolve the role, authority and permitted scope behind the action.

03
BIND

Applicable policy

Associate the rules and decision conditions in force at execution.

04
DECIDE

Approval

Record required human or Authority approval points and their outcome.

05
COMMIT

State change

Preserve the resulting state and, where applicable, operational finality.

06
PRESERVE

Evidence

Retain the material evidence needed to reconstruct the outcome.

DEFENSIBLE RECORDThe infrastructure can answer the material questions behind an outcome.
AUDITABLE BY DESIGN
01Who acted?02What were they entitled to do?03What policy applied?04Was approval required?05What changed?06Can the outcome be reconstructed?
01
ATTRIBUTABLEThe actor and authority behind the action remain identifiable.
02
POLICY-LINKEDThe decision context in force at execution remains attached.
03
RECONSTRUCTABLEThe material path from action to outcome can be evidenced.
◇
TRUST PRINCIPLEActor, authority, policy, approval, state and evidence remain connected.
06 · SOVEREIGN DEPLOYMENT & EXTENSION

Deploy to the boundarythe Authority requires.

Senbert architecture can be placed in approved technical environments while preserving an Authority-specific runtime, explicit data and integration boundaries, and clear operational interfaces.

Technical deployment aligns to the selected Authority operating model; it does not redefine sovereign mandate.
TECHNICAL PLACEMENTDifferent infrastructure locations. The same Authority-specific runtime discipline.
01

Senbert-managed approved environment

Where the selected operating model places technical responsibility with Senbert.

02

Authority-controlled infrastructure

Where the Authority requires direct control of the technical environment.

03

Sovereign / private or approved regional cloud

Where residency, isolation or approved regional placement determines infrastructure location.

AUTHORITY-BRANDED EXPERIENCEThe Authority defines the service experience. Senbert provides the infrastructure beneath it.

Participant-facing services do not need to present Senbert as the service brand.

Authority identity & branding

Present the service under the Authority's identity and visual system.

Jurisdiction terminology

Use Authority-approved language, classifications and service terminology.

Authority service / domain presentation

Present participant-facing services through the Authority's approved service and domain experience.

Configured communications

Align notices, workflow language and participant communications to the Authority service.

RESPONSIBILITY REMAINS EXPLICITProvider disclosures, hosting and technical responsibility remain aligned to the selected deployment model and applicable requirements.
AUTHORITY-SPECIFIC RUNTIMEConfiguration and sovereign boundaries remain attached to the deployment.

Data residency

Keep data placement aligned to the approved jurisdiction boundary.

Deployment isolation

Maintain separation appropriate to the Authority runtime and operating model.

Integration boundary

Expose only the interfaces approved for the surrounding estate.

Operational interfaces

Make technical responsibility and intervention points explicit.

EXTENSIBILITY MODELAdd domain capability without rebuilding the reusable core.
01
FOUNDATION

Reusable Senbert core

Reusable product architecture and platform services.

02
CONFIGURE

Authority configuration

Jurisdiction rules, lifecycle, permissions and evidence requirements.

03
SPECIALISE

Vertical capability

Domain-specific capability where the regulated market requires it.

04
CONNECT

Integration adapters

Interfaces mapped to the Authority estate and approved ecosystem.

◇
PLATFORM PRINCIPLEReusable architecture. Authority-specific runtimes. Authority-branded experience where required.