Documentation

SPM is the structured, temporal, verifiable and injectable memory layer for agents and teams.

SPM turns fragmented project knowledge into governed project memory that agents can query, package, inject, share, audit and reuse.

Guide index

QuickstartCreate a project, ingest memory and generate the first context pack.API modelUse project-scoped endpoints for objects, search, bundles and temporal memory.MCP and CLIExport context packs and governance records into agent workflows.Agent integrationConnect SPM to agent tools through MCP, CLI, API and context-pack handoffs.SecurityUnderstand entitlements, provenance, retention, legal holds and audit surfaces.PackagingMap SPM into Core, Team, Business, Enterprise and Marketplace offerings.

01 - quickstart

Create useful agent memory in one product flow.

Setup path

Move from tenant setup to an injectable, governed context pack without losing source, temporal layer or policy state.

7 steps

Create organization

Establish the tenant boundary for users, projects, providers, policies and audit logs.

Create project

Open a project memory workspace where SPM can preserve original, current, working and historical context.

Connect source

Attach repositories, files, docs or external systems so memory can be ingested with provenance.

Ingest memory

Normalize source material into memory objects, temporal events, tags, topics and searchable indexes.

Generate context pack

Ask SPM for a scoped, verifiable package that contains only the memory an agent needs.

Test injection

Use the pack through MCP, CLI or API and inspect how the agent receives project memory.

Share governed context

Publish or share context with entitlement tokens, safety status, source metadata and access logs.

CLI / MCP handoff

Generate a verifiable context pack.

verified

export SPM_API_URL=http://localhost:8000
export SPM_API_KEY=<api-token>
spm init --api $SPM_API_URL --project <project-id>
spm temporal state --topic release-readiness --limit 50
spm temporal context-pack create --action-name agent_handoff --topic release-readiness --tags mcp,agent
spm memory-agent maintenance run --topic release-readiness --min-confidence 0.8
spm memory-agent maintenance reviews list --status pending
spm launch readiness --json
spm launch readiness-export --out spm-release-readiness.zip
spm deploy preflight --mode shared-host --host <server-ip> --identity-file ~/.ssh/id_2020_rsa --json
spm deploy shared-env --http-port 3500 --https-port 3543

The CLI and MCP flow should always end in a context pack that can be inspected, verified and injected into an agent run.

pack

hash locked

policy

checked

agent

ready

02 - memory model

SPM keeps time, topic and trust as first-class dimensions.

Requirements

Original memory

Founding constraints, requirements, project principles and non-negotiable facts that agents must keep in view.

Truth

Current state

Accepted project state, latest architecture, active policy decisions and the facts agents should treat as current.

Run context

Working memory

Task-level context for active agent work, handoffs, temporary investigations and pending decisions.

Trace

History

Decisions, derivations, superseded states, agent actions and verification events kept as a temporal audit trail.

Temporal memory

Keeps original, current, working and historical memory separate but linked.

Thematic contexts

Organizes memory by topic and tag so agents can work inside bounded domains.

Intercontext graph

Connects requirements, decisions, agents, shares, policies and events through queryable relationships.

Context packs

Builds portable, policy-checked memory packages for MCP, API, CLI and external agents.

Governed sharing

Shares context with provenance, safety previews, entitlements, access logs and revocation.

Marketplace substrate

Lets valuable context packs become listed, licensed and distributed with source and usage controls.

03 - api model

Use project-scoped endpoints as the official SPM contract.

SurfaceMethodEndpoint

Memory objects

Create project-scoped memory objects with schema, provenance, policy state and indexing.

POST

/v1/projects/{project_id}/objects

Hybrid search

Retrieve policy-filtered memory through hybrid, context or kind-based recall.

POST

/v1/projects/{project_id}/search

Bundles

Persist selected memory as a reproducible bundle with object refs and manifests.

POST

/v1/projects/{project_id}/bundles

Temporal events

Record original, current, working or history events with topics, tags and hashes.

POST

/v1/projects/{project_id}/temporal/events

Temporal state

Compare original memory, current state, working memory and historical tail.

GET

/v1/projects/{project_id}/temporal/state

Context packs

Generate injectable memory packages for agents, MCP, CLI and API consumers.

POST

/v1/projects/{project_id}/temporal/context-pack

