Use pnpm in northstar/web; npm breaks the lockfile
From 3 corrections: Hope, Priya, Sam
Learn and checkRules and skills
Your corrections become rules and skills.
Agents report what they meant to do, so the lessons in the actual work are lost. OrgX reads what happened, step by step, and drafts rules from corrections and skills from runs that held up. A person confirms what binds.
Compare what the agent reported with what OrgX read, then confirm the rule.
What the agent reported
“Added date-fns. Build passes.”
What OrgX read · 6 steps
- PlanAdding the date library.
- Commandnpm install date-fns
- Resultnpm warn: package-lock.json created next to pnpm-lock.yaml
- Correction“We use pnpm here. npm writes a second lockfile and breaks CI.”
- Change of coursepnpm add date-fns
- VerificationChecks pass.
What OrgX drafted Rule Skill Decision
Add a dependency in northstar/web
- pnpm add the package
- Run pnpm build
- Commit pnpm-lock.yaml only
From 4 runs that passed CI
Launch copy leads with the agency buyer
From ChatGPT, Hope. Confirmed by Hope.
- Read, not summarizedEvery command, edit, failure and correction, linked to its session.
- Skills from what workedSteps that held up across runs become a skill the next agent follows.
- You confirmOrgX proposes. Nothing binds the team until a person confirms it.
How it works
- OrgX reads each session your team runs.
- It drafts rules, skills and decisions with their sources.
- You confirm; every later session gets them.