TRUST INFRASTRUCTURE
Altmur — Trust made verifiable. Complexity made invisible.
Altmur is building the trust automation plane for independently governed systems and autonomous agents. It brings together cryptographic identity evidence, verifiable credentials, issuer trust and lifecycle automation to make trustworthy digital participation practical without centralized control.
Certificates, credentials, keys, signatures, passports and attestations are the mechanisms through which Altmur delivers this capability. They are not its ultimate purpose. The purpose is to make trust a dependable, reusable foundation for digital interaction.
“Trust should be built into participation, not rebuilt by every participant.”
THE PROBLEM
Trust remains fragmented, difficult and expensive to operate.
Certificate authorities, identity providers, workload identity frameworks, credential issuers, key management and authorization systems each address a legitimate problem. Bringing them together across organizational boundaries remains difficult, and autonomous agents add new questions: which agent is acting, who is accountable for it, and whether its claimed delegation can be verified.
A regional grain elevator joining a federated agricultural network should not need to run a certificate authority, manage signing keys and master every credential protocol before it can participate. These are problems of trust establishment, continuity, provenance and lifecycle management.
THE PRODUCT MISSION
Make verifiable trust accessible, automated and interoperable.
Altmur pursues this mission through four complementary responsibilities.
- 01
Establish
Support the controlled establishment of cryptographic identities, issuer relationships and trust material, relying on appropriately authorized issuers, registrars and attestors.
- 02
Verify
Enable relying parties to evaluate the authenticity, integrity, provenance, validity and current status of certificates and credentials.
- 03
Maintain
Automate renewal, rotation, suspension, revocation and recovery so lifecycle operations are dependable rather than manual.
- 04
Simplify
Hide unnecessary complexity behind coherent APIs, declarative profiles and operational automation—without weakening security guarantees.
A CREDENTIAL IS NOT AN IDENTITY
One persistent identity. Zero or more passports. Zero or more credentials.
An RSN ID identifies a subject. A passport represents a participation context. Credentials provide independently issued assertions relevant to that context, each with its own issuer, validity period, status and lifecycle. A subject’s persistent identity must survive the expiration or replacement of its credentials.
Persistent identity is managed through OpenRSN; Altmur provides cryptographic issuance, presentation support, verification and lifecycle services for these trust instruments. Altmur is not a global identity authority, a universal authorization engine, an agent runtime, or a replacement for SPIFFE, SPIRE, OAuth or established credential standards.
Altmur establishes verifiable trust evidence. The receiving authority decides what that evidence permits.
VERIFIED ENGINEERING PROGRESS
Evidence, with its boundaries intact.
- 01Research thesisA clear, falsifiable proposition
- 02Engineering evidenceDemonstrated behavior in defined tests
- 03Operating evidencePerformance under field conditions
- 04Independent assuranceExternal scrutiny and verified outcomes
WORKED EXAMPLE · ALTMUR Altmur, our trust infrastructure venture, is the reference system. Altible models its components, capabilities, dependencies and prerequisites, while Altmur remains the authority for its own declarations, tests and fixtures. Every figure below is Altmur’s, and all of it sits at level 02: engineering evidence.
27 / 27
Certificate regression checks
Altmur v2.2.0 development verification
16 / 16
Credential demonstration checks
Altmur validated development scenarios
518
Machine-modeled entities
Altible’s model of Altmur, zero generation warnings
Altmur v2.2.0 Phase 1 development checks and Altible’s model of Altmur, November 2026. These results stop at engineering evidence: they do not establish production readiness, hardware-backed key custody, operational federation, or independent assurance. A passing check is not permission to deploy.
WHERE THE WORK STANDS
Experimental · development verification gates passed
Built foundations. More assurance still to earn.
Altmur has passed specified development verification gates, while production key custody, operational recovery, and independent security assessment remain distinct obligations. Production use as an OpenRSN federation trust anchor has not yet been approved.
The next proof point: secure key-provider integration, standards-aligned issuer verification, SPIFFE/SPIRE interoperability, and demonstrated cross-domain trust scenarios with explicit admission and authorization boundaries.
Research, experimental and applied initiatives are presented according to their intended role, not as claims of general availability.
