How to use it

Take the tour

A few minutes' walk through Home, Ask, Knowledge bases, People and Help: what each part is for and how to use it. Use the arrow keys or Next, and Esc to stop at any time. Start the tour

Sign in

1. Open Grit's address. If you aren't signed in, it takes you to the sign-in page, then back to where you were.
2. Enter your email and password.
3. The first time, scan the code with an authenticator app (Google Authenticator, 1Password, Authy) and enter the 6-digit number.

You stay signed in for up to three days. Forgot your password? Use the link on the sign-in page.

Ask a question

Go to Ask and type a question in plain words. You get Grit's answer with its sources underneath; open a source to see the exact page. If Grit's material doesn't answer it, it says so instead of guessing.

• Better questions get better answers: name the product, brand or situation ("Pella impact windows in coastal Florida" rather than "windows").
• Check the sources: each sentence is numbered to the page it came from. If a source looks old or wrong, use Feedback and choose "Wrong or missing knowledge".
• Your recent questions are listed under the box, so you can ask again.

Which knowledge base is which

• Published: Grit Guide, Grit Blueprint and Stefanie's public pages and posts, as published. Everyone at Grit.
• General (external): general building-industry knowledge that's safe for customers: industry lessons, the glossary, research and published transcripts. Everyone at Grit now, and customers later.
• Internal: Grit's own working knowledge. Grit only, never customers.
• Stefanie and Ben's private notes: Stefanie and Ben only.
• A client's knowledge base (Cofer, Magbee, Tucker and the others): only the people it's shared with.

Knowledge bases lists each one with who can read it and how much is in it: the number of web pages, notes and PDFs, and how many words. Open one to see its documents.

See what's waiting for you

The top of your home page lists anything that needs you, one line each, with a button. When the list is empty, nothing needs you.

Add documents

On your home page, find the knowledge base and press Add documents.

1. A file: PDF, Word, text, or a recording (audio or video), up to 50 MB. Recordings are transcribed with who spoke and when.
2. Pages from a website: enter the address and press Find its pages. Nothing is fetched yet. Untick what you don't want.
3. Say whether Grit may use it and who owns it.
4. Press Read it on the document. It shows the cost first and spends nothing until you say yes. Only then can answers use it.

Team members can add to Internal. An admin says yes before it's used.

Fix or remove something

• An answer is wrong: Stefanie presses Review this answer under it, then approves, corrects or withdraws it. Both versions are kept.
• A document shouldn't be used: open it and press Withdraw. You see which answers relied on it first. You can lift a withdrawal later; nothing is deleted.
• A manufacturer changed a page: the new version waits under Newer editions until it's approved. Answers keep using the old one until then.

Decisions: review and approvals

• Review lists answers and items waiting for a person. Waiting for you comes first; items for someone else say whose they are, and you can read them but not decide them.
• Approvals (approvers) lists changes waiting for a yes: uploads, new website editions, and changes to who can read or approve. After you decide, a card shows what happened: in force now, or how many more approvals it needs.
• The person who asked for a change can't approve it themselves.

Send feedback

Press Feedback at the bottom right of any page. Say what it is (something wrong, an idea, a question, or wrong or missing knowledge) and what happened.

• Add a screenshot: press Capture this screen (your browser asks which tab to share; the form hides while it captures), or paste one with Ctrl+V, or drop a picture in.
• The console log and failed requests go with it so problems can be found quickly. Tokens, keys, email addresses and ids are removed first. Press See what's sent to check, or untick it.
• Follow it in Decisions, then Feedback: where each one stands, every change with its note, and messages you can answer. A change shows up in your To do.
• Approvers work the Feedback board: Needs review, Backlog, In progress, In review, Done, Declined. Done and Declined need a note, which the sender sees. Claude works the board too, shown as "Claude (agent)"; an approver can move any card back.

Your agent

An agent is an AI assistant that learns from one person's decisions. It suggests; the person decides. It never sends, publishes or speaks for anyone. Your home page shows a checklist of what it still needs and the next step.

Give Paige a task

Paige is Grit's working assistant on the Mac Studio. You give her work from Claude in your browser. She picks it up within about 15 minutes, does it with Grit's knowledge (citing it), and puts the result back where Claude can read it to you. Only tasks from Stefanie or Ben are taken.

Once: Michael connects your Claude to Paige's work queue with you on a call. In Claude, under Settings, then Connectors, a connector named Paige's work queue is added, signed in with your own queue key (from the password manager; never paste it into a chat).

Then just ask Claude in plain words. For example:

• "Put a task on Paige's queue: what do Grit's published pages say about impact-rated glass? Three points with links."
• "Add an instruction to that task: only use Grit Guide pages, nothing from vendors."
• "What has Paige finished since yesterday? Show me the results."
• "Is Paige waiting on me for anything?" When a task needs your decision (an unapproved source, an open choice, anything outside Grit), she parks it with one question and her suggestion.
• "Answer Paige on task T-12: use Therma-Tru and Pella only, draft the text only. Then reopen the task."
• For a client, name its lane: "Put a task on Paige's queue in lane paige:client_tucker: what does Tucker's material say about their dealer program? Priority 2." Paige reads that one client's knowledge base for it, in a check-in of its own, and nothing about any other client goes in the result.

Paige never sends, posts, publishes, emails anyone, spends money, approves anything or changes who can see what. If one of those would help, she lists it under Proposed next actions for you to decide.

Where work waits

There are three lists, and each has one home:

• Your To do (top of every page): everything waiting for you: reviews, approvals, and replies on your feedback.
• Paige's work queue: one queue for Paige's tasks. You add to it and read results through Claude (above). There's no second copy anywhere.
• The feedback board: what people have reported, and what's being done about it.

Reading new documents and websites runs inside the knowledge system by itself; there's no queue to manage.

What the system guarantees

Who can read what, how answers are sourced, why nothing is lost, and what agents can never do. Read what it guarantees

Settings (admins)

From Settings an admin can add a knowledge base for a new client, see who can read each one, manage people, and archive a knowledge base (a final backup is kept; nothing is deleted). Every change is recorded with who made it.

View as (Settings, then View as) shows what someone else would get from Ask, without signing in as them: a client's customer (their client's knowledge base plus General), a person on the team, or any set of knowledge bases. It only reads: nothing is kept as their question, and each source is checked against what they can read. You see only what you can read yourself; anything else is named as left out.

Need a hand?

Ask Ben. Until handoff, Michael can help too.