On your first action in this repo, follow the startup sequence in ROUTER.md before recommending or editing anything. It names the canonical files and the order to read them. Re-run it (or /pdda) when you switch tasks, resume a long session, or feel context has drifted.
See GUIDING-PRINCIPLES.md for the repo's north star — the goals and tradeoff lens these rules serve.
These apply to every response, plan, and change in this repo.
The first sentence says what changed or what the verdict is. Supporting detail comes after.
Name the assumption, tradeoff, and failure mode before a consequential edit. If the claim cannot be wrong, it is probably too vague.
Every consequential change gets a read on the shared scale: Easy / Costly / One-way door.
Do not report a win you did not verify. In this repo, utils/pdda/pdda.sh run is the main rail unless a narrower single check (utils/pdda/pdda.sh <check>) is more appropriate.
If a PDDA script is added, removed, or behaviorally changed, update the matching contract docs in the same change:
PROJECT/PDDA.mdutils/pdda/PDDA-INSTALL.md- any repo-facing startup docs that describe the shipped surface
This is the standalone PDDA source-of-truth repo. Favor changes to the document contract, install manifest, and shipped shell checks. Do not pull in unrelated runtime or product docs from other repos.
Update CHANGELOG.md at the end of a substantive iteration. PROJECT/PDDA.md owns the contract for what belongs there.
- The canonical PDDA contract lives in
PROJECT/PDDA.md. - The runnable install surface lives in
utils/pdda/pdda.sh(checks + runner),utils/pdda/pdda-doc-ready.sh(LLM layer), andutils/pdda/pdda-lib.sh(shared helpers). - The extraction contract lives in
utils/pdda/PDDA-INSTALL.md. ROADMAP.mdis this repo's pointer ledger, not a second plan body.PROJECT/PDDA-ACTIVITY.jsonlis runtime output, not install history to copy into target repos.