Control
Every action leaves a record
Control you can verify, not just claim. Nolocron tracks where every block came from and records what every operation did — including every action an assistant takes — so you can check its work instead of taking it on faith.
The trail behind one answer
SCOPE
Held to project ‘Q3 Launch’ (locked)
READ
12 blocks from ‘Launch notes’
TOOL
vault.search — query: ‘pricing tiers’
TOOL
block.hydrate — 3 blocks expanded
CITE
4 sources cited in the answer
RESULT
Answer returneddone
RUN RECEIPT
Receipt saved · 7f3a91e2-04bd
Recorded in the append-only event store — reviewable after the fact.
Why it matters
When a system hides how data was retrieved or transformed, you can't tell whether a record — or an answer built from it — is trustworthy. A black box you can't inspect is one you can't trust.
What Nolocron provides
- Provenance flows down the source, store, and block hierarchy and stays with each block.
- An append-only event store records imports, exports, deletes, scheduled tasks, and assistant queries.
- Every assistant action leaves a receipt: who acted, what was accessed, and a redacted record of the run.
- Machine-generated output is labelled derived, never passed off as source.
How it works
- Open a block and read its source story.
- Open the activity record to see every operation.
- Follow an assistant's citations back to the original blocks.
- Export or document the trail when you need to show your work.
Proof
- Every block traces to its origin; every action leaves a receipt.
- What the AI said stays separate from what the source said.
- The record-keeping runs today; a single see-everything-and-undo view is on the roadmap.
Related