OCTOPUS docsocto.ad

Docs / How OCTOPUS differs, by category

How OCTOPUS differs, by category

Fourteen dimensions, compared with what each category of tool typically offers. Comparisons are by category only.

These comparisons are by category, never by product.

DimensionWhat the category typically offersWhat OCTOPUS does
Memory persistenceAgent frameworks keep per-run state; search assistants index documents; vector RAG stores text chunks. Memory across sessions and teams is left to the integrator.A typed, linked knowledge graph is the system of record. It persists across every session, agent and team. New entities enter as proposals a person confirms.
Context assemblyVector RAG retrieves the nearest chunks; relationships between facts are flattened into text.Context is assembled per task, retrieved with relationships intact across every domain in one pass, and checked against an explicit schema before it reaches the model.
Entity resolutionSearch tools de-duplicate documents, not entities; frameworks leave it to the developer.People, organizations, products and events are typed, reconciled and de-duplicated across sources and aligned to standard public vocabularies.
Decision recordTracing tools log model calls; the decision itself lives in chat.Proposals, options and verdicts are recorded as auditable structure, attributed and replayable. Consequential decisions go to a person, on the record.
Autonomy controlFrameworks offer a human-in-the-loop hook; automation is on or off per flow.Autonomy is set per lane. New behavior runs in shadow first, with a decision date and a kill switch. Brake the whole fleet or one lane.
Task closureA task is complete when the agent returns or the step succeeds.A task closes only on evidence that the effect landed (the change merged, the record was written, the page serves the new version), never on the agent's report alone.
Approval modelApproval steps ask the same 'are you sure?' about every action.Approvals are sorted by reversibility: reversible actions run at once with a short undo window, irreversible ones need a deliberate confirmation, and higher stakes ask for a more deliberate one. A decision card missing context is refused before it reaches a person.
Failure handlingErrors go to logs and dashboards; retries are configurable.A failure becomes a tracked record with a measured cause and a fix carried to closure.
Silence and unknown statesA quiet queue reads as healthy unless an error fires.A held lane is shown as held, a lane that went quiet raises its hand, and a signal the platform cannot read reports unknown, never healthy. Alerts fire on a change of state.
Schema contractsValidation is the application's job; RAG stores accept any text.Data is validated against explicit schema contracts before it lands, so drift is caught before it spreads.
Audit and provenanceCall logs with retention; provenance per document at best.A complete, queryable, tamper-evident record of what happened, when, by whom and why, with provenance for how each piece of knowledge entered and what it supports.
TenancyTenants separated by policy and access control.Tenant isolation by architecture, not policy: one tenant's credentials cannot reach another tenant's estate, and every connection is authenticated and scoped to its tenant.
IntegrationAn SDK (frameworks), connectors (integration platforms) or indexers (search).An MCP endpoint, open APIs over knowledge, context, signals and content, connectors, a governed external-model counsel lane, and cross-organization federation. Every connection is authenticated and tenant-scoped.
Grounding guardsPrompting conventions, left to the developer.Two practices enforced as engineering: look up before you make up, and verify the effect before reporting success.