chitin-chronicle

1. Add to Boot Sequence

Add this line to your AGENTS.md startup section:

bash /home/aaron/.openclaw/workspace/skills/chitin-chronicle/editorial/boot-check.sh

This shows editorial state every time you wake up.

2. Before Publishing Anything

# Check if safe to publish
node /home/aaron/.openclaw/workspace/skills/chitin-chronicle/scripts/editorial.js check "day-14" "substack"

If there's a conflict or it's already published, you'll see an error.

3. Claim Your Work

# Claim before drafting
node /home/aaron/.openclaw/workspace/skills/chitin-chronicle/scripts/editorial.js claim "day-14" "publish" "substack"

Other agents will see this claim and won't duplicate your work.

4. After Publishing

# Record the publication
node /home/aaron/.openclaw/workspace/skills/chitin-chronicle/scripts/editorial.js publish "day-14" "substack" "https://chitin.substack.com/p/day-14" "Day 14: Title Here"

This:

"CONFLICT: another agent claimed this"

Someone else is working on the same content+channel. Options: 1. Wait for their claim to expire (2 hours) 2. Coordinate directly (Telegram/Discord) 3. Work on a different channel

"Already published"

This content+channel combo is in the ledger. If you want to republish: 1. Use a different content-id (e.g., "day-14-v2") 2. Or manually edit ledger.json (not recommended)

Git commit failures

If you see git errors: 1. Ensure the editorial/ directory is in a git repo 2. Run cd editorial && git init if needed 3. Check git is configured (git config user.email)

The tool silently ignores commit failures, so operations still work.

Boot script shows nothing

If boot-check.sh produces no output: 1. Check the script is executable (chmod +x) 2. Verify JSON files exist (ls editorial/) 3. Run manually: bash editorial/boot-check.sh