Case

I inherited a half-built vibe-coded app

Onboarding reads the code and drafts the solution's design from it, for people to confirm before anything binds.

What happened

You took over an app built quickly with agents. There are no requirements and no design, just code.

Code shows what the app does, not what it should do. An agent that changes it has nothing to check against.

Runs onboarding as the "Onboard <solution>" initiative (with its demand), started with /corpole:onboard: a quick baseline, then module by module, one repository at a time.
Writes what it finds in the code, documents and tests as design drafts of that repository's component (modules become TDR drafts; behaviour FDR, rules BDR, qualities NFDR), never as binding records. Objectives and needs stay requirement drafts.
Guards modules nobody has reviewed yet: the agent asks first (advisory) or waits (enforced).

Run /corpole:onboard in each repository and review the drafts on the onboarding page.
For each draft choose Confirm as the design, Wrong behaviour → defect, or Reject.
Leave onboarding when the maturity checks are met; the Onboard initiative closes once its work is done, and new work goes to your next initiative.