Votre système a dit NON.
BOUNDA proves what still became real.
11 Consequence Boundaries. Une seule logique Evidence Close. HELD, BREACHED ou UNKNOWN — scellé dans un Evidence Pack que votre auditeur peut vérifier sans faire confiance à BOUNDA.
Lecture seule · Aucun identifiant · Aucun write production · External Verify · Deux semaines · Un Evidence Pack
Names indicate common systems, providers or preuve sources BOUNDA can analyze through client-controlled exports. No partnership or endorsement implied.
Un log prouve ce que le système a dit. Pas ce qui est devenu réel.
BOUNDA ne remplace pas SIEM, IAM, SCADA, observabilité ou moteurs de policy. Il prouve la conséquence aval qu’ils ne prouvent pas par défaut.
Paiement DECLINED
Une capture, un fee, un settlement ou un objet provider existe-t-il ?
Agent REJECTED
Un tool call, des tokens, une mémoire ou un workflow ont-ils eu lieu ?
Export DENIED
Une URL signée, un fichier, des bytes ou une réplique existent-ils ?
Accès REVOKED
Un token, une session ou un credential a-t-il survécu ?
Job CANCELLED
Did a retry, worker or webhook still run?
Commande BLOCKED
Did an actuator, fieldbus or physical action move?
11 Consequence Boundaries. Une logique de preuve unique.
Boundaries are product families. Surfaces are concrete flows. Markets are commercial bundles. This is the core grammar of BOUNDA.
Money Boundaries
Did money still move?
Prove whether money, fees, settlement, payout, refund or provider objects were born after a financial NO.
Agent Boundaries
Did the agent still act?
Prove whether an AI agent created a real effect after REJECTED, BLOCKED, DENIED or CANCELLED.
Data Boundaries
Did data still exist or leak?
Prove whether data was created, exposed, copied, cached or exported after DENIED, BLOCKED or DELETE_CONFIRMED.
Identity Boundaries
Did access still survive?
Prove whether an access right survived or was created after REVOKED, DENIED or DISABLED.
Workflow Boundaries
Did the process still run?
Prove whether asynchronous operational effects still ran after CANCELLED, TIMEOUT, FAILED or ABORTED.
State Boundaries
Did state still change?
Prove whether state changed after CANCELLED, FAILED, ROLLBACK or DENIED.
Compute Boundaries
Did compute still burn?
Prove whether compute, cost or simulation artifacts were born after STOPPED, CANCELLED or TIMEOUT.
Engineering Truth Boundaries
Did engineering truth still mutate?
Prove whether PLM, MBSE, ALM, BOM, MES or Digital Twin truth mutated after a blocked engineering change.
Physical Boundaries
Did the physical world still move?
Prove whether a physical command, actuator, PLC sequence or fieldbus effect occurred after BLOCKED, STALE or NOT_VALIDATED.
Publication Boundaries
Did an unproven claim still go live?
Prove whether a report, dashboard, board memo or compliance claim was published without the required preuve.
Network Boundaries
Did the partner still receive something?
Prove whether a backend call, ACK, MFT file, EDI document, webhook or partner artifact was born after REJECTED.
Choisissez une boundary. Envoyez des reçus en lecture seule. Recevez un verdict scellé.
1. Decision
DECLINED, DENIED, REJECTED, CANCELLED, BLOCKED.
2. Receipts
Provider logs, IAM exports, storage inventory, queues, DB audit.
3. Units
Fee, token, URL, credential, retry, DB write, GPU cycle, actuator.
4. Verdict
HELD, BREACHED ou UNKNOWN. No fake clean claim.
5. Pack
Certificate, ledger, graph, manifest, Merkle, external verify.
Regardez la réalité franchir la boundary.
Votre système a dit NON. BOUNDA checks whether forbidden Reality Units were born anyway — with expected/observed deltas, receipts, proof sufficiency, verdict and action.
The RC16 Reality Passage Engine is preserved and now re-centered on the final Boundary taxonomy.
Pas un simple rapport. Un Evidence Pack scellé.
A replayable package that proves what happened after the NO — or proves why BOUNDA cannot safely claim HELD.
Boundary Verdict Certificate
HELD / BREACHED / WATCH / UNKNOWN.
Consequence Unit Ledger
Every event, delta and unit.
Preuve Sufficiency Matrix
What can be claimed, what is blocked.
Consequence Graph
Root cause and propagation chain.
Reality Budget
Measured, derived, modelled and unknown value.
External Verify
SHA-256, Merkle root and offline verifier.
boundary: Money
surface: Payment
decision: DECLINED
verdict: BREACHED
unit.provider_object: +1
unit.fee: scoped.71
unit.webhook: sent
unit.settlement: UNKNOWN
manifest: sha256
merkle_root: verified
external_verify: PASS
Les marchés sont des bundles. Les Boundaries restent propres.
Finance n’est pas une boundary. Finance / PSP combines Money, Identity, Workflow, State and Network Boundaries. Même logique pour IA, Cloud, OT et partenaires.
Finance / PSP
Prove financial consequences after payment, KYC, refund, settlement and partner NOs.
Explorer →AI / MCP
Prove whether rejected agents still called tools, burned tokens, wrote memory or triggered workflows.
Explorer →Cloud / IAM / Data
Prove whether denied exports, revoked access or deleted data still exist downstream.
Explorer →API / MFT / B2B
Prove whether a rejected flow still produced an ACK, file, webhook or partner state.
Explorer →OT / Industry
Prove whether blocked commands still created physical or engineering consequences.
Explorer →SaaS / Platform
Prove consequences across tenants, exports, access, webhooks and asynchronous jobs.
Explorer →Preuve à l’échelle. Claims avec discipline.
50.47M/s
Évaluations de boundaries par seconde.
<11µs
Latence p99 du chemin de décision.
61.5×
Throughput de replay batch.
11.3M/s
Éléments de preuve vérifiés en externe.
Benchmarks internes — à valider sur le périmètre client en lecture seule. BOUNDA mesure la valeur ; il ne garantit pas un ROI.
Choisissez une boundary.
Nous la vérifions.
Read-only. No credentials. No production write. One Evidence Pack.