DrKu.io® / EVIDENCE CENTER

Don’t Trust the Claim.
Inspect the Evidence.

Execution trust should be supported by inspectable evidence, explicit boundaries and versioned technical records.

This center consolidates the public status, published architecture, demonstrator scope and failure boundaries behind DrKu.io execution-trust technology — with what is and is not claimed kept explicit at all times.

Begin inspecting
01 / OFFICIAL IP STATUSHKIPD REGISTRY

Official IP Status

The granted Hong Kong short-term patent status, identifiers and publication date for the S2F / EAO / VEU family, as verified against official records. This page does not host or imply a substitute for the official register.

S2F / EAO / VEUGRANTED / PUBLISHED · PATENT IN FORCE

FAIL-CLOSED EXECUTION METHOD, SYSTEM, STORAGE MEDIUM AND COMMUNICATION PROTOCOL FOR AN AUTOMATED SYSTEM

Application No.
32025115222.1
Publication No.
30139064 A
Patent No.
HK30139064
Granted / Published
16 October 2026
Current Registry Status
Patent in Force
Proprietor
DrKu Technology Limited
Last Verified
16 October 2026

Status is reflected as last verified against official HKIPD records. The official register is the sole authoritative source; always confirm current status directly via the HKIPD Online Search System.

Official Publication Notices — October 2026

These four complementary applications have received official Notices of Publication and remain pending until publication and grant are completed and confirmed in the official register.

02 / PUBLISHED CLAIM ARCHITECTURENON-CLAIM-CONSTRUCTION SUMMARY

Published Claim Architecture

A public, non-claim-construction technical summary of the granted S2F / EAO / VEU family. It describes what the family addresses in plain English; it is not a claim construction and does not define patent scope.

NON-CLAIM-CONSTRUCTION SUMMARY
S2F / EAO / VEUFail-Closed Execution

Addresses the final execution boundary by requiring explicit execution authorization to be independently verified before a consequential effect is allowed to occur.

If valid authorization cannot be established or verified, execution is denied.

EXECUTION BOUNDARY LAYEREXECUTION BOUNDARY
Check architectural overlap (Relevance Navigator)

This summary is a public description only. It is not a claim construction, does not establish patent scope or infringement, and does not represent that every claim or embodiment of the family is implemented in any demonstrator.

03 / NET0 VALIDATIONBOUNDED REFERENCE DEMONSTRATOR

NET0 Validation

The public bounded scope of the NET0.hk integrated five-IP reference demonstrator — what was tested, what passed, and what was intentionally not claimed.

WHAT WAS TESTED
PUBLIC DEMONSTRATORv0.1.1 — simulation-oriented
EXTERNAL-NODE TRACKv0.2.0 — NET0-NODE/1
EXTERNAL COMPUTEJetson Orin NX
WHAT PASSED
  • One controlled, signed, task-scoped safe-software-effect round trip.
  • Independent endpoint verification of the fail-closed execution boundary (positive path).
INTENTIONALLY NOT CLAIMED
  • Physical actuation validation.
  • Implementation of every patent claim.
  • Production readiness, safety certification or regulatory approval.
  • Universal applicability across all environments.
Explore NET0.hk
04 / FINANCIAL EXECUTION CONTEXTe-rmb.com v0.1.5 SIMULATION

Financial Execution Context

e-rmb.com v0.1.5 applies SPIP, ACAVP, TPOL and S2F / EAO / VEU within a bounded financial execution-context simulation. It explores how a digital decision could otherwise lead to a financial effect — deliberately separated from real financial infrastructure.

SELECTED / APPLICABLE CONTROL SURFACESCURRENT e-rmb.com v0.1.5 SIMULATION
SPIPACAVPTPOLS2F / EAO / VEU

e-rmb.com v0.1.5 applies SPIP, ACAVP, TPOL and S2F / EAO / VEU within a bounded financial execution-context simulation.

PACT is part of the wider DrKu.io portfolio but is not exercised here as a physical-feasibility control.

This mapping describes the bounded demonstrator scope. It does not establish implementation or validation of every patent claim.

Explore e-rmb.com
CURRENT PUBLIC BOUNDARY
Modesimulation only
Real moneyno
Official e-CNY connectionno
FPS connectionno
Wallet / accountno
Custody / depositsno
Clearing / settlementno
Regulated financial serviceno
CURRENT ACCEPTANCE BASELINE
SCENARIOS11 deterministic simulation scenarios
EXPECTED OUTCOMES11 / 11 expected outcomes
EXERCISED GOVERNANCE OUTCOMES
PROCEEDHOLDBLOCK

REVIEW remains part of the governance decision vocabulary but is not exercised by the current 11-scenario baseline.

SIMULATION ONLY
REAL MONEY — NOOFFICIAL e-CNY CONNECTION — NOFPS CONNECTION — NO

This is DrKu-controlled demonstrator acceptance evidence. It is not independent certification, production assurance, real-money validation, regulatory approval or proof that every patent claim is implemented.

The demonstrator does not move real money and has no official e-CNY or FPS connection. It does not provide wallet, banking, payment, exchange, remittance, custody, clearing, settlement or regulated financial services.

05 / FAILURE BOUNDARIESWHY EXECUTION MUST STOP

Failure Boundaries

