Memory and Knowledge Now Follow the Role

Details

Until now an employee's memory and the knowledge it drew on sat outside the permission system. From today they sit inside it. Every knowledge lookup, every fact pulled into an answer, and every note an employee writes back to its own notebook or work journal is checked first against the access of the person it is working for at that moment. That last part matters more than it sounds. An employee is not one fixed identity with one fixed reach: it works for whoever is talking to it. The check is therefore made per action, as the action happens, rather than fixed once when the employee was set up. Ask the same employee the same question as two different people and each of you gets an answer bounded by what you can already see. Trained sources, notebooks and work journals each carry their own setting: shared with the organisation, or restricted to their owner and the people explicitly granted access. Restricted means restricted here. Unlike an ordinary workspace file, an Owner or Admin does not quietly inherit private material by asking an employee for it. They can still manage who has access, but they cannot read through an employee as a side door. Nothing moves and nothing is deleted by this. Narrow someone's access and what an employee recalls for them narrows with it. Widen it again and it widens back.

What changed

• Knowledge lookups are checked against the person asking, not the employee alone
• What an employee writes to its notebook and journal is scoped the same way
• Checked at the moment of each action, so no employee keeps yesterday's reach
• Owners and Admins cannot read restricted material through an employee
• Change access and recall changes with it, without moving or deleting anything