Proof Storage & Operating Records
Where Niyatna stores evidence, review outcomes, and memory updates for company work.
Niyatna stores proof so delegated work can be reviewed later.
The storage layer should preserve the relationship between the original intent, assigned work, evidence, review status, and memory update.
Proof record schema
A completed or blocked intent can produce a proof record with:
intent: original request, requester, scope, and acceptance criteria;assignment: owner, agent path, or human review path;evidence: files, reports, screenshots, task records, citations, or receipts;review: accepted, rejected, blocked, or revised;report_back: final summary sent to the requester;memory_update: what should be remembered or ignored next time.
Storage principles
- Store evidence that helps the company audit work.
- Keep sensitive context scoped to the right workspace.
- Avoid exposing private credentials or raw confidential data in proof bundles.
- Keep draft, staged, and accepted records distinct.
- Preserve enough history for future decisions without turning memory into command.
Data rule
Proof storage should answer one question clearly: what was requested, what happened, who reviewed it, and what can the company trust next time?