Persistent project intelligence
How ACCPT turns session history into memory the next collaborator can use
Documentation records information. Project intelligence organises it into knowledge.
Capture the session
Every completed session ends in a structured receipt, not a raw transcript.
Extract the knowledge
The receipt is parsed: entities, decisions, risks and open questions are pulled out.
Store it two ways
Neither representation works alone — together they cover facts and meaning.
Knowledge graph
Explicit relationships — what depends on what, and why.
Vector memory
Semantic similarity — related discussions, even in different words.
Retrieve on demand
A context retrieval layer assembles what's relevant to the task at hand.
Rehydrate the next contributor
A new collaborator starts from an assembled context package, not from zero.
Requirement · ACCPT-PPI-001
Every session receipt must record
Objectives completed
Architectural decisions
Assumptions
Risks
Outstanding work
Files modified
References to supporting artefacts
Without PPI
Manually reads the README, architecture docs, build logs and past receipts.
With PPI
Retrieves relevant decisions, constraints and open issues automatically.
Both paths still end in the same Declaration of Understanding — only how it's prepared changes.