How Project0 works

Memory, commitment, retrieval, and the briefing before every response.

Most "AI infrastructure" stops at the model. Project0 starts before the model speaks and stays after the work is committed. Here is what actually happens, in order.

Memory architecture

How memory works in Project0.

Information moves down into permanence. Four tiers. One boundary.

Temporary
Session memory
Per-session only. Context window only. Gone when the session ends.
Short TTL. No persistence by design.
Boundary
Promote boundary
Private
Personal
Your notes, your agents, your context. Private.
Persistent store. User-scoped rules. Admin override available.
Mutable
Team
Collaborative. Mutable via supersession only. Ideas forming together.
Persistent store. Role-scoped ACL. Supersession chain visible.
Permanent
Institutional
The bible. Immutable. What the project actually is.
Append-only. KMS-signed. Authority + actor on every write.
Promote system

How a decision becomes permanent.

Promote is the line between thinking and deciding.

Human Agent Application Promote() Commitment boundary Every Promote declares: Who decided actor identity Under what authority human-led · HITL · autonomous With what evidence declared, not inferred Sealed decision record Immutable. Verifiable. Attributable. 0x9f7a3c8e4d4f129ab6e5c0a178b3f4d9 0x9f7a3c8e4d4f129ab6e5c0a178b3f4d9
Promote system

How Promote actually works.

The API contract behind every commitment event.

1
API call initiates commitment
Single endpoint, single contract.
2
Required fields validated
Actor identity, authority mode, evidence manifest, truth posture.
3
SHA-256 commitment hash generated
KMS-signed with non-exportable key.
4
Appended to persistent store
No update. No delete. Ever.
Every commitment hash is independently verifiable.
Retrieval system

How agents get the right context.

Not a raw dump. Precisely the right information.

Message comes in What kind of question is this? Text search Exact matches Semantic search Meaning matches Graph retrieval Related context Merge and rank results Agent responds with full context
Retrieval system

How retrieval actually works.

Classification and retrieval pipeline, in order.

1
Intent classifier (pre-inference)
Simple messages skip heavy memory. No wasted reads.
2
Session cache check
Short TTL. Cache hit means skip retrieval entirely.
3
Parallel retrieval across three engines
Text, semantic vectors, graph-augmented. Simultaneous.
4
Rank fusion
Weighted merge across all sources. Best context wins.
5
Cognitive preload assembled
Charter, memory, governance snapshot. Ready for inference.
Cognitive preload

What the agent knows before it speaks.

Every response starts with a structured briefing.

Cognitive Preload Assembled at inference time
Field 01
Project charter
What this project is, the goals, the constraints. The agent does not guess. It knows.
Field 02
Role and scope
What this agent is allowed to do and what it is not. Boundaries loaded, not inferred.
Field 03
Relevant memory
Pulled from team and personal tiers, filtered by relevance. Not everything. The right things.
Field 04
Governance snapshot
Current authority mode, active rules, constraints. The agent knows the rules before it acts.
Field 05
Recent decisions
What was promoted, what's pending, what was blocked. No re-proposing rejected ideas.
When a new person joins your team, you brief them. We do the same for agents, every single time.
What this unlocks

Why this matters.

One moment of friction. Eight operational unlocks.

For your team
Headline · Workforce
Agents as co-workers
Not chatbots. Accountable contributors with a commitment mechanism. They join the team, follow the rules, and leave a trail you can audit.
Onboarding
New human or new agent, nobody starts from zero. Ever.
Institutional knowledge
People leave, agents rotate. The project knowledge stays.
Decision intelligence
Structured data to learn from. Not just conversations.
For your partners and auditors
Headline · Defensibility
Auditability
Who decided, under what authority, with what evidence. Always. Every action sealed at the moment of commitment, independently verifiable years later.
Correction without destruction
Fix mistakes, keep the record. Supersede, never erase.
Brownfield ready
Works alongside your existing stack. No rip and replace.
Provable trust
Your competitors show Jira tickets. You show a verified decision record.

This is the substrate beneath every Project0 platform.

Talk to integration → See the proof →