Company Context

Maintain one governed, organization-wide source of verified company facts and use it safely from Chat, workflows, and Process Flows.

Company Context is your organization's shared source of verified priorities, policies, terminology, constraints, risk appetite, stakeholders, and other durable facts. Each organization has at most one Company Context, and it always uses the Memex knowledge-base engine.

Company Context is not the former ontology- or table-backed Organization Knowledgebase. It does not have imports, promotion, governed rows, or extraction domains. It is one centrally maintained Memex knowledge base.

Who can use it

Surface	Read	Write
Company Context editor	Organization owners and administrators, subject to clearance	Organization owners and administrators, up to their own clearance
Chat and Cortex	Authorized organization members, subject to clearance	Never
Knowledge workflow block	Search and Read File, subject to clearance	Add Data is rejected
Process Flow AI action	Only when the pack declares a Company Context briefing	Never

Being an administrator grants access to the dedicated editor; it does not bypass classification. Every reader sees only material at or below their clearance, and an administrator cannot apply a classification above their own clearance.

Create and maintain Company Context

Open Settings → Organization → Company Context. The first visit initializes the organization's singleton if it does not exist yet.

Create pages and folders, or ingest supported files and sources. Use verified, durable facts rather than process-specific drafts.

Apply the appropriate classification to every page or source. Search the knowledge base to confirm that expected wording and references are discoverable.

Update or remove stale material from this same editor. Changes are audited and become available to authorized readers after indexing completes.

The editor uses the same page, folder, source, upload, search, and classification controls as a Memex workspace knowledge base. Generic knowledge-base APIs, Chat tools, workflow writes, recordings, and Process Flow projection jobs cannot use this privileged write path. They return COMPANY_CONTEXT_ADMIN_REQUIRED when they target the singleton with a mutation.

Ground AI actions without rewriting their prompts

A pack author can declare a stable companyContextBriefing.question on an AI workflow action. Before the action runs, Scrydon adds server-owned stage, task, action, and subject details, asks Company Context that task-aware question, and injects the cited answer as a separate context category. The pack's prompt remains unchanged.

An absent, empty, or temporarily unavailable Company Context does not block the action. The action runs with its generic pack prompt, and the Prompt & Context panel shows the briefing status. See Process Flow action types for the authoring contract.

Read it without changing it

Ask Chat or Cortex to search Company Context or answer from it.
Use Search or Read File in the Knowledge workflow block.
Open authorized References from a grounded Process Flow output or shared action conversation.

References are authorized again when opened. A source that has been removed, reclassified above your clearance, or otherwise made inaccessible appears as unavailable instead of exposing a stale link.

What never flows back into Company Context

There is no promotion operation. Chat messages, attachments, generated answers, recording transcripts, accepted refinements, and Process Flow artifacts never update Company Context automatically. Relevant shared-conversation summaries and decisions are written only to the Process Flow instance knowledge base. To make a fact organization-wide, an authorized administrator must add or edit it deliberately in the Company Context editor.

Knowledge bases — choose between conversation knowledge, workspace knowledge bases, and Company Context.
Knowledge Base Clearance — understand classification and no-read-up behavior.
Chat knowledge bases — query Company Context from Chat without granting write access.
Knowledge note editing — use the shared Memex authoring controls.