pce-memory-api

Structure software changes as Evidence Packs grounded with Law/Term.

1|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/CAPHTECH/claude-marketplace --skill pce-memory-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pce-memory-api
Source: https://github.com/CAPHTECH/claude-marketplace/tree/main/caphtech-plugin/skills/eld-ground-memory-collector/references/pce_memory_api.md
Command: npx skills add https://github.com/CAPHTECH/claude-marketplace --skill pce-memory-api

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reference for PCE Memory tooling including observe, upsert, and activate operations.

Quick Start

Use the documented API signatures to interact with memory store from your Claude workflow.

Frequently Asked Questions about pce-memory-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure changes as Evidence Packs in software development workflows?

Evidence Packs organize changes by grounding them with Law/Term within an Evidence-Loop Development cycle. The PCE Memory API provides observe, upsert, and activate operations to record and retrieve Evidence Packs from your memory store, enabling traceable change governance across feature development, bug fixes, and refactors.

What operations does the PCE Memory API provide for managing development changes?

The PCE Memory API offers observe, upsert, and activate operations to interact with your memory store. These operations let you query existing Evidence Packs, write new changes with grounding, and retrieve stored data to enforce minimal change, pure/IO separation, and traceable phase-based outputs.

How do I use the PCE Memory API to enforce change governance in my codebase?

Use the Memory API's documented signatures to store Evidence Packs that ground changes in Law/Term within your Evidence-Loop cycle. The API integrates with ADRs, link maps, and Evidence Ladder to enforce minimal change patterns and maintain traceable change records across your development workflow.

Can I apply PCE Memory API to bug fixes and refactoring in addition to new features?

Yes. The PCE Memory API applies across new feature development, bug fixes, and refactors. It covers the complete lifecycle—issue creation, sense/model/predict/change/ground/record loops, design, implementation, testing, telemetry, and documentation—with consistent change governance.

What does the PCE Memory store track within the Evidence-Loop Development cycle?

The pce-memory store tracks Evidence Packs grounded in Law/Term, capturing changes through sense/model/predict/change/ground/record loops. It maintains ADRs, link maps, and Evidence Ladder records to enforce minimal change, pure/IO separation, and phase-based outputs across your development process.