puda-memory
Puda Memory
Goal
Maintain project.md as the source of truth for each project: protocol links, and a chronological history so runs are reproducible and auditable.
CRITICAL: Persist all project-related state so runs are reproducible and auditable.
Each project folder has project.md as the single place to record everything about that project for long-term memory. Paths below are relative to the project folder (which contains protocols/).
When to Update
- After creating a protocol file
- After updating or deriving a new protocol
- After every protocol run
What to Record in project.md
- Protocols: Use explicit markdown links to protocol files under
protocols/. In the "Protocols" section, list each as[<protocol_id>](protocols/<protocol_id>.json)with an optional short description after the link (e.g.[<protocol_id>](protocols/<protocol_id>.json) — <summary>).
More from pudap/skills
puda
Setup puda project, CLI installation, and project/experiment structure. Use when initializing a Puda project, puda experiment, or when updating skills is needed
29puda-protocol
Protocol creation for PUDA. Use when doing anything related to PUDA protocols
29puda-database
Query the puda database using SQL and the puda CLI. Use when users need to inspect schema or run SQL commands
28puda-report
Use this skill when generating reports on PUDA experiments. Data analysis, plotting graphs, extract data and hashing of data to create an experiment report.
28puda-edge
Creating an edge client to integrate any machine into PUDA. Use when scaffolding a new machine edge service, writing a machine driver, or setting up the NATS-based communication layer for a machine
28puda-data
Extract, hash, export, and report on PUDA experimental data. Provides data provenance through SHA-256 hashing. Supports multiple devices (first, biologic) and measurement types (CV, OCV, CA, PEIS, GEIS).
28