Thundercloud Technology01 / Initial scope
Read and draft
The reference-engine example permits selected reading and drafting. A send request is refused under that contract.
Proof · Scope matters
Inspect the result.
Understand its limits.
A useful demonstration identifies the system, the action, the observed result and what remains untested.
Controlled local demonstration
A permission can change.
The boundary must follow.
02 / Changed scope
Replace the contract
A replacement contract includes the send capability. The previous contract is superseded and cannot authorize later work.
03 / Separate principal
Keep grants separate
The note-taking agent’s scope does not acquire the email agent’s capabilities. Its send request remains refused.
What this establishes
Recorded permission checks from a local reference-engine test. The story is fictional and sending is simulated; no email account is connected.
What remains outside this demonstrationLive email delivery, complete interception, production security, replacement-team recovery and a completed customer outcome.
Product direction
Authority. Evidence.
Continuity of control.
| Area | Current foundation | Proof still required |
|---|---|---|
| Authority | Scoped grants and reference-engine permission checks; supported integrations must be qualified individually. | Acceptance for each customer principal, route, dependency and revocation condition. |
| Evidence | Records and integrity verification for the evidence available to the system. | Coverage, attribution, retention and independent observations of external effects. |
| Continuity | Asset-boundary and handoff planning. | An authorized recipient using the agreed delivered material after a tested transition. |
Reading the record
Three different observations.
A captured request
A record of what was requested through a supported observation point. It does not establish that the action completed.
A tool-reported result
A record of what the tool reported. It is not independent confirmation of the resulting external state.
An independently confirmed effect
A state change supported by a separate observation, with its source and limits identified. Confirmation applies only to what was observed.
Coverage depends on connected systems and supported observation points. Provenance and integrity checks do not establish truth, completeness, motive or wrongdoing. Missing records and unobserved effects remain unknown.
Thundercloud records and reports documented outcomes. Customers maintain their own response framework, make response decisions and choose and arrange any remediation. We do not advise on those decisions or offer remediation; we remain accountable for our own work and product maintenance.
One workflow.
A testable outcome.
A scoped evaluation identifies its owner, asset, permitted and refused test actions, available evidence and defined permission-change check.
A continuity exercise additionally needs an agreed recipient, transferable components and a successful acceptance check. A record or agreement alone does not establish recovery.
Discuss an evaluation →