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 preserves the relationship between the original request, the assigned work, the evidence, the review status, and the memory update.
What a proof record contains
A completed or blocked request can produce a proof record with:
- Request: the original ask, requester, scope, and acceptance criteria;
- Assignment: the owner, agent path, or human review path;
- Evidence: files, reports, screenshots, task records, citations, or receipts;
- Review: accepted, rejected, blocked, or revised;
- Report-back: the 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.
Rule
Proof storage should answer one question clearly: what was requested, what happened, who reviewed it, and what the company can trust next time?