Cloud governs. Your compute executes. Proof closes the loop.#
Trusted Compute is the LumenFlow pattern for routing an Ask to an enrolled connected runtime running on hardware you control — a developer machine, CI runner, private server, or edge box — and keeping the work governed by policy, approvals, and evidence in Cloud.
This is not "LumenFlow runs on anyone's machine." It is bring your own trusted compute, governed centrally.
The chain#
| Step | What happens | Where it runs |
|---|---|---|
| Ask | Operator submits intent | Cloud |
| Dispatch | Cloud routes work to an enrolled runtime | Cloud → Runtime |
| Rules | Policy decisions allow or deny each scope | Runtime + Cloud |
| Tool calls | Runtime executes code edits, tests, etc. | Runtime |
| Approvals | Risky actions (e.g. PR creation) pause for human sign-off | Cloud |
| Proof | Evidence syncs back, replay assembles the chain | Cloud |
Evidence bundle#
Each run writes a canonical evidence bundle. It holds the core Proof files plus a signed manifest:
| File | Contents |
|---|---|
ask.json | The submitted Ask |
node-session.json | Connected-runtime session metadata |
policy-decisions.jsonl | Allow / deny decisions per scope |
tool-calls.jsonl | Each tool invocation with summaries |
file-diff.patch | Code changes produced |
test-results.json | Test outcome summary |
approval.json | Approval request and resolution record |
pr-summary.md | Human-readable PR description |
replay-link.txt | URL into Cloud Replay |
manifest.json | Schema version, bundle kind, run id, mode, required artifact list, artifact hashes, signer key id, and signature algorithm |
manifest.sig | Detached Ed25519 signature over the manifest |
verifier-public-key.pem | Public key for independently checking the detached signature |
A third party can verify that the required files are present, the hashes match, the schema is supported, and the detached signature validates.
Naming#
The user-facing nouns follow the LumenFlow product language: Ask, Connections, Rules, Approvals, Proof.