Maintainers

Gathered from the owner each resource declares. Change a resource's owner and it moves.

Documents

---

29

• Agent catalogs

  The same idea applied to AI agents — what they call, what they cost, and what they actually did.

  docs
• Brownfield resources

  Discover datastore access, commands and services, then import ownership and registry contracts.

  docs
• CLI reference

  Every `ac` command, what it does, and the flags worth knowing.

  docs
• autocatalog and EventCatalog

  How the two tools relate, what each one starts from, and how to run them together.

  docs
• Cross-domain delivery

  What autocatalog enforces when work crosses a domain boundary, step by step, and what it leaves to people.

  docs
• Delivery

  How an event reaches each consumer, read from the broker configuration, checked in pull requests and proven against a test broker.

  docs
• The docs convention

  Every repository owns its docs/; one site aggregates them. This site is the proof.

  docs
• Drift gating in CI

  Fail the pull request that breaks a consumer, not the release that ships it.

  docs
• Events from Avro and protobuf

  Passive discovery over .avsc and .proto files, with the wire-format semantics kept intact.

  docs
• Fields

  Which events carry a field, which consumers it reaches, and where it disagrees with itself.

  docs
• Importing an existing catalog

  Bring in events from GitHub, AsyncAPI, or an EventCatalog project.

  docs
• Events from JSON Schema

  Passive discovery over the schema files already in a repository.

  docs
• Events from autotel-message-contract

  Approved message contracts become catalog events; the contract tests pin the bytes, autocatalog catalogs them and gates their drift.

  docs
• Events from OpenAPI

  Passive discovery over the OpenAPI specs already in a repository — webhooks and callbacks, not every endpoint.

  docs
• Events from Rust, Go, Java and .NET

  Write the schemas from a test with each language's own generator, commit them, and scan them like any JSON Schema.

  docs
• Events from Pydantic

  The same catalog, extracted from Python models.

  docs
• Validation

  What `ac validate` and `ac health` check, and how to make them fail a build.

  docs
• Versioning

  How versions are stored, ordered, and diffed.

  docs
• Events from Zod

  Define an event once in TypeScript; the catalog, graph and service pages derive from it.

  docs
• Federation

  One company catalog from catalogs each team owns, EventCatalog projects included, pinned to reviewed commits.

  docs
• Introduction

  One provenance-aware catalog, discovered by convention from the repositories you already have.

  docs
• MCP for coding agents

  Fourteen tools that let an AI coding agent query the catalog, ask what a change breaks, and draw the architecture in the conversation.

  docs
• Writing a plugin

  Teach ac scan and ac drift to read events from a format of your own.

  docs
• Production operation

  The trust model, artifact integrity, transactional publication, and crash recovery.

  docs
• Quick start

  One command from a repository with contracts/ and docs/ to a site.

  docs
• Retiring a field

  Whether you can remove a field or an event yet, consumer by consumer, with the evidence for each.

  docs
• Catalog rules

  Your own architecture checks, run by the drift gate on what each pull request changes.

  docs
• Runtime evidence with autotel

  The contracts say what a service promises; a snapshot from its tests says what it sent.

  docs
• The company site

  One command builds one site from every enrolled repository.

  docs