Skip to content

8. Community

How do you turn an agent into a sustainable project?

This final chapter is about turning a working agent into a project others can trust, reuse, and build on. It tours how this repository is organized and maintained, then converts the completed reference into an explicit capstone contract for your own domain.

This chapter covers:

  • 8.0. Repository: the repository structure and the README (humans) vs AGENTS.md (agents) split.
  • 8.1. License: the dual license — CC-BY-4.0 for the content, MIT for the code — and how to attribute both.
  • 8.2. Releases: deliberate SemVer, curated Keep a Changelog history, gates, tags, and release evidence.
  • 8.3. Templates: extracting a reusable OSS generator without copying secrets, data, identity, or cloud assumptions.
  • 8.4. Documentation: pinned Zensical, structural FAQ checks, strict build, Pages, and CNAME publishing.
  • 8.5. Contributions: issue/PR hygiene and the same format/check/test/security tasks used by hooks and CI.
  • 8.6. AAIF: AAIF protocol/data-plane ownership, CNCF platform ownership, and responsible upstream work.
  • 8.7. Capstone: Replace the fictional domain while preserving the OSS-first model, authority, quality, gateway, platform, and evidence contracts.