Skip to main content
The execution layer is still being built, so nothing below runs yet. It describes the contract the errands are being built against, which is fixed.

Every step leaves a record

An errand that says it read your APR should be able to show you the page it read it off. So Hence screenshots as it goes, and every act it performs produces a receipt: what was requested, of whom, on what date, by what route, what confirmation to expect, and the proof that it was delivered. Receipts exist for you, but they are also the reason an errand’s result can be checked rather than believed. A figure that arrives without a source and a date is an assertion.

Where the figures come from matters

Results distinguish how each value arrived:
  • From a document — a statement Hence downloaded and stored, or a structured response from the service itself. The strongest kind, because the artifact is kept and the figure points at it.
  • Read off a page — a number lifted from a rendered portal page. Recorded as a reading, with the screenshot attached.
  • From you — something you told Hence in the conversation.
A result shows the kind alongside the figure. A number read off a page and a number taken from a stored statement are not the same claim, and Hence does not present them as if they were.

What you get back

A finished errand returns its state, a table or summary of what it found or did, the receipts, a reference to the screenshot taken at each account or step, and the remaining action with whose it is.

Where screenshots live

Screenshots are stored on our side and referenced. They are not pasted into your assistant’s transcript. The result points at each one rather than carrying it, so an authenticated account page does not end up scattered through a transcript that belongs to the host rather than to us. That default is the boundary, and it is the reason the warning below is survivable.
During the pilot, screenshots are not redacted. An account page that shows an account number is captured as it appears. Redaction at capture is a committed change that must land before access widens beyond the pilot group — see Trust and control.