← All projects

JOINT AD × ORP RESEARCH

RESEARCH

Proposed security research · working names

Owner control over identity and disclosure.

AIUS is a proposed security research program connecting Another Dimension's identity and disclosure questions with OpenRoot's authenticated transport research. AIUS is a working umbrella name for this joint research into owner-controlled disclosure.

CONCEPT MOTIF — NOT A RUNNING SYSTEM

35 / 7

RESEARCH TARGET

WHY

Carrying is not permission to read.

Its starting principle is that carrying protected information and having permission to read it are different authorities. Recipient, purpose, fields and scope matter: human-readable names are presentation, and verified recipients with bounded grants are the research target.

SYSTEM

HEPTAGRAM 35/7 — a research target.

The current target requires all 35 logical fragments to reconstruct an encrypted object, followed by seven required authorizations before permitted information is disclosed to a verified recipient. The cryptographic construction, independence of those authorizations, availability and recovery rules still require research and validation.

  1. 01All 35 logical fragments
  2. 02Ciphertext reconstructed — no plaintext at this step
  3. 03All seven required authorizations — cryptographic enforcement is a research target
  4. 04Permitted fields disclosed to a verified recipient

RELATED RESEARCH

Related research directions — working names.

METEOR SCATTER
Dynamic placement and safe relocation of protected fragments. Moving a fragment does not erase a hostile copy or prove anonymity; safe replication, locator privacy and loss recovery remain open.
ORBIT GATE ∞ / INFINITY RATCHET
Authenticated counterpart discovery, fresh session authority and replay resistance. These are working concepts: no ratchet, crash-safe replay protection or permanent revocation has been implemented, and the rotating gate is a metaphor, not a new physical effect or an unlimited supply of network ports.
CANENS
Consent-based research into voice as a supplementary signal, including recorded and synthetic speech threats. Voice is not unique and can be recorded or synthesized, so it is never treated as a high-assurance access secret; no evaluation results exist yet.
AIUS STARWATCH
Privacy-conscious incident evidence, review, warnings and containment. A signed assertion is not proof of a real-world identity or location, and the evidence does not guarantee identifying a person behind a VPN or Tor path.
Identity and selective disclosure
Separating display names from cryptographic subjects, purpose-specific identifiers, and disclosure of only the claims a recipient is permitted to receive. Payment or confidential routing by display name alone is out of scope.

RECORD

What has been recorded.

Research brief

Result
A research brief recorded the owner's target of 35 logical fragments and seven required authorizations, and split responsibilities between Another Dimension and OpenRoot.
Scope
A research brief and a responsibility split only
Recorded by · version
2026-10-16
Source
Private technical record (reviewed for the website on 2026-10-17)
Limits
  • No feasibility analysis, cryptographic construction or prototype has been completed.
  • No independent security review of AIUS has taken place.
  • The seven listed roles are not yet seven independent cryptographic keys.
  • No naming or trademark clearance is asserted for AIUS or its working names.

PROOF / STATUS

Current status.

A research brief and the AD/ORP responsibility split have been prepared. Feasibility analysis, cryptographic enforcement, recovery design and prototype qualification remain pending. AIUS has not been built or independently validated; read this page as a research proposal. Voice alone is not a high-assurance access secret, and incident evidence does not guarantee identification of a real person behind a network path.

NEXT

What happens next.

Any future feasibility or prototype result will be shown with its scope and limits. AIUS is a research project, not the company's security contact: the company's own security responsibilities and contact are described on the Security page in the site footer.