Intent and context
Describe the intended action, its scope, and the available information before assigning it authority or an outcome.
Swiss research and development association
Make automated actions more controllable, traceable, and verifiable.
SwissTokint studies how to check whether an automated action follows its intended rules before it is performed, and how an authorisation, observed outcome, and verifiable evidence can then be connected.
Open research · POM-RX v0.1 · published technical boundaries.
An automated-action cycle
Read the cycle without conflating its stages.
SwissTokint studies the roles before and after an automated action. Each stage contributes bounded information without turning an intent, authorisation, or observation into proof of everything else.
Policy, control, and authorisation
Keep the policy engine, pre-execution control, and authorisation decision separate; each may belong to another component or role.
Observation, reconciliation, and evidence
Connect an observed outcome with what was expected, retain bounded evidence, and make the remaining unknowns explicit.
Current research project
POM-RX v0.1 — a structural check of supplied receipts.
POM-RX v0.1 is a public working specification and tested prototype. It describes three supplied receipts — preflight, execution acknowledgement, and reconciliation — and their structural check. A policy engine, an authorisation decision, external observation, and reconciliation remain distinct roles that POM-RX neither replaces nor establishes.
POM-RX v0.1 — public working specification and tested prototype.
POM-RX explores how a supplied receipt chain can link a declared policy, a pre-execution check, an authorization, an execution acknowledgement, and reconciliation.
The pinned public commit contains the `pom-rx/0.1` schema, one Node/TypeScript reference verifier and one seven-test Node suite. The verifier checks the supplied structure, contiguous phase order, selected shared fields and receipt hash links.
These checks apply only to the supplied receipts. They do not establish trusted chronology, the truth of an external fact, source authenticity, authorization consumption, independent observation or execution blocking. POM-RX v0.1 does not place orders or custody assets, and is not a production control, audit, certification, or security or performance guarantee.
Application domains
Where these questions can be studied.
These cards describe study contexts, not deployed integrations. They are neither a promise of control nor evidence of execution, safety, or compliance.
Study
Payments and financial operations
Describe conditions an integration could compare before submitting an operation: beneficiary, limit, policy, and authorisations.
Study
AI agents
Separate an agent’s capabilities, rules, expected authorisations, and responsibility for a contemplated external action.
Study
APIs and enterprise systems
Examine identity, destination, context, and policy for a critical change in a bounded scenario.
Study
Cybersecurity
Model a divergence between a requested action and expected conditions without claiming to detect an incident or block an attack.
Study
Blockchain and digital assets
Study the role of a network, destination, contract, or hash anchoring without treating a ledger as the truth of an external fact.
Learning Hub V3
Explore six learning paths at your own pace.
The Learning Hub offers local, voluntary learning across autonomous systems, pre-execution control, POM-RX, security, blockchain, and governance. It grants neither certification nor a level of mastery.
Association
A research mission and institutional framework kept distinct.
Constituted in Martigny, Association SwissTokint documents its mission, public resources, and institutional boundaries without presenting itself as a bank, financial company, auditor, or certification body.
Resources and contact
Read the resources, then prepare an email.
Documentation points to the current public resources. The contact form prepares an email in your mail application; it sends nothing to the site server.