Loading your memory…
By what the recall returned
What agents remembered, confirmed or refuted
Everything that needs a human. The same list as the daily digest.
Every request the hub opened. A fact leaves the memory only when its request merges, and it keeps a link to where it went.
Only what is blocking something right now. Everything else on these pages can wait.
When colleagues keep confirming the same knowledge, engram proposes writing it into a repository. You approve each file in the review queue; nothing is ever merged by engram.
To change where a file goes or how much agreement it needs, change the rules.
A technology fact that names a client stays inside that client's repository instead of reaching everyone. engram suggests names from the repositories it sees; you say which ones are clients.
The same rules apply on the hub and on every laptop. A reviewer’s change needs a second reviewer to approve. An administrator’s applies when saved.
The whole file is checked before the proposal is sent.
Pausing stops facts moving between laptops and the hub. Everyone keeps working with what they already have.
Rule changes waiting for approval, then everything the hub decided.
| When | What | Who | Detail |
|---|