v0.3.47 — company memory export test
Company memory export test
This release adds a runnable demo for testing whether operational/company memory can move between agents or vendors without depending on hidden model memory or private chat history.
Try it directly from the GitHub tag:
npx -y --package github:caioribeiroclw-pixel/pluribus#v0.3.47 pluribus demo company-memory-export-test --jsonExpected result: ok: true with a review-required export receipt that includes decisions, active constraints, exceptions, owners, source freshness, stale sources, and explicit omitted gaps.
Why this exists
Claude Tag, self-authored skills, MCP memory servers, and company-agent workflows are making persistent operational memory a real lock-in surface. The useful export test is intentionally boring: can another vendor/agent reconstruct enough from a neutral receipt to continue safely, while still seeing what was not exported?
Added
pluribus demo company-memory-export-test- Packaged fixture:
examples/company-memory-export-test/company-memory-export-receipt.json - Docs:
docs/company-memory-export-test.md - Tests and CLI wiring for the demo command
Verification
npm test: 71/71 passinggit diff --check: clean- GitHub-tag smoke passed with the command above
Distribution note
The npm package has not moved yet: pluribus-context latest is still 0.3.46. Use the GitHub tag install command above for this release until npm publishing is repaired.