What each part of OCTOPUS does, what you control, and what to ask to see when you evaluate it. Memory first, because everything else stands on it.
Receipts, not adjectives.
Last updated · Machine-readable: llms.txt · capabilities.json
Most agents forget last week. In OCTOPUS a typed, linked context graph is the organization's system of record, and every agent and team works from the same one.
Knowledge persists across every session, every agent and every team, and accrues instead of evaporating into chat logs. It is organized by meaning and stays queryable over time.
People, organizations, products and events are extracted, typed, classified and reconciled across sources. The same entity is linked and de-duplicated wherever it appears, and aligned to standard public vocabularies.
New entities arrive as reviewable proposals, and a person confirms before anything durable is written. Signals are captured the moment they appear, scored for relevance, and the ones that matter are promoted into durable knowledge with a human in the loop.
The platform knows how knowledge entered, who created it and what it supports.
The right context is assembled for each task and shape-checked against an explicit schema before it reaches a model. Retrieval keeps relationships intact instead of flattening them into text chunks, and pulls related facts across every domain in one pass.
Meetings, calls and threads are distilled into decisions, action items, topics and expertise. Past conversations stay searchable and reusable as grounded memory.
| Claim | Ask to see |
|---|---|
| Knowledge persists across sessions, agents and teams. | A fact recorded in one session, retrieved by a different agent in another. |
| A person confirms new entities before they are written. | The proposal queue, and the confirmation on one entity. |
| Provenance on every fact. | For one fact: how it entered, who created it, and what it supports. |
| Context is schema-validated before it reaches a model. | A context assembly that failed its shape check, and what happened next. |
A coordinated fleet of goal-driven agents completes multi-step work within the bounds you set, with dispatch, hand-off and health monitoring. Consequential actions pass a coherence check before they execute, and a task closes only on evidence that the effect landed.
Work enters the fleet as defined tasks with a goal and acceptance criteria. Agents claim tasks by capability, preferred specialists first and capable fallback after.
Each lane runs inside an explicit scope: which systems it may touch, what it may change, and which moves need a person.
A task closes on evidence that the effect landed (the change merged, the record was written, the page serves the new version), not on the agent's report.
Failures become tracked records with a measured cause and a fix carried to closure.
Autonomy is set per lane. New behavior runs in shadow first, observed, with a decision date and a kill switch.
Brake the whole fleet or one lane. A held lane reads held, and a silent one is told apart from it. A signal the platform cannot read reports unknown, never healthy. Workers and services report heartbeats, and alerts fire on changes of state.
| Claim | Ask to see |
|---|---|
| A task closes on evidence, not on the agent's report. | One closed task, and the evidence that closed it. |
| Each lane runs inside an explicit scope. | One lane's scope, and a move it was refused. |
| New behavior runs in shadow first, with a decision date and a kill switch. | One shadowed behavior, its decision date, and its kill switch. |
Proposals, options and verdicts are recorded as auditable structure rather than lost in chat, and consequential decisions are routed to a person, on the record.
Decisions that belong to a person arrive on the Desk, phone-first. Each card leads with the question, a recommendation and its reasoning, options side by side, and detail on demand. You can reply by voice.
A card that depends on missing context or undefined terms is refused before it reaches you.
A reversible action executes at once, with a short undo window. An irreversible one (anything that leaves the organization, such as an outbound message or a payment) waits for a deliberate confirmation. Higher stakes ask for a more deliberate one.
Each decision is recorded with who made it, when and what they chose.
| Claim | Ask to see |
|---|---|
| A card missing context is refused before it reaches a person. | A refused card, and the reason it was refused. |
| Each decision is recorded with who, when and what. | The record of one decision, read back. |
Proactive, scheduled briefings and monitoring reach you before you think to ask: what moved, what is stuck and what is waiting on you.
A discovery loop continuously maps partners, opportunities and the actors worth knowing in your orbit.
A living, tracked model of your products, positioning, go-to-market and the market signals moving around them.
Content moves from idea to published asset, grounded in your knowledge and shaped to your voice, with provenance linking each piece to what it drew on. A hard pre-publish gate blocks anything drawing on embargoed or pre-filing material until the protection window clears.
External-model counsel is a governed lane for a second opinion from outside models, redaction-checked and IP-gated so nothing proprietary leaves the estate before you are ready.
We're onboarding a small group of teams that need agents they can depend on. Leave your work email. We'll remember it.
No spam. Your data is never sold. We only write about access.
Ask the octopusGrounded answers about OCTOPUS