PKC Capture Experiment
Record what was tried, what was learned, and what it informs.
Process
- Resolve knowledge root (
pkc_common.py resolve-root). - Collect: title, hypothesis, method, results, conclusion, related code paths.
- Write
experiments/<slug>.mdusing template or:python3 "${CLAUDE_PLUGIN_ROOT}/scripts/pkc_capture.py" experiment \ --repo . \ --title "JWT vs session-cookie spike" \ --hypothesis "JWT will simplify horizontal scaling" \ --result "Both workable; JWT slightly simpler ops" \ --conclusion "Proceed with JWT" \ --informs user-authentication - Typed edges:
- Experiment → Feature/Design/Requirement:
rel: informs - Decision that followed → Experiment:
rel: originates_from(on the DecisionRecord)
- Experiment → Feature/Design/Requirement:
- Refresh
experiments/index.mdandlog.md. - Offer to capture a follow-on DecisionRecord via pkc-capture-decision.
Frontmatter essentials
type: Experiment
title: …
hypothesis: …
result: …
conclusion: …
status: completed # or running | abandoned
verified: true
links:
- target: /features/….md
rel: informs
Done when
- Experiment concept written with hypothesis + conclusion
- At least one
informslink when a target feature/design is known - Catalog + log updated