Common questions about Satoshium Attestor, Attestations, Evidence, Trust Statements, authority boundaries, corrections, interoperability, and Attestor's established operational state.
Attestor is the Satoshium Suite institution responsible for producing governed, attributable, bounded Trust Statements through Rule-Constrained Evaluation of Attestations against eligible governed inputs. It preserves the scope, provenance, limitations, relationships, and authority boundaries necessary to make those conclusions reviewable.
A Trust Statement is Attestor's canonical output: a governed, attributable, bounded conclusion produced through Rule-Constrained Evaluation of an Attestation against eligible governed inputs. It should preserve the basis and limits of its conclusion without replacing the authority of the objects it references.
No. Attestor does not establish universal truth. It produces a bounded conclusion within a defined scope under Attestor rules. The conclusion should say no more than its eligible inputs, evidence, provenance, status, limitations, and applicable evaluation support.
An Attestation is a governed, attributable, bounded assertion about a subject, record, relationship, condition, event, or other trust-relevant matter. An Attestation may participate in evaluation, but it is not itself the final Trust Statement.
An Attestation expresses an assertion. A Trust Statement expresses Attestor's conclusion after applicable rule-constrained evaluation. The two are related but distinct Attestor objects.
Evidence provides supporting material or authoritative references used to evaluate an Attestation and support a Trust Statement. Evidence informs a conclusion; it does not become proof merely because Attestor references it. Its provenance, relevance, scope, status, limitations, and source authority should remain visible where applicable.
“Trust signal” remains descriptive language for trust-relevant evaluation context. It is not presently established as a separate canonical Attestor object, controlled record type, reputation score, or automatic trust indicator. It must not be confused with Beacon's canonical Discovery Signals.
Certifier owns the Certification Package and certification process. Attestor may reference a Certification Package as an authoritative input when relevant and eligible, but it does not certify or recertify the subject. Certifier retains authority over the certification; Attestor retains authority over its own Trust Statement.
Anchor owns the Integrity Reference. Attestor may reference an Anchor Integrity Reference when integrity context is relevant to an evaluation, but Attestor does not establish or redefine Anchor's integrity determination.
Beacon owns Discovery Signals and Discovery Metadata. Attestor may reference those objects when discovery context is relevant, but it does not create or redefine Beacon's canonical discovery architecture.
Yes, when they are relevant and eligible. Registry retains authority over Satoshium Registry records, and Chronicle retains authority over Chronicle Entries. Attestor may use those objects as governed references without assuming their institutional authority.
It means that Attestor may rely upon or reference an object governed elsewhere without becoming the authority for that object. The source institution remains authoritative for its canonical object; Attestor is responsible for how the eligible reference participates in its own evaluation and Trust Statement.
Yes. Attestor governs changes affecting its own Attestations and Trust Statements through Correction, Lifecycle, and Versioning architecture while preserving prior state, provenance, and historical traceability. Review and correction are activities, not lifecycle states. A materially changed assertion or conclusion requires a new canonical object.
No. Reputation is not an Attestor canonical object, and Attestor does not establish a generic reputation framework, reputation score, confidence percentage, or universal trust score. Its canonical output is the bounded Trust Statement.
No. Canonical creation does not automatically authorize publication. Attestor separately governs Publication State as unpublished or published. Publication requires a governed publication decision; technical accessibility alone does not establish Published state.
Yes. Attestor completed its first controlled production operation and established Operational Proof. The operation produced ATT-2026-0001 and TRST-2026-0001, both now Active · Published · V1.0. Their final published-state representations passed Validator v0.5, governed Review completed 25 / 25 satisfied requirements, both production objects received conformant Conformance outcomes, and the post-operation institutional review concluded 11 PASS / 0 FAIL / 0 UNRESOLVED.
Future work is continuing governance, not a prerequisite to operational status. Each future Attestation, Evaluation, Trust Statement, correction, source class, specialized profile, or implementation path remains separately governed and must satisfy its own applicable requirements. The first production operation does not mean every Attestation Type, Evaluation Outcome, lifecycle value, relationship value, external-source path, or specialized profile has been production-tested.
Six eligible Suite-source inputs were used to form ATT-2026-0001, a verification-related Attestation concerning SC-CERT-2026-0001. Rule-Constrained Evaluation produced the outcome supported and formed the bounded canonical Trust Statement TRST-2026-0001. The operation then completed Validation, governed Review, Conformance, lifecycle activation, Publication, final-state revalidation, production-evidence preservation, post-operation institutional review, and Operational Proof.
Canonical Attestations use ATT-YYYY-NNNN. Canonical Trust Statements use TRST-YYYY-NNNN. Canonical identity answers which governed object; version identity answers which governed state of that object.
The adopted Evaluation Outcomes are supported, partially-supported, not-supported, contradicted, and indeterminate. An Evaluation Outcome is not itself the bounded conclusion or the identity of a Trust Statement.
The adopted Lifecycle States are draft, active, superseded, withdrawn, and retired. Review and correction are governed activities rather than lifecycle states.
No. Evaluation determines a substantive Evaluation Outcome and supports formation of a bounded conclusion. Validation determines whether an Attestor object satisfies applicable normative requirements. Conformance determines whether a declared target satisfies an applicable requirements set using required validation and evidence.
Aggregate Validation Results are valid, invalid, incomplete, and error. Per-rule Validation dispositions are pass, fail, not-applicable, and not-tested. Conformance dispositions are satisfied, not-satisfied, not-applicable, and not-demonstrated; Conformance outcomes are conformant, nonconformant, undetermined, and error.
Attestor does not manufacture trust from a sequence of signals. It forms governed Attestations, evaluates eligible inputs under bounded rules, and produces Trust Statements whose basis, scope, limitations, provenance, and authority remain visible.