Knowledge Engine

What it does

The Knowledge Engine is the Knowledge section of the workspace: what Nexus knows about the client. Their site, their documents, their meetings, their competitors, their brand and their people. Every other engine writes with this context, so the more that's here, the more specific the work.

Its optional module, Competitive intelligence, has its own guide.

Set it up

"Show the knowledge engine setup." shows what's done for the client and the next step. The same checklist is on Roadmap › Onboarding in the app.

1. Website — Give the client's website URL.
2. The client's site in the knowledge base — Read the client's site pages into the knowledge base (done in the background; refreshed on a schedule).
3. Client documents added — Add the client's own material: decks, briefs, case studies, product docs, a Drive folder or links.
4. Meetings reaching the knowledge base (optional) — Each strategist connects their Google Meet once; call transcripts with the client then reach the knowledge base.
5. Competitors — Name 3-6 competitors; the G2M's competitive set is added automatically once it exists.
6. Brand identity (optional) — Build it from the website and any brandbook (brand-identity agent).
7. A client contact on the team (optional) — The client's people are read from their Slack channel once a day; add anyone else on the Team page.

• The site is read into the knowledge base in the background.
• ✋ The client's own material comes from the client: decks, briefs, case studies, product docs. "Add this document to Acme's knowledge: [link]."
• ✋ Each strategist connects their Google Meet once, so call transcripts with the client reach the knowledge base.

Prompts

• "Show the knowledge engine setup."
• "Add this document to Acme's knowledge: [link]."

Machine twins: /help/knowledge-engine.json · /help/knowledge-engine.md · /help.json · /llms.txt

Reviewed 2026-10-31. In Slack, ask Nexus how do I … and it answers from this guide, with where your company stands.