Nine failure modes the execution-trust architecture is designed to address. Each is mapped to the relevant control surface(s) and its current public evidence status. Not all are validated — only those with actual public evidence are marked as such.

Stale Input

ARCHITECTURAL INTENT

Is the live evidence still fresh enough to act on?

Data that was precise when captured may have degraded, reordered or gone stale before it influences execution.

CONTROL SURFACE(S)
SPIP
EVIDENCE

Architectural intent — not separately validated in public demonstrators.

Replay

BOUNDED SIMULATION EVIDENCE

Could a valid earlier message be replayed as if it were new?

A previously valid input or authorization must not be accepted as if it were freshly issued at commitment.

CONTROL SURFACE(S)
SPIPS2F / EAO / VEU
EVIDENCE

e-rmb.com v0.1.5 exercises a replay_duplicate scenario and returns BLOCK / NOT_EXECUTED in the current deterministic simulation baseline. This is bounded simulation evidence. It does not represent validation of every replay mode, production environment or patent claim.

Wrong Context

ARCHITECTURAL INTENT

Does the execution context still match the one the decision was made under?

Authorization valid under one context may be invalid under another; the current context must be checked at commitment.

CONTROL SURFACE(S)
TPOLS2F / EAO / VEU
EVIDENCE

Architectural intent — not separately validated in public demonstrators.

Revoked Identity

ARCHITECTURAL INTENT

Is the relied-upon device, component or identity still valid right now?

A previously valid identity may have been revoked; lifecycle and revocation status must be checked before reliance.

CONTROL SURFACE(S)
ACAVP
EVIDENCE

Architectural intent — not separately validated in public demonstrators.

Physical Infeasibility

ARCHITECTURAL INTENT

Can the proposed physical action actually proceed under current conditions?

An action feasible under nominal assumptions may be infeasible given live tolerances, limits or operating conditions.

CONTROL SURFACE(S)
PACT
EVIDENCE

Architectural intent — physical actuation not validated by NET0-NODE/1.

Policy Mismatch

BOUNDED SIMULATION EVIDENCE

Do the verified facts satisfy the applicable execution policy?

Even with valid evidence and identity, the verified facts must satisfy the explicit, versioned policy in force.

CONTROL SURFACE(S)
TPOL
EVIDENCE

e-rmb.com v0.1.5 exercises policy-failure conditions including condition_unsatisfied and spending_limit_violation. The current deterministic simulation baseline returns BLOCK / NOT_EXECUTED for those scenarios. This is bounded simulation evidence only.

Expired Authority

BOUNDED SIMULATION EVIDENCE

Is this exact effect still authorized at commitment?

Authorization that was valid earlier may have expired; validity must be re-established at the moment of effect.

CONTROL SURFACE(S)
S2F / EAO / VEU
EVIDENCE

e-rmb.com v0.1.5 exercises expired_mandate and returns BLOCK / NOT_EXECUTED in the current deterministic simulation baseline. NET0-NODE/1 separately validates a positive-path, task-scoped execution-boundary round trip. Neither result is production certification or proof that every expiry / continuity claim is implemented.

Explore NET0.hk

Target Mismatch

BOUNDED SIMULATION EVIDENCE

Is the exact target at commitment the one that was authorized?

The exact target of the effect must be independently verified as the authorized target before the effect is allowed.

CONTROL SURFACE(S)
S2F / EAO / VEU
EVIDENCE

e-rmb.com v0.1.5 exercises payee_mismatch and returns BLOCK / NOT_EXECUTED in the current deterministic simulation baseline. NET0-NODE/1 separately validates positive-path target-bound execution behaviour. These are bounded demonstrator results and do not define patent scope.

Explore NET0.hk

Bypass Attempt

RELATED PUBLIC EVIDENCE — POSITIVE PATH ONLY

Can the execution boundary be circumvented entirely?

The fail-closed boundary must hold even under bypass attempts; when valid authorization cannot be established, execution is denied.

CONTROL SURFACE(S)
S2F / EAO / VEU
EVIDENCE

NET0-NODE/1 v0.2.0 validated one controlled, signed, task-scoped safe-software-effect round trip (positive path). Failure-injection results are not separately published.

The cited public record validates a related execution-boundary / positive-path behaviour. A separately published failure-injection result for this specific condition is not currently claimed.

Explore NET0.hk

These cards describe architectural intent and, where stated, bounded public evidence. They do not constitute certification, production assurance, or a representation that every failure mode has been independently validated. A demonstrated behaviour should not be read as representing every claim or embodiment of a patent family.

Try the Effect Journey simulator
06 / CLAIM BOUNDARYPERMANENT

Claim Boundary

What this center supports, and what it does not claim — kept side by side so the boundary is always explicit.

WHAT IS SUPPORTED
  • Official patent status, as verified against HKIPD records.
  • Bounded technical behaviours actually tested in public demonstrators.
  • Published claim architecture (non-claim-construction summary).
  • Current demonstrator scope and validation boundaries.
WHAT IS NOT CLAIMED
  • Universal safety or universal applicability.
  • Production readiness unless separately evidenced.
  • Regulatory certification or safety certification.
  • Patent infringement or freedom to operate.
  • Implementation of every patent claim in any demonstrator.
  • Semantic truth from cryptographic integrity alone.