Attestor is designed to participate in the Satoshium Suite by referencing and exchanging governed information while preserving the provenance, scope, meaning, identifiers, status, relationships, and authority of the objects involved.
Interoperability allows information to participate in an Attestor evaluation without collapsing institutional boundaries or converting a referenced object into an Attestor-owned object.
Attestor may reference authoritative Atlas intelligence when relevant to an evaluation. Atlas retains authority over its intelligence and structural record; Attestor governs only its use within Attestor evaluation.
Suite RelationshipAttestor may participate in workflows defined or orchestrated through Navigator. Navigator retains responsibility for workflow definition and orchestration, while Attestor retains responsibility for its evaluation and Trust Statement.
Suite RelationshipAttestor may reference a Certifier Certification Package as a governed source input. The first production operation did so with SC-CERT-2026-0001. Its certification, identifier, state, and governing meaning remained under Certifier authority while Attestor governed its own Eligibility, Attestation, Evaluation, and Trust Statement.
Suite RelationshipAttestor may reference a Satoshium Registry record and its governed relationships. Registry retains authority over the registered record, identifier, status, and lifecycle.
Suite RelationshipAttestor may reference a Chronicle Entry for historical, event, or provenance context. Chronicle retains authority over the preserved entry and its historical record.
Suite RelationshipAttestor may reference an Anchor Integrity Reference when integrity context is relevant. Anchor retains authority over the Integrity Reference and its governing integrity model.
Suite RelationshipAttestor may reference Beacon Discovery Signals or Discovery Metadata when discovery context is relevant. Beacon retains authority over its canonical discovery objects and their lifecycle.
Suite RelationshipAttestor may accept governed information from external platforms, protocols, repositories, or authorities when the applicable Eligibility, Provenance, Validation, Scope, relevant-state, and Authority requirements can be satisfied under established Attestor architecture.
Governed RelationshipInteroperability is not satisfied merely by transferring a value or identifier. Attestor should preserve enough information to understand what the referenced object is, where it came from, how it relates to the evaluation, and what authority and limitations remain attached to it.
These reference-context requirements are established by Attestor's Reference Profile, Authority, Provenance, Relationships, Eligibility, and state architecture. The first production operation exercised structured governed references in canonical ATT/TRST representations and demonstrated that this context can be preserved across institutional boundaries. Future transport-specific or external exchange formats may continue to evolve without reopening the established institutional requirements.
Where a governed Suite object already exists, Attestor should reference that object rather than silently recreate it as an Attestor record. Attestor may preserve the information necessary to evaluate and trace the reference, but the originating object remains authoritative in its source institution.
Referenced objects may later change status, version, publication state, or other governed properties. Attestor preserves the relevant source state used during Evaluation and distinguishes it from later source changes. A material source-state change may trigger Review, but Review does not predetermine correction, withdrawal, supersession, or creation of a new canonical object.
Attestor does not perform the source institution's lifecycle operation. It responds within its own authority to the consequences of that change.
The first controlled production operation demonstrated interoperability across multiple Suite institutions while preserving canonical identity, provenance, relationship meaning, relevant state, and institutional authority.
The production case therefore establishes a concrete Suite interoperability baseline. It does not imply that every future external protocol, representation, profile, or integration is automatically interoperable.
Attestor participates in a Suite of institutions with distinct canonical responsibilities:
Atlas → Authoritative Intelligence
Navigator → Workflow Definition / Orchestration
Certifier → Certification Package
Registry → Satoshium Registry Record
Chronicle → Chronicle Entry
Anchor → Integrity Reference
Beacon → Discovery Signal / Discovery Metadata
Attestor → Trust Statement
Interoperability is established as both institutional architecture and demonstrated production capability. Required reference context is governed through the Reference Profile and related Authority, Provenance, Eligibility, Relationships, state, Validation, and Conformance architecture; the first production operation demonstrated that those boundaries can survive real cross-Suite use.
Concrete APIs, transports, external adapters, authentication mechanisms, and source-change notification mechanisms remain technology-specific implementation choices unless separately adopted. Their continued openness does not make the institutional interoperability model incomplete.