Grit Blueprint · What the system guarantees

Who can read what

Each knowledge base has its own lock. The database checks every read against the reader's own key. A page or an agent can't read a knowledge base its key wasn't given, even if a screen or a prompt asks it to.
Internal is for Grit only. Customers will read General (external) and their own knowledge base, never Internal.
Private notes stay private. Stefanie and Ben's private notes are readable by Stefanie and Ben only. A client's knowledge base is readable only by the people it's shared with.
It's checked, not assumed. An access audit tries every key against every knowledge base: each reads what it should and is refused everywhere else. It passes 190 of 190 checks today and runs after every change.

Every answer shows where it came from. Each sentence links to the page it's based on.
No source, no answer. If Grit's material doesn't cover the question, it says so instead of guessing.
Only approved material is used. A new upload is used only after an admin says yes. When a manufacturer changes a page, answers keep using the version Grit approved until someone approves the new one.
A withdrawn document stops being used at once, and you see which answers relied on it before you withdraw it.

Decisions are permanent records. Every review, approval and change records who made it, when and why. A mistake is fixed with a correction that sits beside the original, so both stay visible.
You can see how things stood at any time in the past. The feedback board and the records can be read as they were on any earlier date.
Withdrawing or archiving deletes nothing. A withdrawal can be lifted. An archived knowledge base keeps a final backup.
Backups every night, plus one every 5 minutes for withdrawals. Every knowledge base is backed up each night, and the whole server too. A full restore was rehearsed on 7 November, and a client's knowledge base was restored again on 10 November after the database upgrade: both came back identical.

An agent never acts for anyone. Stefanie's agent, Paige and the client agents never send, post, publish, email, spend money, approve anything or change who can see what. Anything like that is listed for a person to decide.
Your own decision comes first. When an agent learns from your reviews, its suggestion stays hidden until you've decided, so it can't steer you.
Changes to access and approval rules need a second person. The person who proposes a change can't approve it, and the database refuses a change approved by the same key that proposed it.
Claude on the feedback board can only move feedback cards. It has a key of its own that can't read or change anything else. Every move is labeled "Claude (agent)" and needs a note, and an approver can move a card back at any time.

Costs are shown first. Reading a document or a website shows the cost before anything is spent, and nothing is spent until someone says yes.
Everything stays in Grit's own Amazon account, in one region (Ohio, us-east-2). Every page is private to signed-in Grit people.
Updates are checked before they're installed. Each database release is signed by its maker, and the signature is checked before it goes on Grit's servers. Every update goes to the test server first.

You're named from your sign-in, never from what a page says.
Secrets are stripped before anything leaves your browser. Sign-in tokens, keys, email addresses and ids are removed from the console log, and only failed requests' addresses are kept, never their contents. You see it all before you send it, and you can leave it out.
Erasing a person's feedback makes it unreadable for good. Each person's feedback is sealed with a key of its own. Erasing destroys that key, so the words can't be read now or at any earlier date, and the database issues a receipt that proves it. Sealing was switched on before any feedback was sent, so this covers all of it.

An answer can still be wrong if the source is wrong or old. That's why answers can be reviewed, and why Stefanie's corrections are kept.
An agent's suggestion is a suggestion. Read it before you use it.
Someone who can read a knowledge base can copy what they read. The system controls access; it can't control what people do with what they've read.

Something here doesn't match what you see? Use the Feedback button. It goes straight to the board.