New Plant Onboarding Runbook
Turned Rocky Raccoon's successful onboarding into the repeatable Abbey plant procedure.
Tags: Abbey Root • Plant Toolkit • Documentation
New Plant Onboarding Runbook
Summary
Rocky Raccoon’s onboarding did more than add another orchid to the site. It proved the complete path for creating a plant workspace, preserving its source photo metadata, replacing the scaffold with verified content, publishing safe derivatives, and closing the session cleanly.
That process now lives in the plant website runbook instead of in conversation history.
Accomplishments
- Added the
abbey plant newworkflow to the authoritative plant runbook. - Documented XMP caption correction, rename previews, and recoverable backups.
- Documented verified facts, honest unknowns, and scaffold-content completion.
- Added canonical photo and sidecar integrity checks.
- Added publication-manifest review and direct public metadata verification.
- Connected onboarding to the existing publish, site build, capture, review, and commit workflow.
Lessons Learned
A runbook should capture the checks that made a real process trustworthy, not just the commands that happened to succeed. For plant onboarding, that means distinguishing structural validity from publication readiness and verifying both preservation of private originals and safety of public derivatives.
Next Steps
- Use the documented workflow for the next new plant.
- Update the runbook only when normal use exposes another missing decision or safety check.