SYSTEM NOMINAL / ----.--.-- --:--:-- UTC LOCAL / DOC SUBSYSTEM 07 / KAGENTI EDGE OK white paperprivacyterms
aperx memo SUBSYSTEM 07 · COMPUTE AGNOSTIC
date:
loading...
to:
validators, standards bodies, and IP owners
from:
autosymbotic division
subject:
the epistemic hyperledger
shell:
Kagenti Edge Protocol

proof that it was novel, and proof of who said so.

FIG.1 // live pseudo-hypergraph · contour stack = multiset multiplicity · node rings = self-lineage · orbiting beads = lineage units · click to inject claim σ_d · SYNC

AperX exists to uncover and verify the truth, because the Truth Matters. It is an optimistic verification platformRef: APX-SPEC-001 for machine learning provenance, now operating beneath the Kagenti Compute-Agnostic ProtocolRef: APX-SPEC-002. Heavy hypergraph mathematics runs off-chain under a deterministic, content-addressed specification; the chain holds only commitments, bonds, and fraud-proof gates, so verification scales with edge MLOps instead of stalling at a block limit.

Models, datasets, and claims are vertices; lineages, weight configurations, and derivations are directed hyperedgesRef: APX-SPEC-001. Novelty is a U-statisticRef: APX-SPEC-001 over combinations of prior art, queried by lifted inference. Unverified state carries observer-relativeRef: APX-SPEC-001 possibility bandsRef: APX-SPEC-001 until consensus collapses it into a committed edge. Kagenti-orchestrated agents reason in Wasm sandboxes and sign their conclusions with local SPIFFE identities before bulk-syncing to the ledger.

0
hypergraph classes
0
step validation lifecycle
0
mathematical foundations
0
honesty tiers
### ledger topologyfour hypergraph classesSPEC v1.0

ML provenance genuinely has four shapes. Flattening any into one linear chain destroys information consensus needs.

directed // multi-party attribution

One edge e = (T, H, ω) states "these checkpoints, datasets, and training runs, in these proportions, produced this model," or which prior works and authors produced a claim. A pairwise graph must decompose that into edges nobody asserted.

uniform // standardized evaluation

Every review edge binds exactly k evaluators, whether k benchmark harnesses scoring a checkpoint or k reviewers judging a paper. Uniformity makes edges exchangeable, the precondition for lifted inference.

pseudo // recursive derivation

Multiset edges keep repeated lineage visible instead of silently deduplicating it, so a model fine-tuned from its own ancestor, or a self-citation, is on the ledger and gets discounted rather than rewarded.

complete // saturation reference

σ_d = |E_d| / C(n_d, k) measures how much of a domain's combinatorial space is already explored. A novelty score of 0.6 means something different in a saturated architecture family than in an emerging one.

### the consensus mathematicsrecomputable by any partySPEC v1.0

Every quantity is recomputable from committed inputs. That is what makes the fraud proofs work.

1 · Novelty as a U-statistic

Hoeffding (1948), minimum-variance unbiased

A claim no single prior work anticipates but which a combination jointly anticipates is a property of subsets, so the estimator ranges over subsets. Unbiasedness is what makes it defensible in a dispute in a way a tuned heuristic is not.

