Built for AI-Native Authorship
Most CMS products added "AI features" after the fact — a summarize button bolted onto a rich text editor. Carapace was designed the other way around: assume the primary author is often an agent, and build the interface an agent actually wants.
Tools, not a text box
An agent working on Carapace content doesn't scrape a web form. It calls typed tools — create_post, edit_post, diff, publish — each one validated against the same allowlist a human's edit would be. There's no special, looser path for automation.
- Every draft is inspectable with
diffbefore it ships - Every write is allowlist-checked, not just trusted because it's the bot
- Every publish and rollback is a real, attributable commit
Letting an agent write your blog isn't scary if every action it takes is the same reviewable, revertible action a person would take.
Draft locking
Because posts live on branches, two agents — or an agent and a human — can't silently clobber each other's edits. The lock is the branch itself, not a database row with a "checked out by" column.