Goal and authority
Requested outcome, governing purpose, jurisdiction, constraints, requesting authority and human gates.
Evidence and provenance
Built, tested, deployed and proven are different states.
RSQS AI aims to preserve the evidence required to distinguish architectural intent from implementation, testing, deployment and independent verification.
Evidence object.
Consequential execution should leave a durable record of what was requested, what authority existed, what ran, what was tested and what remains uncertain.
Capabilities and versions
Execution plan, capability dependencies, source versions, deployment targets and implementation lineage.
Tests and artifacts
Test results, health checks, artifact hashes, generated outputs, observed limitations and failure states.
Human decisions
Review, authorization, release acceptance and any human action required during execution.
Traceability
Timestamps, source references, evidence links, hashes and immutable identifiers connecting claims back to their basis.
Known unknowns
Uncertainty remains represented explicitly rather than being collapsed into success, safety or compliance.
Public proof register.
The public register is intended to expose verified capability claims without publishing unnecessary protected implementation details.
| Capability | Claim state | Public proof |
|---|---|---|
| RSQS AI institutional web surface | Live / externally verified | Public HTTPS endpoint, governed Contabo deployment, external content verification. |
| Zenodo production adapter | Built / governed workflow | Production-only endpoint restriction, identity validation, DOI preparation and explicit release confirmation. |
| Institutional publication pipeline | In integration | LaTeX source, PDF build, artifact hashing, Zenodo manifest and DOI linkage. |
| Evidence-led capability register | Expanding | Versioned capability, deployment and evidence records exposed selectively through the public site. |
Fail closed
No evidence is not evidence of safety, compliance, success or authority.
Where proof is absent, the public state should remain unverified or unknown. This is intended to prevent a growing institution from confusing repository existence, architectural descriptions or successful builds with demonstrated operational capability.