Scope receipt
Shows what was allowed and, just as importantly, what remained outside the approval.
Receipts
The work is not finished until the result is inspectable.
A TitanDash receipt binds the request, evidence, authority, execution, and verification into one record.
TSK-SAMPLE-TLS-001
Renew one TLS certificate
- Requested
- Restore HTTPS for shop.example after a certificate warning.
- Evidence
- Presented certificate expires in 12 days; nginx configuration passes; port 443 answers.
- Approved scope
- Renew one certificate, reload nginx, verify hostname and expiry.
- Not approved
- DNS changes, package upgrades, application edits, unrelated service restarts.
- Preflight
- Renewal account readable; challenge path reachable; current certificate preserved.
- Result
- Renewal completed and nginx reloaded without configuration error.
- Verification
- Expected hostname presented; new expiry read back; HTTPS returned 200.
- Rollback
- Prior certificate retained until post-action verification passed.
Evidence receipt
Preserves the measurements that justified the action instead of rewriting the story afterward.
Outcome receipt
Records whether verification passed, failed, or remained incomplete. Those states are never interchangeable.
Start here
Make the next server action inspectable.
Explore the proposed receipt format. Customer repair execution is not available; onboarding creates no purchase or server authority.