Project memory for AI agents

Project memory that agents can actually use.

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.

SPM context packverified

Requirements

Original memory

Truth

Current state

Run context

Working memory

Trace

History

Query

topic:release-readiness tags:mcp,agent

Graph

requirements, current state, policy, handoff

Injection

MCP, API, CLI, governed share

provenance hash
policy decision
entitlement log

SPM gives agentic teams a durable memory layer for real project work: temporal context, trusted handoffs, governed sharing and reusable context assets.

Built for long-running agent work where requirements, decisions and current state must survive across tools, teams and runs.

Designed to make context portable without losing provenance, safety policy, access history or commercial rights.

Product model

SPM organizes memory by time, topic, graph and trust.

The product value is not more storage. It is continuity: agents can distinguish original requirements from current truth, working notes from history and reusable context from private source data.

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.

Workflow

From scattered project knowledge to injectable agent context.

01

Capture

Ingest requirements, decisions, code context, policies, run logs and source material with provenance.

02

Structure

Separate memory by temporal layer, topic and tag, then connect related events through graph relationships.

03

Package

Generate context packs that include only the memory a task, agent or team workflow needs.

04

Inject

Deliver context to MCP tools, API consumers, CLI workflows or external agents.

05

Govern

Verify hashes, enforce policies, inspect access logs, revoke entitlements and preserve audit trails.

Use cases

Built for agent workflows with real project stakes.

SPM is strongest when memory must be queried, verified, injected and governed across more than one run or tool.

Coding agents

Keep requirements, architectural decisions, current state and active task context aligned across runs.

Agent product teams

Offer agents a controlled memory substrate instead of relying on chat history or oversized prompts.

Consultancies

Package reusable project knowledge as governed context packs for client delivery and support.

Regulated teams

Preserve source, access, retention, legal hold and verification data around every memory handoff.

Deployment options

One memory product, multiple deployment paths.

  • Runs locally for builders who want private project memory beside their agent tooling.
  • Scales into a hosted team console with projects, quotas, invoices and governance trails.
  • Supports private deployment patterns for organizations with stricter data boundaries.
  • Turns governed context packs into marketplace-ready assets with provenance and entitlement logs.

Trust layer

Governance is part of the memory object, not an afterthought.

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

Commercial packaging

Deploy SPM where project memory needs to live.

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.

Next step

Evaluate project memory against a real agent workflow.