PUKNOWLEDGE / MCP / 0.4.0 ALPHA
Let the next session
continue the right work.
Keep the current task, sources, revisions and approval boundaries outside chat memory. Change sessions or agents, then verify before continuing.
- Local-first
- Apache-2.0
- Skill in preparation

01 / WHY IT EXISTS
Long projects fail in
the gaps between sessions.
The real risk is an old decision becoming current direction, a candidate becoming an approved fact, an untraceable source revision, or context silently crossing project boundaries.
02 / SYNTHETIC WORKFLOW
One recovery. Three visible boundaries.
These panels use public synthetic fixtures. They are not private-project screenshots or replicas of a host UI.
03 / WHAT IT MANAGES
Manage complexity.
Keep decisions yours.
PuKnowledge is a workbench, not another model. It manages how agents use project material reliably.
Task continuity
Restore the current task, stage, next step and exact revision.
Sources & evidence
Connect conclusions to concrete sources, fingerprints and revisions.
Candidate vs approved
Keep working snapshots, candidates and approved truth separate.
Controlled writes
Preview first, then save with a baseline, fingerprint and idempotency key.
04 / HOST EVIDENCE
Protocol support and host evidence, kept separate.
These host results are maintainer-run calls using 0.3.3 and synthetic projects. They do not establish all 0.4.0 features, independent-user validation or compatibility with every host version.
05 / INSTALL LOCALLY
Your projects stay
in your environment.
Requires Python 3.11 or newer. This is a 0.4.0 Alpha release candidate. The commands below pin that candidate commit; a public GitHub Release has not been created yet.
Read full installation guide ↗git clone https://github.com/pulapulapin/pu-mcp.git
cd pu-mcp
git checkout --detach 4668a868059dbddd4982fc9c99b8440ebe248692
python3 -m venv .venv
.venv/bin/python -m pip install -e .Installation does not scan project content. You explicitly register a directory and project ID during initialization.
06 / HONEST LIMITS
It knows what was delivered.
It does not pretend to know everything.
READY means selected sources were delivered as agreed. It does not prove truth, completeness or approval.
Manuscripts, Canon and official material remain project files; the database manages state, relationships and versions.
The current product targets a single user and trusted local workspace, not multi-tenant SaaS.
Built for work that lasts weeks or months and cannot tolerate silent changes to project truth.