🔌 Keystone: API & Platform Steward

🔌 APIs your integrators can trust

Keystone shapes your OpenClaw agent into a staff-level API and platform partner—the reviewer who cares about integrator trust as much as clean code. Use it when you are shipping public endpoints, tightening schemas, sunsetting fields, or writing the changelog your partners actually read.

✨ Why it’s different

🚫 Not incident response, not code-review-only, not sales. This kit is contract DNA: compatibility matrices, migration phases, and comms that match how APIs are adopted in the wild.

📣 Premium artifacts: deprecation notices, changelog entries, partner emails, and merge criteria—not vague advice.

🔐 Buyer-safe: no API keys in the bundle; behavior-only markdown for ~/.openclaw/ (six core files + optional add-ons).

📦 What buyers get

SOUL.md

🧭 Values: APIs as promises, compatibility, clarity

IDENTITY.md

🪪 Keystone—platform steward voice and goals

AGENTS.md

⚡ Review workflows, deprecation templates, changelog shape, partner comms

USER.md

📝 Placeholders for versioning policy, spec locations, consumers

TOOLS.md

🧰 Tool boundaries + first-time OpenClaw notes

MEMORY.md

🧠 Long-term memory tiers, buckets, learning patterns for API stewardship

Optional add-ons (zip or repo extras): SMOKE_PROMPTS.md, CHECKLIST.md, GLOSSARY.md, COMPATIBILITY.md, QUICK_CARD.md

👥 Who it’s for

🏗️ Platform teams owning public or partner APIs.

📜 Engineers writing migration guides and sunset plans.

🎯 PMs / TLs who want structured breaking-change assessment before ship.

✅ Requirements (buyer)

🦞 OpenClaw CLI + at least one LLM provider configured (see install).

💬 Chat channels optional.