Primitives and shared objects.

Cryptographic primitives

STARKs

Target prover family: transparent hash-based (STARK-class); current harness: classical simulator + mock fold. For institutional archives that must remain checkable for a decade or more, the proof family is a genesis choice, not an afterthought.

Arc and recursive heterogeneous aggregation

We are prototyping the Arc accumulation scheme ("Arc: Accumulation for Reed–Solomon Codes", Bünz, Mishra, Nguyen, Wang, 2024) for recursive heterogeneous circuit proof aggregation: incrementally verifiable computation (IVC) across circuits that are not identical. Continuous attestation and multi-policy products need exactly this: fold histories and compose proofs without rebuilding the world each epoch.

Target shape: verifier work stays flat analytically/definitionally as history grows (not measured on folded histories); applications compose without forcing every vertical onto one monolithic circuit.

Interoperability standards we are shaping

Drawn from continuous-attestation and compliance work we are prototyping:

• Classified obligations state — liability and asset vectors with horizons, mobility, and entitlement maps; the object continuous PoR actually proves.
• Coverage predicate & ladder — executable classical evaluators and harnesses so "assets cover liabilities" means a ladder under registered policy, not a scalar photograph.
• Regime profiles & tolerances — versioned profiles for Swiss safeguarding, MiCAR, and ADGM-class client-asset rules, with breach taxonomies and tolerance hooks inside the attested object.
• Audience derivation — one proven state; supervisor, bank, and client each verify only their entitled predicate, with sequencing that respects legal notification order.
• Policy-as-code surface — TypeScript policies with custody labels as proof; formal specs of ERC-3643-class transfer rules support differential testing of existing gates.
• Assurance-criteria track — objects meant for a standards body and assurance partners, not locked inside a single vendor's PDF.

Why standards, not just product

Privacy math without shared criteria does not deploy. Shared criteria without portable proofs do not travel across borders. We publish vocabulary, tolerances, and proof composition as open objects; the applications that consume them are the business.