{"schema":"groundwork-plan/1","name":"tier-1","title":"Prototypes & landing pages","release":"b155517c3eaff44615027b9f0d74299d7138c775","audience":"1 person, weeks. Someone will ask: Nothing","instructions":["Work through steps in order. Each step is independent of the ones after it.","write-file: fetch source as plain text and write it verbatim to target, creating directories as needed. Do not reformat it, do not improve it, do not translate it.","merge-into: target already exists. Fetch source and merge it in without disturbing what is there. Never overwrite the file.","run: fetch source and run it as a shell command from the repo root.","convention: no file operation. Apply what source describes wherever targetNote says.","targetNote is for you to act on too: \"make it executable\" means chmod +x.","sha256 is the hash of exactly what source serves. Hash what you fetched before you write it. If it differs, the site has moved since this plan was generated: fetch the plan again from the same URL and start over. Never write content that does not match its step.","customise: this step is a template or a configurable check. Write it verbatim first, then make exactly the edits this field names and nothing else. A step without customise is never edited.","A step with customise is not done until you have made those edits. Say which values you set and what you set them from.","If a step needs something listed in needs and the repo does not have it, skip the step and say so. Do not install a framework to satisfy a check.","Do not invent a step that is not in this plan.","Steps carry the tier that introduced them, or the capability that did. That is provenance, not priority: a step from tier 1 is as required as a step from tier 4, and a step a capability added is as required as either.","If the repo already has a working version of a step, leave it alone and say so. Re-running a plan is expected."],"prerequisites":[],"steps":[{"id":"constitution","title":"Shared project instructions","tier":1,"action":"write-file","source":"https://ntent.app/r/f/constitution","sha256":"4ad91e85a752a81387840681f5da12246530202cb4d9e9170eb40621324e8ebc","target":"AGENTS.md","targetNote":"point CLAUDE.md at it with a one-line @AGENTS.md import","customise":"It is a template. Replace every <angle bracket>, delete the sections marked for tiers above yours, and cut any row of the enforcement table whose command this repo does not have.","why":"Everyone inventing their own conventions, and every assistant inventing a different set again.","enforcement":"review","verify":"Ask an assistant \"what are the rules in this repo\" and it answers from the file."},{"id":"symlink-claude","title":"Shared instructions for coding agents","tier":1,"action":"run","source":"https://ntent.app/r/f/symlink-claude","sha256":"390916ef5802ea148badbf0e934bd6a3ba6c140408f2e2a3cbd6ea1e3146859a","why":"2 rule files that disagree, because one tool reads CLAUDE.md and another reads AGENTS.md.","enforcement":"none","needs":["AGENTS.md"],"verify":"Run it twice: the second run says there is nothing to do. Then start a session and ask the assistant to name a rule that only exists in AGENTS.md. In Claude Code, /context lists CLAUDE.md under Memory files. Copy a line of AGENTS.md into CLAUDE.md and run it again: it names that line and leaves it where it is."},{"id":"pre-commit","title":"Pre-commit checks","tier":1,"action":"write-file","source":"https://ntent.app/r/f/pre-commit","sha256":"93626e41aa0df823c263ceec1b231b50fe409d79a36a28d1b5b4c54f233d1f6a","target":"scripts/git-hooks/pre-commit","targetNote":"make it executable","why":"A mistake caught an hour later on the build server, after someone has already spent time reviewing it. This catches it on your machine, before the commit.","enforcement":"gate","verify":"Stage a file that fails a check this tier installs and the commit is refused, naming the check and the fix. At tier 1 that is check-env: add a variable to the env schema and not to .env.example. The hardcoded-colour case needs the tier 2 lint rules."},{"id":"hooks-path","title":"Git hook setup","tier":1,"action":"merge-into","source":"https://ntent.app/r/f/hooks-path","sha256":"7155c50ee73ae905e6fd1104dca859559de83208a86cb4fd968472d31268a728","target":"package.json","targetNote":"inside the \"scripts\" block","why":"Store hook setup in git so every contributor and coding agent runs the same checks.","enforcement":"none","verify":"Run pnpm install, then `git config core.hooksPath` prints scripts/git-hooks. A fresh clone gets the same answer with no manual step. Leave .git/hooks alone: it may hold hooks somebody else installed."},{"id":"check-env","title":"Environment variable checks","tier":1,"action":"write-file","source":"https://ntent.app/r/f/check-env","sha256":"1930b023e3cf1f54d9c0cabc5720bc9aa5509b10d6d1d9ae05b9212064ba56ad","target":"scripts/check-env.mjs","customise":"Point CONFIG.schemaFile at this repo’s env schema, CONFIG.exampleFile at its example file, and CONFIG.sourceDirs at the directories it keeps source in, if they are not src/env.ts, .env.example and src. The pre-commit hook reads those three back out of the file, so moving them keeps the gate wired.","why":"A setting the app needs that is missing from .env.example, so someone who downloads the repo cannot start it and has no idea why. Also the reverse, and code that reads process.env directly instead of through the schema.","enforcement":"gate","verify":"Add a variable to the schema, do not add it to .env.example, and the check names it."},{"id":"decisions","title":"Decision log","tier":1,"action":"write-file","source":"https://ntent.app/r/f/decisions","sha256":"64d083971ed620984d7f0d0bb99d59b52982caf8d703764dc23f9218c8d80e5b","target":"DECISIONS.md","customise":"The first entry is an example from a billing app: delete it. Then write the decisions this project has actually made, one entry each, and label any whose source is memory rather than a thread or a call as \"(from memory)\". A fresh project may have none yet, and a file with only the template entry in it is correct.","why":"The same decision being re-made in month 6 because nobody remembers the reason for the first one.","enforcement":"review","verify":"Every entry names a real decision, who agreed it and when. Nothing in the file is invented, and an entry reconstructed from memory says so."}],"finally":["Run the verify line for each step you completed.","For a gate step, running the verify line means having watched its probe turn it red first — the red gate.","Write groundwork.manifest.json at the repo root in the shape under manifest, with this plan's release, every step you installed with its sha256, every step you skipped with the reason, and every customise edit you made.","Report a list: what you installed, what you skipped, and the reason for each skip.","Do not report success for a step whose verify line you did not run."],"manifest":{"target":"groundwork.manifest.json","why":"So the next run, and the next person, can tell which release this repo is on, what was installed, what was skipped and why, and what was edited on purpose. Merge into it if it exists: replace the entries for the steps you touched and leave the rest.","shape":{"schema":"groundwork-manifest/1","release":"b155517c3eaff44615027b9f0d74299d7138c775","plan":"tier-1","on":"<today, YYYY-MM-DD>","installed":[{"id":"<step id>","target":"<step target>","sha256":"<the sha256 from the step>"}],"skipped":[{"id":"<step id>","reason":"<the need this repo does not have, or \"already present\">"}],"customised":[{"id":"<step id>","edits":"<what you set, and what you set it from>"}]}}}