| Internet-Draft | Execution Finality for Cyber Defense | November 2026 |
| Das | Expires 22 May 2027 | [Page] |
A cyberattack does not have to defeat every security mechanism to become catastrophic. One internet-facing service, one stolen but valid credential, one hijacked administrative session, or one autonomous AI tool calling a legitimately available interface may be enough. The decisive risk is the transition from access, prediction, intention or nominal authorization into an actual consequence: a changed configuration, an executed privileged command, a released dataset, a provisioned cloud resource, a dispatched payment, an altered network route or an activated physical device.¶
This document analyzes two independently documented public developments of November 2026: the reported intrusion into the internal operational network of the Fugaku supercomputer through a publicly reachable status dashboard, and the reported discovery of autonomous multi-agent offensive frameworks, including an exposed framework named exploit_agent, together with cloud-credential abuse such as LLMJacking. The two events are not shown to be connected, and no public evidence shows artificial intelligence was used at Fugaku. They share a defender-risk pattern: apparently valid access becoming a real consequence.¶
The document specifies a consequence-bound architecture. A proposed operation (a Candidate Act) remains non-effective until the actual pending operation, its target, destination, scope, resource version, current authority and protected policy state have been independently validated at a defender-controlled, non-bypassable enforcement point (a Finality Sink, in industry terms a reference monitor or commit gate) located at, or unavoidably upstream of, the point where the effect becomes real. It defines normative requirements for coverage, independence, effect binding, freshness and revocation, cumulative exposure, replay and idempotency, failure semantics and safety-critical operation; application profiles for high-performance computing, cloud control planes, AI-agent tool execution, telecommunications, finance and cyber-physical systems; a counterfactual analysis of the Fugaku incident; a differentiation from conventional systems; ten falsifiable experiments; and an informative FAQ.¶
IETF relevance: the document is an architectural and requirements contribution relevant to security work on remote attestation, workload identity, delegated and fine-grained authorization, transparency of authorization evidence, and agent-to-tool interfaces. Industry relevance: the model is applicable to AI-agent platforms, cloud providers, HPC operators, telecommunications operators and financial infrastructure; the alignment sections are AI-generated, are not an endorsement, validation or infringement statement, and must be cross-checked against the original filings. Regulatory relevance: the document discusses relevance to the EU AI Act (cybersecurity and robustness of high-risk AI systems), NIS2, DORA and GDPR security of processing; it is not legal advice.¶
Based on the Mothership application PCT/IB2026/055615, filed 4 June 2026 and publicly disclosed 16 July 2026. The underlying invention is human-originated; AI-assisted tools were used to create this document, which may contain errors, and readers must cross-check it against the original, publicly available sources. To read the full PCT filing, search "Sangam Das" on WIPO PATENTSCOPE, search PCT/IB2026/055615 (pctib202655615), or read it at https://www.tdcommons.org/dpubs_series/12542/. No deployment, adoption, endorsement or performance claim is made about any third-party system, and no latency, efficacy or safety guarantee is claimed.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 22 May 2027.¶
Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
Modern defenses are layered: perimeter filtering, authentication, authorization policy, endpoint and network detection, and, increasingly, guardrails around AI models. Each layer answers a question about identity, session, request content or observed behavior. None of these questions is "may this specific, reconstructed operation, with this actual target and these actual effects, become effective at this protected boundary under the current independently protected authority?"¶
The question matters because identity-bound and request-bound decisions can be satisfied by an attacker. A stolen SSH key authenticates. A compromised dashboard process makes service-to-service calls that look legitimate. A manipulated AI agent emits a syntactically valid tool call. A correctly signed request may describe one thing while its actual side effects are another. When the consequence is irreversible (disclosure of plaintext, physical actuation, settlement, public certificate issuance), a detection that arrives after the effect cannot undo it.¶
The central proposition of this document is that "identity accepted" is not equivalent to "this specific consequential operation is independently authorized to take effect now", and that "an AI system proposed an action" is not equivalent to "the protected downstream system must carry it out".¶
This document addresses high-consequence systems: national scientific computing platforms, critical cloud management, AI-driven infrastructure operations, financial clearing and settlement, telecommunications control planes, electricity distribution, industrial safety systems and protected enterprise-data release. It is not about conversational question answering, per-token moderation, or validating every packet, instruction or floating-point operation.¶
To keep facts separate from design and speculation, statements in this document are of four kinds.¶
A published description of an attack is not proof of the victim's full configuration. A framework's capability is not proof that every observed intrusion used it. No attribution is inferred from language in source-code comments. No claim of product adoption, deployment, licensing, infringement, partnership or endorsement is made about any third-party system named here.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
PUBLIC FACT: In an English notice dated 17 November 2026, RIKEN reported unauthorized access to the internal operational network of the supercomputer Fugaku through a publicly available operational-status dashboard [RIKEN]. The reported timeline (RIKEN local time) is summarized below.¶
PUBLIC FACT: RIKEN reported that multiple internal servers were tampered with, including installation of malicious programs on some. Information from the user authentication system and files in user home directories were taken or may have been taken, potentially including names, email addresses, identifiers, stored SSH private keys and access keys, and stored research files, with a possible impact of up to 4,597 individuals across Fugaku and RIKYU users. RIKEN stated it had no evidence of exfiltration of research data or files at that time, reported attempts to connect to other systems using some obtained credentials, and was still investigating the exploitation method and secondary damage [RIKEN].¶
The notice does not establish a specific vulnerability, a credential-stealing technique, an AI offensive agent or named malware as the cause of entry, does not disclose Fugaku's full administrative topology, and does not prove the absence of exfiltration beyond the state of evidence at publication.¶
ENGINEERING INTERPRETATION: The public dashboard is the entry exposure. The potential protected effects are deeper: changing privileged server state, accessing stored secrets, authorizing later administrative operations, connecting to remote systems with stolen credentials, and releasing sensitive information. Each has its own effect boundary. Treating the dashboard as the only possible enforcement point would be an architectural error.¶
PUBLIC FACT: On 16 November 2026 Google Threat Intelligence Group and Mandiant published "GTIG AI Threat Tracker: Agentic Threat Activity Crosses a Significant Threshold" [GTIG]. As reported, threat actors used or experimented with multi-agent offensive frameworks (the report names ARTEX, CAIRN, CyberStrikeAI and PentAGI, with CAIRN and PentAGI observed in deployment). GTIG reported an exposed staging server hosting a framework it called exploit_agent, which integrated with multiple language models, compared pre-patch and post-patch software, identified likely vulnerabilities, drafted exploits and was configured to execute them automatically without a human approving each step. GTIG also described credential theft, compromised sessions, unauthorized service-account creation, cloud-resource abuse and LLMJacking, and attacks through AI-related software and coding-agent configurations [GTIG].¶
PUBLIC FACT: The report reproduced Russian-language comments from configuration material. This document does not treat language in comments as evidence of operator nationality or state sponsorship and does not state that any particular actor attacked Fugaku.¶
The Fugaku case demonstrates a pathway from an externally accessible service into an internal operational environment followed by suspected credential exposure and attempted credential reuse. The GTIG report demonstrates movement toward autonomous attack chaining and that stolen cloud credentials can rapidly become consequential consumption or privilege changes. The connection between the cases is a shared defender-risk pattern, not a shared attacker: an exposed or compromised component may supply apparent authority for a more consequential action elsewhere. Joint government guidance on adopting agentic AI services addresses the related organizational risk [AGENTIC-GUIDANCE]. It would be unsound to claim one defense would have prevented both incidents entirely. Some harms occur at the moment of exploitation or an unmediated memory read, before any separately defined control point, and some attacks target the very kernel, hypervisor, firmware or storage layer relied upon to enforce finality.¶
The controls below are valuable and are retained by this architecture. Their limits are limits of scope and trust assumption, not defects.¶
| Control | Scope limit relevant here |
|---|---|
| Firewall, WAF, ingress gateway | Cannot attest that a later privileged command from an already compromised internal host is safe. |
| Passwords, SSH keys, MFA, signed requests | Establish identity or key possession. A stolen secret looks like the principal unless hardware-bound or context-sensitive. A real user may request an effect that is unauthorized now. |
| IAM, RBAC, ABAC | Restrict action classes. Gaps may arise from stale authorization, no reconstruction of actual effects, indirect mutation paths, or inconsistent coverage across heterogeneous systems. |
| Zero trust (NIST SP 800-207) | Rejects implicit trust from network location. Whether exact effect reconstruction, resource-version binding, cumulative exposure, transitive effects and proof of no unmediated path are provided depends on the design [NIST800-207] [NIST800-207A]. |
| EDR, SIEM, SOC | Detection after a privileged operation cannot always undo it. |
| AI guardrails | Do not govern every external model, and cannot guarantee integrity of each downstream tool call. |
| Sandboxes | Still need sanctioned channels for external effects. Those channels are the consequence boundary. |
| Human approval | A person may approve a description while the actual command differs; too slow for some machine-speed flows. |
| Logs, signatures, receipts | Evidence is not prevention. A receipt from a compromised agent may be untrustworthy. A log cannot un-send stolen data. |
A conventional defense can be excellent at asking who, deciding whether a session can start, observing what happened, or preventing known threats. The architecture in this document adds one narrow question at the final boundary: may this reconstructed operation, with this actual target and these effects, become effective here under the current independently protected authority?¶
The attacker MAY control any of: a public web service or dashboard; the tools of an AI agent; an ordinary user account; stolen session material or long-lived credentials; an internal process; a delegated service identity; an automated multi-agent offensive workflow located outside the defender's administrative reach. The attacker MAY act at machine speed, in parallel, across many identities, and MAY replay valid prior requests.¶
The architecture assumes that the Finality Sink, the Protected Authority store and the necessary trust anchors remain outside the attacker's effective control. If that assumption cannot be established for an effect class, the protection claim for that class MUST be narrowed. Compromise of a hypervisor, firmware or kernel hosting the sink, collusion among sufficiently privileged administrators, and compromise of the trust root are explicitly out of the protection claim (see Section 21).¶
OUTSIDE DEFENDER DEFENDER-CONTROLLED DOMAIN
+-----------------+ +------------------------------+
| attacker, AI | request | ENTRY ENFORCEMENT ZONE |
| offensive agent,+--------->| WAF / API / SSH gateway |
| stolen-key user | +--------------+---------------+
+-----------------+ |
+---------------v---------------+
| COMPROMISABLE WORKFLOW |
| service, session, agent, queue|
+---------------+---------------+
|
+---------------v---------------+
| CANDIDATE ACT |
| actual pending operation |
| NON-EFFECTIVE |
+---------------+---------------+
|
+---------------v---------------+
| PROTECTED FINALITY SINK |
| independent validation |
| exact effect binding |
+-------+---------------+-------+
| |
DENY / HOLD / ALLOW effect
SAFE FALLBACK at the resource
Ingress and sink can coincide for a simple API. In multi-hop critical infrastructure they usually do not.¶
A Candidate Act is any proposal for a classified effect, for example "delete these records", "start these GPU instances", "grant this role", "alter routing configuration", "release this protected dataset" or "open this industrial valve". Until validated and committed it MUST remain in a Non-Effective State. A "pending" flag held only in an untrusted application database is insufficient if another path can commit the same operation without gating.¶
The Finality Sink, or a trusted component upstream of it that the initiator cannot influence, reconstructs the Actual Pending Operation: normalized arguments, resolved destination object, privilege and identity context, delegated authority, transaction or resource version, scope, side effects, targets, expected resource consumption, and transitive operations that the platform can enumerate. Approval MUST bind to this operation and not to an earlier natural-language request, a wildcard, or a mutable pointer such as "latest".¶
The validator evaluates the canonical Actual Pending Operation against current Protected Authority and trusted observations. It MUST be independent of the initiator: the same compromised agent, dashboard or credential MUST NOT be able both to propose a protected effect and to self-approve it. Physical separation is not mandatory when hardware or software isolation is demonstrably strong. Validator availability, trust roots, integrity and authenticated communication have to be engineered.¶
The Finality Sink is the protected effectuation boundary. It MAY be implemented as an application reference monitor, storage-release mediator, trusted privileged-operation gateway, scheduler administrative commit hook, cloud control-plane commit gate, protected settlement boundary, HSM-backed authorization boundary, or hardware-mediated actuator command guard. It MUST be co-located with, or unavoidably upstream of, the real effect point. A dashboard that merely displays a policy decision is not a Finality Sink.¶
The protected effect commits only if the operation still matches the validated operation and current policy conditions. Resource version, target identity, scope, signed capability, monotonic counter or transactional compare-and-swap MAY enforce the binding. The sink MUST recheck or abort if material state changes between evaluation and use.¶
A deployment MAY generate authenticated evidence of an executed bounded phase, a destination-side result, or a later reconciliation step. Such records are OPTIONAL supplements for multi-step or audit-intensive workflows. Neither agent-reported success nor the mere existence of a signed receipt substitutes for control of the actual protected effect.¶
[PROPOSED]
|
v
[NORMALIZE + RECONSTRUCT]
|
v
[NON-EFFECTIVE / PENDING] --> [DENY: policy conflict]
| --> [HOLD: fresh evidence unavailable]
v
[INDEPENDENT AUTHORIZE]
|
v
[BIND act + sink + target + scope + version + epoch]
|
v
[ATOMIC COMMIT CHECK] --- mismatch ---> [ABORT / RE-EVALUATE]
|
v
[PROTECTED EFFECT OCCURS]
|
+--> [OPTIONAL evidence, audit, receipts, reconciliation]
The Finality Sink is on the defender's side, at the protected resource boundary that makes the consequential operation effective. The entry zone is often the first enforcement location but is not necessarily the last or a sufficient one.¶
An internet-facing reverse proxy, WAF, API gateway, remote-access front end or private ingress service can perform preliminary authentication, request normalization, rate limiting, anomaly filtering and restricted routing. It cannot necessarily see the final operation after an internal service rewrites a command, a scheduler expands work, a database trigger fires, an agent calls a new tool, or an attacker moves laterally.¶
[Internet]
|
v
[Public dashboard] -- exploit / foothold --> [Internal host]
|
+----------------------+
| |
v v
[Credential use] [Direct unmediated path]
| |
v v
[Internal API] EFFECT
| (UNSAFE COVERAGE GAP)
v
[FINALITY SINK] ---> DENY
|
v
[Privileged effect, only if permitted]
The figure shows a possible architecture problem and is not the confirmed topology of Fugaku or any other system. All paths to protected effects MUST be mediated.¶
For each Protected Effect Class ask: can the same consequence become effective without passing this gate? If yes, the purported Finality Sink is incomplete for that effect. Every permitted bypass MUST be eliminated, protected by an equivalent trusted sink, or documented as an accepted residual risk. For each class an implementer SHOULD enumerate all APIs; direct file or storage access; administrative channels; job schedulers; asynchronous workers; maintenance routines; stored programs; backup and restore tools; break-glass processes; and hardware or debug paths.¶
The following requirements apply to a deployment that claims protection for a Protected Effect Class. They are stated per class: a claim for one class says nothing about others.¶
The sink MUST produce one of the following outcomes and MUST NOT default to ALLOW when the validator, policy store or evidence is unavailable for a protected effect that has no preauthorized safe fallback.¶
For every classified effect E committed on protected resource R, a deployment aims to satisfy:¶
COMMIT(E, R) implies VALID_CURRENT_AUTHORITY(E, R)
and MATCHES_APPROVED_ACT(E)
and TRUSTED_SINK_ENFORCED(E, R)
and CURRENT_POLICY_AND_SCOPE_VALID(E, R)
For a protected effect category C:
ALL_EFFECTUATION_PATHS(C) pass through an equivalent trusted sink
or are explicitly excluded from the protection claim.
¶
This is a target property for design and verification, not an empirical theorem about deployed infrastructure.¶
No single encoding is prescribed. Fields MUST be canonicalized, protected against substitution, and interpreted consistently by the signer or evaluator and the sink. Deterministic JSON canonicalization [RFC8785] is one possible choice.¶
{
"act_id": "opaque unique identifier",
"initiator_context": "authenticated principal and session",
"authenticated_delegation": "bounded delegation chain",
"operation_type": "e.g. role.grant | data.release | vm.provision",
"canonical_parameters": "normalized arguments",
"target_resource": "resolved object identity",
"effective_destination": "resolved destination",
"authorized_scope": "limits on volume, count, duration",
"expected_effect_class": "protected effect class",
"resource_generation": "version or generation at validation",
"policy_epoch": "epoch at validation",
"expiry": "validity interval end",
"nonce_or_use_count": "single-use or bounded-use control"
}
¶
on consequential_operation(request, protected_resource):
actual = trusted_reconstruct(request, protected_resource)
if not actual.is_classified_protected_effect:
return existing_authorized_processing(request)
stage_as_non_effective(actual)
context = read_protected_policy_and_resource_state()
decision = independent_validate(actual, context)
if decision is DENY:
return reject_without_effect()
if decision is HOLD:
return hold_without_effect_and_request_fresh_evidence()
if not exact_act_matches(decision, actual):
return reject_without_effect()
if not current_epoch_and_generation_match(decision, context):
return retry_validation_without_effect()
return protected_atomic_commit(actual, decision)
¶
This is a logical outline. Real implementations have to address isolation, concurrency, trust roots, deterministic safety behavior, error propagation, and whether atomic commit is possible on the target platform.¶
For cumulative effects, validation includes an atomic reservation against the Exposure Ledger for the protected exposure unit. A reservation is created before commit, converted to committed consumption on success, and released on abort or expiry. Idempotency keys and protected counters limit races and blind retries. The ledger is held by the same authority as the sink, or by a service the sink can verify.¶
Candidate effects: privileged scheduler mutations, creation of administrative identities, release of sensitive scientific datasets, high-value inter-system credential use, large quota reallocations, disabling of security controls, and job-submission privileges exceeding project scope.¶
Proposed placement: cluster administration API and scheduler configuration commit; hardware- or OS-mediated secret release; dataset access-control and release gateway; a designated privileged command broker. The gate SHOULD NOT interrupt compute-node numerics, parallel MPI communication, or high-throughput scheduling beyond the bounded administrative decisions selected by policy. If a gate is placed in a frequent job-submission workflow, queue overhead MUST be benchmarked and local checks optimized.¶
Candidate effects: IAM privilege changes, production network or firewall activation, bulk resource provisioning, production secret release, key-management policy mutation, deployment promotion, creation of high-privilege service accounts, raising billing limits, enabling paid services.¶
The final-effect boundary is the protected create, scale or enable operation in the control plane, not the earlier prompt or script. The pending operation identifies account, project, region, machine type, quantity, creation rate, expected recurring expenditure, service identity and current exposure limits. Per-request success does not imply unlimited cumulative permission: the sink or its Exposure Ledger counts existing reservations and committed usage across concurrent processes and rotated service accounts. If billing or activation occurs in a third-party system without adequate enforcement hooks, an external overlay offers only a weaker proxy-level control and MUST NOT claim non-bypassability without provider-side cooperation.¶
Candidate effects: deleting records, sending payments, changing identity policy, granting repository access, deploying production code, exporting customer data, invoking privileged security tooling.¶
Proposed placement: the application tool dispatcher for preliminary gating plus resource-specific protected executors for authoritative commit. An agent-protocol proxy or SDK hook is useful but alone may not cover direct API and internal service routes. Agent self-reported completion is not equivalent to destination-observed finality. A model is treated as a proposer: its output does not itself carry authority.¶
Candidate effects: management-plane configuration changes, policy activation, slice authority updates, trusted software package rollout, route propagation, sensitive subscriber-data release. Placement: management orchestration commit, domain controllers, slice-policy activation and protected administrative interfaces. Remote authorization MUST NOT be inserted into deadline-constrained radio loops (PHY, MAC or HARQ). Safe bounded rollout and rollback SHOULD be evaluated against the actual topology generation.¶
Candidate effects: transaction posting, payment capture, settlement authorization, beneficiary change, treasury transfer, exposure escalation, protected signing-key use. Placement: core-banking authorization and ledger posting, the payment gateway at the actual financial-effect boundary, HSM-mediated signing under bound context, and a protected exposure ledger. The design MUST distinguish request acceptance from actual settlement and MUST NOT assume rollback of external settlement.¶
Candidate effects: circuit switching, plant setting changes, disabling protective interlocks, setpoint writes, remote actuator commands, safety parameter updates. Placement: a protected operational-technology command relay, a safety-certified controller boundary, or an equivalent secure actuation reference monitor. See R19 to R21.¶
Candidate effects: release of movement or actuator authority, unsafe mission changes, protected navigation parameters, payload activation, high-consequence fleet commands. Placement: a protected vehicle or robot command guard with local bounded safety rules. Where remote latency is unacceptable, rely on locally enforceable preauthorization. A remote approval message does not verify the vehicle's actual safe state.¶
This section is COUNTERFACTUAL. It does not describe confirmed existing Fugaku components or defenses, and it does not establish that any proposed control would have prevented the actual incident.¶
Conclusion: a correctly deployed consequence-bound system might have contained or denied certain downstream actions after an initial foothold. It cannot be claimed from public evidence that it would have prevented the actual Fugaku breach.¶
An external attacker uses an autonomous multi-agent workflow to scan internet-facing software, generate exploit candidates, attempt access and pivot after success. The defender cannot require the attacking model to run a benign policy filter. The defender can intervene in layers:¶
Example 1 (role creation). An AI-driven exploit gains code execution in an exposed web service and calls an internal IAM API to grant itself a privileged role. With a protected IAM commit gate, the role change is an Actual Pending Operation checked against this service, this principal, the target role and delegation scope, and is denied if unauthorized however valid the API call looks. Limit: if the attacker controls the IAM enforcement root or a direct backdoor to the role store, the assumptions fail.¶
Example 2 (destructive script). A compromised automation agent submits a script deleting many protected research artifacts. The resource layer reconstructs the real target list, deletion type, ownership, retention rules and transitive effects. A general instruction such as "clean up old workspaces" cannot authorize deletion of all protected datasets. Limit: users may still intentionally delete approved items; the layer is not a universal truth oracle.¶
Example 3 (agent handoff). A monitoring agent asks a remediation agent to "restore stability" and the downstream agent interprets that as permission to change routing or firewall policy globally. The gate decides from the actual administrative update and delegated authority, not from the upstream agent's plausible language or signed message.¶
Each scenario lists the threat, protected effect, required gate, possible result and residual risk. All are counterfactual design analyses.¶
| Dimension | Conventional (typical) | Consequence-bound |
|---|---|---|
| Unit of decision | Session, request, identity, role | Reconstructed pending operation |
| Where enforced | Perimeter, identity provider, gateway | At or unavoidably upstream of the effect point |
| Trust in initiator | Initiator or its token carries authority | Initiator is an untrusted proposer |
| Approval binds to | Identity, role or a description | Canonical operation, resource generation, epoch, expiry |
| Timing | Login or request time; detection after | At commit, before irreversibility |
| Staleness | Token lifetime; revocation lag | Permit epoch compared at commit |
| Aggregate effects | Per-request quotas | Protected cumulative exposure ledger |
| Indirect effects | Usually the direct API only | Consequence closure |
| Bypass analysis | Rarely a formal precondition | Condition of the claim |
| Failure behavior | Fail-open, fail-closed or ad hoc | DENY, HOLD, ALLOW, SAFE FALLBACK, RECONCILE |
| Evidence | Logs and alerts after the fact | Gate first; receipts optional |
| Claim style | "Protected" in general terms | Conditional, per class, falsifiable |
Reference monitors, mandatory access control, transactional databases, admission controllers, privileged-access management, capability systems, two-person rules and modern zero-trust policy enforcement points each implement part of this logic. The claim is not that each part is new. For a chosen class of effects, the combination of actual-operation reconstruction, binding to resource version and epoch, independence from the proposer, cumulative exposure, transitive-effect coverage and exhaustive bypass analysis is an integration pattern whose value is testable and SHOULD be compared fairly against the best existing baseline. If an existing policy enforcement point already does all of this for a given effect class, the architecture is simply that enforcement point, well deployed.¶
TIER 4 CROSS-DOMAIN CONTINUITY
multiple participating sinks validate authority
across resources and organizations
TIER 3 ISOLATED / HARDWARE-ROOTED SINK
reference monitor or key-release path, measured
integrity, alternate-path control
TIER 2 AUTHORITATIVE APPLICATION SINK
privileged resource service enforces at commit
TIER 1 OUTER GATE
API gateway or proxy rejects some dangerous requests;
not necessarily non-bypassable
TIER 0 OBSERVE
shadow mode; map and reconstruct effects;
no prevention claim
It is neither necessary nor desirable to validate every token, instruction, floating-point operation, packet or sensor sample. Deployments SHOULD classify the few operation categories that cross meaningful consequence boundaries and leave the high-frequency path unchanged.¶
HIGH-FREQUENCY WORKLOAD PATH (unchanged)
AI inference | HPC compute | radio processing | sensor sampling
==============================================================>
no per-token, per-flop, per-packet or PHY-loop validation
LOW-FREQUENCY CONSEQUENCE PATH (gated)
privileged config, data release, role change, payment, quota,
scheduler mutation, actuator command
|
v
canonical pending act
|
v
LOCAL protected gate (hot path) ---> commit / deny
^
| protected cached policy + version / epoch checks
|
warm path: policy preparation, review, attestation
Hot path: a local, deterministic validation or permit-consumption check at the protected commit point, using precomputed, signed or protected cached inputs with bounded work. Warm path: policy authoring, stronger identity, human review, attestation negotiation, multi-party approval, evidence reconciliation and semantic analysis, before commit or outside strict deadlines. The final critical action MUST NOT proceed merely because validation has not finished.¶
T_total = T_existing + T_normalization + T_validation
+ T_commit_binding + T_coordination + T_optional_audit
¶
Only components on the synchronous protected path contribute to measured latency. No numeric overhead is asserted without benchmark evidence. A millisecond-level goal may be reasonable in some software control planes but is not a universal measured property, especially with remote consensus, humans, HSM operations or cross-datacenter calls.¶
| Class | Description | Gate behavior |
|---|---|---|
| I | Hard real-time physical safety | Deterministic bounded local checks; preserve certified interlocks |
| II | Soft real-time infrastructure control | Preapproved configuration corridors; local hot-path gates |
| III | Administrative configuration | Stronger validation, audit, possible human authorization |
| IV | Financial and data release | Sufficient verification before irreversible commit |
| V | Ordinary compute and inference | No per-token or per-flop check absent an external effect |
Optimization techniques include: native APIs and existing protected commit hooks; precomputed policy invalidated on version change; separation of the trusted evaluator from untrusted model and tool logic; small authenticated capabilities bound to precise operation fields; batching only when atomic batch semantics and cumulative policy are preserved; avoiding network round trips for local time-critical decisions; caching only under explicit freshness, revocation, expiry and replay controls; applying cumulative quotas at one consistent resource authority; admission control for high-risk actions; and testing queue growth, timeout behavior and worst-case latency, not only the mean.¶
Safety versus security: critical infrastructure cannot always fail closed in the everyday IT sense, since stopping a life-saving actuator or safety relay could itself be harmful. See R19 to R21. During a validator partition, options include denying unsafe administrative changes, holding nonessential operations, continuing previously authorized bounded work, entering a deterministic degraded mode, and allowing tightly defined safety-preserving local actions.¶
All experiments occur in isolated, consented laboratory environments. They do not reproduce the undisclosed Fugaku technique or attack live infrastructure.¶
Reporting rule: results SHOULD report hardware, topology, software versions, classification rules, trust assumptions, baseline controls, exact enforcement coverage, methodology, traffic, median and tail latencies, failure outcomes and confidence intervals. Blanket claims such as zero latency, 100 percent prevention or unhackable MUST NOT be made. A laboratory demonstration MUST be distinguished from deployment in HPC or national critical infrastructure.¶
This section is AI-generated. Readers MUST cross-check it against the original PCT filing (PCT/IB2026/055615) and each company's current documentation before drawing any conclusion. The alignment below is not an endorsement, validation or infringement statement, and implies no adoption, licence or partnership, nor that any company uses the described approach. Product descriptions reflect general public information and may be outdated or wrong.¶
For each company the text states where a Finality Sink would sit, what it would check, what it would reject and why that matters.¶
What the alignment shows: all four expose tools or control planes through which an authenticated, legitimate-looking call can cause a real consequence. For model vendors the natural insertion point is the tool-execution and API-credential layer outside the model; for cloud vendors it is the control-plane commit; for productivity suites it is role assignment and data release. Each vendor already ships identity, policy, quota, logging and approval features. Whether any of them already satisfies the coverage, binding and cumulative-exposure conditions for a given effect class is an empirical question this document does not answer.¶
This section is AI-generated, is not legal advice, and does not claim that following this document achieves compliance with any law. References to instruments SHOULD be verified against the official texts.¶
This entire document is about security properties. The following considerations apply specifically to deployments of the architecture.¶
Authorization records, Exposure Ledgers, audit logs and optional receipts can contain personal data (identities, dataset names, destinations, volumes). Deployments SHOULD minimize what is recorded, restrict access to these records, apply retention limits, and consider the obligations that apply to personal data processing, including breach-notification obligations when a release gate or ledger is itself compromised. Release gates are a privacy-protecting control when they limit what a stolen identity can disclose, but the classification rules that drive them can themselves reveal sensitive structure and MUST be protected.¶
This document has no IANA actions.¶
The underlying invention, architectural concepts and identified patent disclosures are human-originated by the author. This document is based on the Mothership international application PCT/IB2026/055615 [PCT-55615], filed 4 June 2026 and publicly disclosed 16 July 2026. The publication reference supplied by the author is WO 2026/150382 A2. Additional applications supplied by the author for cross-platform execution-finality architecture and independent-evaluator design are Indian application 202631127058 (25 October 2026) and Indian application 202631131650 (3 November 2026); these identifiers are provided for traceability and MUST be cross-checked against authoritative patent-office records. Detailed IETF IPR disclosures will be filed separately, and a reference implementation will be published on GitHub later.¶
To read the full PCT filing: search "Sangam Das" on WIPO PATENTSCOPE (https://patentscope.wipo.int/); search PCT/IB2026/055615 (pctib202655615); or read the PCT file directly at https://www.tdcommons.org/dpubs_series/12542/. This document is explanatory and is not a substitute for the claims, specification or prosecution file; the authoritative scope and priority of any invention reside in the original filed patent documents.¶
AI-assisted tools were used to create this document, including to summarize the filing and public incident reports and to draft the threat scenarios, comparisons, industry-relevance and regulatory-context material. It may contain errors, omissions, outdated details or unverified assumptions. Readers MUST cross-check all incident, product, regulatory and technical claims against the original, publicly available sources. Third-party names appear solely for public-source context; no deployment, adoption, collaboration, endorsement, licensing relationship or infringement is asserted or implied, and no efficacy, latency, performance, certification or safety guarantee is claimed without a reproducible implementation and independent testing.¶