Graph query

Traverse topics, tags, events, supersession and related context links.

POST

/v1/projects/{project_id}/temporal/graph-query

Memory triage

Classify incoming project context with the LLM-first Memory Agent and create or queue governed memory.

POST

/v1/projects/{project_id}/memory-agent/triage

Autonomous maintenance

Consolidate, promote, summarize or review-gate stale and conflicting memory.

POST

/v1/projects/{project_id}/memory-agent/maintenance/run

Maintenance reviews

Inspect risky maintenance operations before approving or rejecting project-memory changes.

GET

/v1/projects/{project_id}/memory-agent/maintenance/reviews

Conflict inbox

List conflict-gated maintenance reviews with assignment, severity and SLA state.

GET

/v1/projects/{project_id}/memory-agent/maintenance/conflicts

Maintenance diff

Compare the proposed maintenance operation with source memories, changed fields and conflict signals.

GET

/v1/projects/{project_id}/memory-agent/maintenance/reviews/{review_id}/diff

Review assignment

Assign a gated maintenance review, set severity, attach SLA and write assignment lineage.

PATCH

/v1/projects/{project_id}/memory-agent/maintenance/reviews/{review_id}/assignment

Maintenance policies

Schedule recurring LLM-first maintenance with confidence gates, scope and hash state.

POST

/v1/projects/{project_id}/memory-agent/maintenance/policies

Release readiness

Compute the commercial launch gates across demo data, trust, deployment, docs, visual QA and billing.

GET

/v1/productization/release-readiness

Product access request

Capture a public product access request with plan, deployment preference, urgency and privacy-preserving request signals.

POST

/v1/productization/access-requests

Access request inbox

Let owners and admins triage access requests from the private SPM console.

GET

/v1/productization/access-requests

Access request notifications

Inspect signed webhook deliveries to sales, Slack, CRM or email-gateway systems without storing raw destination URLs.

GET

/v1/productization/access-requests/notifications

Readiness export

Download a hash-verifiable ZIP with readiness, trust, deployment and visual QA evidence.

GET

/v1/productization/release-readiness/export

Marketplace

Discover governed context listings with provenance, safety and entitlement state.

GET

/v1/context-marketplace/listings

04 - mcp and cli

Context packs and review gates are the handoff format for external agents.

MCP

Expose context-pack, temporal-state, graph-query, maintenance review and marketplace import operations to agent tools.

CLI

Let builders script temporal state, maintenance policies, review gates, governance records, package export and verification.

API

Keep every operation project-scoped, authenticated, reviewable and auditable for production services.

05 - agent integration

Connect agents without duplicating memory.

SPM owns the memory infrastructure while agent tools request recall, temporal state, context packs, marketplace imports and MCP exports through the official contract.

Recall

Temporal state

Context packs

Maintenance reviews

Marketplace imports

06 - security

Governance is part of the product, not a later add-on.

Private tenant boundary

Role and scope checks

Temporal hash chains

Context pack verification

Source provenance

Safety previews

Entitlement logs

Retention controls

Legal holds

Provider budgets

BYOK direction

Audit exports

07 - packaging

Package SPM as infrastructure, SaaS and marketplace substrate.

Core Local / MCP

Builders and small agent teams

Local or small-team SPM with CLI, MCP, context packs and limited projects.

Team SaaS

Product and engineering teams

Hosted dashboard, agent workspace integrations, temporal memory, sharing and governance basics.

Business

Teams with governed agent workflows

Advanced permissions, audit logs, higher quotas, private context sharing and provider budgets.

Enterprise

Security-conscious organizations

SSO, private deployment, BYOK/data-residency direction, legal controls, SLA and support.

Marketplace

Context publishers and buyers

Listings, entitlements, licensing, access history and revenue-share-ready context distribution.

08 - deployment

Run a deployment preflight before copying code to a shared server.

Shared-host safety

The deployment CLI inspects the remote Linux host over SSH, detects existing containers and occupied ports, verifies Docker and Compose, and recommends localhost high-port bindings so SPM does not take over other apps.

preflight

spm deploy preflight --mode shared-host --host <server-ip> --identity-file ~/.ssh/id_2020_rsa --json

Treat a blocked preflight as a hard stop; treat warnings as operator work before DNS or reverse-proxy routing.