Decision lineage
Preserve the reasoning and evidence basis behind the commitment instead of reconstructing it later from memory and scattered files.
Decision integrity infrastructure
A private Decision Record.
A verifiable proof layer.
Solarascope preserves the basis, evidence boundaries, authority, assumptions and conditions behind consequential reliance. Private customer content remains access-controlled. Public verification metadata appears only when deliberately published.
Why it exists
Decisions should not disappear into a PDF.
The Decision Archive gives Solarascope customers a durable record of what was relied on, what remained uncertain, who held authority, and what conditions should trigger re-examination.
Artefact integrity
Canonical report PDFs receive SHA-256 checksums so the stored artefact can be compared against its recorded integrity fingerprint.
Re-examination
When evidence, authority, assumptions or operating conditions materially change, the record provides the basis for a focused re-check.
Privacy architecture
Private record. Public-safe verification metadata.
Decision Archive is not a public dump of customer diligence, board materials or AI governance evidence. The private record and any deliberately public verification entry are separate layers.
Private layer
- Decision Records and Archive Drafts
- Evidence and customer-supplied material
- Report PDFs and fulfilment outputs
- Customer, organisation and deal-sensitive detail
- Access-controlled storage and scoped delivery
Public verification layer
- Only deliberately published public-safe metadata
- Archive identifier and selected verification fields
- Creation/sealing timestamp where configured
- SHA-256 verification reference for the archive entry
- No automatic publication of private Decision Records
Important integrity boundary. Decision Archive does not claim that the underlying database is immutable or append-only. Public archive verification references and canonical PDF checksums provide cryptographic verification points; they do not convert the operational database into an immutable ledger.
Verified operating controls
Security is implemented as controls, not badges.
Private buckets
Customer report storage is private and normal anonymous/authenticated client roles do not receive direct access to private report objects.
Scoped retrieval
The live application denies missing and deliberately incorrect customer credentials while allowing the correct scoped credential.
Layered perimeter
HTTPS traffic traverses Nginx, host and cloud firewall controls before reaching the localhost-only application service.
Solarascope does not claim SOC 2, ISO 27001 or other certification for the Solarascope application unless and until such certification is independently obtained. Provider certifications, where referenced, are provider-level assurance only.
Before you rely on it, Solarascope it.
Make the decision basis inspectable before commitment.
Use Solarascope to structure the evidence, authority, gaps, conditions and Decision Record behind consequential business, acquisition and AI reliance.