Tutorial · Published 26 August 2026
Deploying the Lycato founder core from source
A production-minded walkthrough for initialization, imports, review policy, backups, cockpit access, and hosted-beta boundaries.
Build and initialize
Install the pinned workspace, build every package, initialize a new company repository, and run the doctor before importing real data. Keep the repository private and put vendor tokens in the documented secret boundary.
pnpm install --frozen-lockfile
pnpm build
node apps/cli/bin/run.js init
node apps/cli/bin/run.js doctorDefine review authority
Name owners, reviewers, risk tiers, protected paths, and which adapters may write proposals. Start with manual review for every external effect.
Run a demo proposal through approve and reject and inspect its source links plus Run Log.
Import and reconcile
Connect one vendor at a time, inspect staged data, resolve conflicts, and commit the resulting canonical record. Never treat an adapter response as an executable instruction.
Run obligations and finance views against the source files.
Prove recovery and boundary
Create a backup, restore it to a clean location, compare hashes, and start the cockpit under the intended authentication mode. Test failed writes and merge conflicts.
If using the hosted beta, document which formation, mail, domain, billing, and Operator features remain disconnected.
Production checklist
- Verify Founder ownership against the deployed environment, not a screenshot.
- Verify Proposal before effect against the deployed environment, not a screenshot.
- Verify Attributable Run Log against the deployed environment, not a screenshot.
- Verify Testable handback against the deployed environment, not a screenshot.