Skip to main content

Learn and checkRules and skills

Correct an agent once. Every agent follows it.

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.

Start free See it work

Compare what the agent reported with what OrgX read, then confirm the rule.

  1. AgentTask: adding date-fns.
  2. Rannpm install date-fns
  3. Resultnpm warn: package-lock.json created next to pnpm-lock.yamlWhat broke
  4. MayaWe use pnpm here. npm writes a second lockfile and breaks CI.Issue
  5. Ranpnpm add date-fnsFix that held

Summary: “Added date-fns. Build passes.”Read: 3 sessions · 15 steps · 3 corrections

StandardMPS

Use pnpm in northstar/web; npm breaks the lockfile

Source: the same correction from three people · Owner confirms itForming · 0 of 3 sessions
CheckMPS

Uses pnpm, not npm

Source: what broke · Every later result is checked for itForming · 0 of 3 sessions
SkillMPS

Add a dependency in northstar/web

Source: the fix that held · pnpm add the package → Run pnpm build → Commit pnpm-lock.yaml onlyForming · 0 of 3 sessions

Proposed until a person confirms it. Nothing OrgX extracts is approved on its own.

  • 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

  1. OrgX reads each session your team runs.
  2. It drafts rules, skills and decisions with their sources.
  3. You confirm; every later session gets them.
See fixes other teams adopted

Try it on one real piece of work.

Start free