Skip to content
SHAMPOO

Product

Shared durable memory and orchestration for people, agents and models.

Your people and AI systems can share durable working memory while SHAMPOO keeps access boundaries, sessions and projects under your control.

Technical detail
A central service holds the tools and their semantics, authorisation decisions, project scope and persistence. Workstations run a thin adapter that presents a local MCP interface, handles secure transport and session renewal, and forwards every operation to the central service. Memory boundaries are profiles: a connection selects one and its session stays bound to it.

In plain terms

What SHAMPOO is

SHAMPOO is persistent shared memory and orchestration infrastructure. It gives humans, AI agents, models, automations and applications a place to work with shared durable context instead of starting again from disconnected chat histories or temporary model context.

It is more than simple AI memory. Knowledge, tasks, sessions, context preparation, reflection, structured debate, recorded decisions, jobs and lanes, human clarification, diagnostics and access control are all part of the same platform, and all of it stays inside boundaries you define.

SHAMPOO is designed for both people and machine clients. It is not a chatbot, and it does not replace the people using it: human involvement is part of the record, not a defect to be removed.

Separate strands in, one durable structure out

Who works in SHAMPOO, and what their work becomes.

  • Human
  • Agent
  • Model
  • Automation
SHAMPOO
  • Memory
  • Tasks
  • Knowledge
  • Sessions
  • Decisions
  • Workflows
People, agents, models and automations keep their own identity; SHAMPOO binds their work into one durable structure.

Capability groups

What it gives you

Each capability is plain English first. Technical detail is one click away, never in your way.

Memory

Memory that survives the conversation

What people and agents learn is written down once and can be recalled later, by whoever picks the work up next.

Technical detail
Durable knowledge is held as entities, observations and typed relations. Entities are unique by name, facts accumulate as observations, and structure accumulates as relations. Nothing is physically deleted: retirement is a lifecycle state, and retired knowledge can revive with its original creation evidence intact.

Tasks

Work that agents can resume

Tasks and notes live outside the chat, so a fresh session can see what is ready, what is in progress and what is finished.

Technical detail
Tasks carry an explicit lifecycle (not started, in progress, done, archived, cancelled), and every transition preserves history rather than overwriting it. Notes use the same storage without actionable state. Digests and ready views compile the current work set deterministically.

Context

Shared context without shared chaos

A new session can be brought up to speed with the relevant work, recent history and open questions instead of starting blank.

Technical detail
Context is compiled by the platform: ready and prime views, digests, session recall and context packs. Compilation is deterministic, so the same state produces the same orientation for any client.

Decisions

Human decisions remain part of the record

When people answer a question or agree an approach, that answer is stored alongside the work rather than lost in a thread.

Technical detail
Agents can queue clarifications for humans and record the answers as durable material. Structured debate captures competing positions; quorum records an agreement with named participants. Inbound material can require review before it becomes agreed state.

Boundaries

Separate boundaries where separation matters

A profile keeps one body of organisational memory separate from another, so private work and shared work do not silently merge.

Technical detail
Each profile is an independently authorised storage and security boundary. A connection selects one profile at handshake and the session stays bound to it. Inside a profile, principals hold an explicit project grant list; ungranted content reads as absent rather than denied, so foreign projects cannot be probed by name.

Orchestration

Orchestration beyond simple chat

Work can be organised into streams that different people and agents claim, complete and hand over, without everyone being online at once.

Technical detail
Jobs are claimable units of work with explicit completion and release. Lanes group work into reviewable streams with their own state and merge step. Recurring timers and delivery jobs are materialised by a separate mechanism that transports work but makes no decisions.

Memory

Consolidation over time

Accumulated memory can be reviewed and tidied deliberately, with proposed changes reviewed before they are applied.

Technical detail
Reflection runs as an explicit pipeline: audit, start, status, decide, apply, review, with cancel, archive and discard paths. Proposals are separate from application, so consolidation is a reviewed action rather than a background rewrite.

Boundaries

History as evidence

Meaningful actions leave a record of who did what and when, so the past can be examined rather than inferred.

Technical detail
Durable objects move between lifecycle states rather than being physically deleted, and transitions record an audit/history event. Operations either complete or fail atomically, so partial state is not left behind.

Operations

Diagnostics that answer the real question

Operators can check what a connection can currently see and whether the service is healthy, before escalating anything.

Technical detail
Status reporting exposes the visibility marker and project list for the current session, which usually distinguishes a scope surprise from an outage. A fuller diagnostic pass reports service health in detail.

Who it is for

The same product, explained at the level you need.

For a managing director

Understand what you are buying: software your organisation owns and runs, giving your people and AI systems a shared, durable working memory.

For an IT manager

A central service plus MariaDB, deployed where you choose, with thin workstation adapters and no database credentials leaving the host.

For a developer

An MCP interface with 107 documented tools covering tasks, knowledge, sessions, context, reflection, debate, quorum, jobs and lanes.

For a security reviewer

Profiles are independently authorised boundaries, sessions are profile-bound, grants are enforced centrally, and revocation applies on the next call.

For an AI engineer

Durable memory, deterministic context compilation, structured debate and claimable work: coordination that survives a restarted agent.

Interface

Twelve categories of documented tools.

Machine clients reach SHAMPOO through MCP. There are 107 documented tools; you do not need to read them all to use the product.

  • Tasks and notes

    Everyday work: create, assign, query, digest and archive tasks and notes.

  • Knowledge graph

    Entities, observations and relations: the durable knowledge surface.

  • Links

    Connections between tasks and the entities they concern.

  • Sessions and context

    Saving, recalling and closing the working state of a session.

  • Intel and knowledge tiers

    Assessing context, asking humans, promoting candidate facts and building context packs.

  • Reflection

    Reviewing and consolidating accumulated memory as a reviewed pipeline.

  • Debate

    Structured disagreement: roles, posts, verdicts and protocol maintenance.

  • Quorum

    Recording agreement with named participants.

  • Jobs and lanes

    Claimable work units and reviewable streams of work.

  • Inbox

    Reviewing inbound material before it becomes agreed state.

  • Diagnostics

    Status and health checks for a session and the service.

  • Authentication

    Enrolment, handshakes, revocation and session administration.

Ownership

Software, not another memory cloud.

SHAMPOO is purchased software that you install and operate. It is not a subscription service where your organisation's working memory lives in somebody else's account.