Skip to Content
Gorila docs

Concepts

Tasks and knowledge, areas and projects, what is private and what is the team's, and how changes get approved.

Tasks and knowledge are separate

Gorila has two domains and they never mix: different data, different MCP tools, different sections in the web app.

Tasks are work: a title, a context (background, goal, how you know it is done, links), an assignee, a status (todo, doing, done), a priority and a due date. A task has a short id such as MAL-42 that people and AIs use to refer to it. There are no custom statuses, labels or fields on purpose.

Knowledge is how the company works and writes. Entries live in fixed categories: brand and tone, copy, product, marketing, sales, support, operations, decisions and company. An entry has a title, a summary and a body, optional triggers, and can be marked "always applies". Knowledge is not attached to a project.

Areas and projects

  • An area is a team or a product with its own voice and rules (Marketing, Support, a brand). Every organization has a general area. Knowledge is company-wide or belongs to one area; when an area's entry and a company-wide one disagree, the area's wins.
  • A project groups tasks inside an area and is temporary: it is archived when it ends.
  • Each person sees the tasks and knowledge of their areas. Owners manage the organization; area admins manage their area's members, agents and approvals.

Private and team

Anything Gorila learns from a person's own chats or their setup is private to that person until they choose to share it. Private tasks (for sensitive matters such as hiring or salaries) are visible only to their creator and assignee. The database enforces this with row-level security, not only the app.

Proposals and approval

AIs do not edit the company's knowledge directly. When someone corrects the AI ("we never offer discounts, we offer free shipping on the next order"), the AI calls propose_knowledge_change. A person who can approve it (an owner, or an admin of that area) says yes in their AI or in the web app, and only then does it apply. Every version is kept and any change can be undone.

People and agents

Every person and agent has a short profile the whole team sees: a title and what they handle. A person's own AI drafts it during their onboarding and they confirm it; an agent's is written by whoever adds it. When someone asks for work that takes several people, or announces a change ("from now on, discounts above 10% need my OK"), their AI reads these profiles to decide who gets which task, tells them who it left out and why, and asks when it isn't clear. For a change, the rule is proposed first and the tasks point to it.

Gorila also helps notice who else a task concerns. Each profile has a one-line version its owner's AI writes ("Web: pricing page, landings, checkout promo codes"), and when a task is created or opened the reply lists that line for every teammate. The AI reads it and speaks up only when the task is about something a teammate owns: "Laura runs the pricing page, shall I tell her?". It says nothing for most tasks, and the list is never sent for private ones.

Agents are teammates. An admin adds one (or the agent asks to join and an admin approves it), it gets a @handle, an area and its own token, and from then on it receives tasks, comments on them and reads knowledge. Agents can only propose team knowledge; they never approve anything. See Agents.

Closed tasks are decisions

When a task is done, its closing comment stays. Before working on something similar, an AI reads what was decided last time (get_task lists the related closed tasks). Rules that will apply again are promoted to knowledge.

On this page