U_n^(m) = C(n,m)⁻¹ · Σ_{i1<…

2 · Report a band, never a number

asymptotic normality

By Hoeffding's projection the estimator is asymptotically normal, so novelty is always an interval. A claim whose interval straddles the threshold is not borderline approved; it is epistemically unresolved.

√n ( U_n^(m) − θ_m ) → N(0, m²·ζ₁)

3 · Possibility, not probability

Zadeh possibility theory

An unverified claim in an emerging field has no reference class. Forcing a probability invents information. The gap Π - N is the epistemic ignorance, reported rather than minimized away.

Π(V) = sup π(x) · N(V) = 1 - Π(Vᶜ) · 0 ≤ N ≤ Π ≤ 1

4 · The collapse rule

necessity commits, possibility rejects

Commitment gates on necessity (conservative lower bound); rejection gates on possibility (optimistic upper bound). The residual region escalates to a human.

COLLAPSE ⟺ D(c) ≤ δ ∧ N* ≥ ν(σ_d,drift) ∧ Σ_agree w ≥ ⅔ Σ w · ν = ν₀ + a·σ_d - b·drift
on the RQM framing: observer-relative state is a structural analogy, not physicsRef: APX-SPEC-001. No Hilbert space, no Born rule. What is borrowed is one commitment: state is relative to the observer, and collapse establishes a shared relation. The math that runs is classical: possibility theory, U-statistics, weighted Byzantine agreement.
### collapse simulatornovelty, possibility, and the collapse ruleLIVE
APX // CONSENSUS ENGINESIMULATION
gatesν
bandAMBIGUOUS
U-statistic0.00
Π
N
decision
### mathematical foundationstwelve areas, three honesty tiersREV 2

Tier I · nowtier I

load-bearing today

Relational calculus gates logical consistency; probability bounds collusion risk and sets the challenge window; game theory and mechanism design align staking and slashing; information theory measures lineage as information transfer; optimization makes disputed replay bit-identical; statistics audit driftRef: APX-SPEC-003; graph theory is the provenance backbone.

relational calculusprobabilitygame theoryinformation theoryoptimizationstatisticsgraph theory

Tier II · scheduledtier II

specified, not yet built

Computability theory and formal methods draw the line between blocking gates that must provably halt and what cannot; the scheduled work is a mechanized proof that recomputation is a total deterministic function. Homology and topology fingerprint network structure so a verified model matches its claimed architecture.

computabilityformal methodshomologytopology

Tier III · frontiertier III

carried as optionality, risk stated

Stochastic PDEs would extend provenance to scientific-ML surrogates; algebraic geometry over parameter varieties is aspirational. The TCIU framework spans tiers: its time-complexity argument is load-bearing, while complex-time representation is a named research option nothing depends on.

stochastic PDEsGalois fieldsSpacekime / TCIU
the discipline this imposes: a document meant to establish mathematical credibility is destroyed faster by one indefensible claim than helped by twelve impressive ones. Every pillar states its concrete job and its honest limit.
### the kagenti compute-agnostic protocoledge-native orchestrationSPEC v2.0

The agents that feed AperX operate in dynamic, non-deterministic environments, often disconnected from cloud infrastructure. Kagenti is a universal, compute-agnostic orchestration protocol capable of running in Wasm sandboxes, on edge devices, and in disconnected environments. It handles application-layer mTLS, agent lifecycle state machines, and cryptographic claim signing independent of the underlying substrate.

The Symbiotic Architectureboundary rule

Kagenti owns the question. AperX owns the answer.

The architecture resolves a foundational tension: autonomous agents must reason in heuristic, non-deterministic ways, yet the claims they produce must live on a deterministic ledger. Kagenti and AperX meet at a sharp boundary.

┌── KAGENTI COMPUTE-AGNOSTIC PROTOCOL (Wasm / Edge / Cloud) ────┐ │ Swarm Manager · Lifecycle Director · App-Layer mTLS · SPIRE │ │ Asynchronous Cryptographic Buffer (SQLite/Wasm Local Cache) │ └─────────────────────────────┬───────────────────────────────────┘SVID-signed claim + deterministic bulk-sync┌── APERX EPISTEMIC LEDGER (Deterministic Cloud Core) ────────────┐ │ 12-step validation · U-statistic novelty · Π/N bands · collapse │ └─────────────────────────────────────────────────────────────────┘

The ledger does not care how the claim was produced or where the agent executed. It only cares that the math recomputes. A claim generated by a stochastic swarm in a Wasm sandbox or a heuristic search on a disconnected edge device is treated identically once it crosses the boundary.

KAGENTI SUBSYSTEM STATE MACHINEINTERACTIVE
⚙️
Swarm Manager
Decomposing
🔄
Lifecycle Director
Scaling
🔒
App-Layer mTLS
Encrypting
🛡️
SPIRE Edge Agent
Issuing SVID
✍️
Claim Signer
Signing
SVID TO APERX PRINCIPAL MAPPINGLIVE COMPUTATION
SHA-256(SVID || contract_id || epoch)
Computing...

Physical Node Compromise ProtectionsSECURITY

cryptographic shredding and ephemeral key derivation

If an edge node is physically compromised, the local buffer must not leak sensitive claim data or identity credentials. The Kagenti protocol enforces cryptographic shredding of the local SQLite/Wasm buffer.

1. Ephemeral Key Derivation: Local buffer encryption keys are derived from the active SVID session and a volatile hardware-backed nonce.
2. Zeroize on Tamper: Upon detection of physical tamper or unauthorized memory access, the volatile nonce is immediately zeroized.
3. Cryptographic Shredding: Without the nonce, the derived encryption key is unrecoverable, instantly rendering the entire local append-only log cryptographically shredded and indistinguishable from random noise.
4. Revocation: The compromised SVID is immediately broadcast to the SPIRE server for revocation, invalidating any future claims from that principal.

Disconnected Edge Protocol

asynchronous cryptographic buffer

Agents operating in remote, subterranean, or contested environments cannot rely on continuous connectivity to the AperX cloud ledger. The Disconnected Edge Protocol ensures that heuristic reasoning and claim generation continue uninterrupted, with cryptographic guarantees preserved for eventual synchronization.

1. Local Execution: Agent runs heuristic tasks in Wasm sandbox.
2. Local SVID Signing: Claims signed using local SPIFFE SVID.
3. Verifiable Local Log: Claims appended to SQLite/Wasm append-only log.
4. Bulk-Sync: Upon network restoration, deterministic batch transmission to AperX Gateway.

The local verifiable log forms a hash chain. Each entry contains the claim content hash, the SVID signature, a local monotonic timestamp, and the previous entry hash.

### node validation lifecyclesubmission to permanent encodingSPEC v1.0

Step 08 is the architectural heart: a protocol forced to produce a verdict on every claim produces bad verdicts on hard claims. This one may say "unresolved" and hand the claim to a human.

  1. Ingest. Receive a content-addressed claim from a Kagenti-orchestrated workload (cloud or edge buffer); verify the SPIFFE SVID; map the SVID to an AperX Principal via SHA-256(SVID || contract_id || epoch); bind identity and priority under commit-reveal.
  2. Gate. Export control (ITAR / EAR), patent embargo, PHI, residency.
  3. Formalize. Extract atoms into stratified Datalog; verify KB ∪ Φ_c ⊭ ⊥.
  4. Featurize. Map to directed, uniform, and pseudo hyperedges; compute lineage multiplicities.
  5. Partition. Build the exchangeability partition; publish partitionRoot.
  6. Estimate. Draw the incomplete design at committed seed; compute Û_B and total variance.
  7. Observe. Each validator posts a bonded, observer-relative verdict.
  8. Collapse or suspend. Evaluate the collapse rule; on failure suspend to a bonded human privileged observer.
  9. Commit. Write the hyperedge with attribution signatures; seal; open the challenge window.
  10. Challenge. Any party recomputes deterministically; divergence is a fraud proof; slash.
  11. Anchor. Finalize; the claim becomes prior art for every subsequent estimate.
  12. Supersede. Later refutation appends supersedes(e_new, e_old). Nothing is ever deleted.
why the heavy math is off-chain: you cannot compute a lifted U-statistic over millions of prior-art tuples inside a block gas limit or a Wasm linear memory constraint. AperX is an optimistic verification system: math runs off-chain under a pinned specification with fixed-point arithmetic; the chain holds commitments, bonds, verdicts, and the challenge window. Kagenti handles the orchestration of the workloads that submit to this machinery.
### research & artifactspre-print gateway · internal peer reviewNDA GATED

UltraMassive pre-print publications, internal critique threads, and working annexes. Access requires execution of the Symbiotic Architecture Two-Way NDA. Production artifacts and ratified discussions are cryptographically synced to the external artifact subdomain.

artifact sync target: artifacts.ultramassiveml.io · status: ACTIVE

Pre-Print Access Restricted

Execute the Symbiotic Architecture Two-Way NDA to Authenticate. All access events are cryptographically logged as directed hyperedges on the APX-HL-NDA ledger. Total epistemic anonymity is enforced: all authors and reviewers are identified strictly by cryptographic SVID principals.

### ProtoLab gatewaymutual NDA, then the testnetLIVE

ProtoLab hosts the pre-release testnet, the reference validator, and unpublished annexes. Access is a mutual, two-way NDA: you disclose IP-corpus context, we disclose protocol internals. The agreement is counsel-reviewed (revision UM-MNDA-2026.07-v1.0) and produces a genuine SHA-256 execution receipt.

GENERATING...
execute mutual NDA
aperx.ultramassiveml.io/protolab-nda.html
GENERATING...
aperx console
AperX control-plane console
execute mutual NDA → unlock testnet Kagenti × AperX repo → read white paper APX-WP-001 →
QR codes generated deterministically in your browser using a self-contained ISO/IEC 18004 encoder. No external libraries, no network calls. Scan with any phone; they resolve to the internal NDA execution endpoint and the AperX console.
↑↓ navigate↵ openesc close