🧱 rc-init — Ritual Bootstrap

The rc-init.sh script creates the skeletal folder structure and placeholder files required for a new Rotkeeper deployment.

This script is typically run once, or when reanimating a collapsed tomb structure. It can be safely run multiple times (idempotent).

📁 What It Creates

• bones/, bones/logs/, bones/archive/, bones/reports/, bones/templates/
• home/, home/assets/, home/content/rotkeeper/
• output/

It also ensures the following exist: - bones/manifest.txt - render-flags.yaml

🔁 Behavior

• Can be run repeatedly without error
• Logs are saved to bones/logs/rc-init.log. All stdout and stderr are captured.
• Errors from rc-expand.sh or rc-render.sh will cause a non-zero exit and be captured in the log.
• Exits 0 on success, 1 if required tools or permissions are missing

🏁 Flags

- `--help`: print usage text and exit
- `--verbose`: print log entries to terminal
- `--dry-run`: simulate setup without creating files

🔗 Related Rituals

• rc-expand.sh — generates content stubs
• rc-render.sh — renders output after structure is seeded

🪦 Limericks

🧪 Usage Examples

Run from the root of your Rotkeeper repo:

bash bones/scripts/rc-init.sh

Or invoke through the main dispatcher:

./rotkeeper init

All output is logged to bones/logs/rc-init.log.

Use this at the beginning of any new tomb cycle or prior to reseeding from archive.

🗂️ Folder Layout Preview

rotkeeper/
├── bones/
│   ├── archive/
│   ├── logs/
│   ├── reports/
│   └── templates/
├── home/
│   ├── assets/
│   └── content/
│       └── rotkeeper/
├── output/
├── render-flags.yaml
└── bones/manifest.txt

⚠️ Notes & Caveats

• If bones/manifest.txt already exists, it will not be overwritten
• Does not clone or fetch any default templates — only prepares the structure
• Won’t run expand or render unless explicitly chained
• Errors are trapped and logged via trap_err. Review rc-init.log for troubleshooting.