Skip to content
autocatalog

Knowledge graph

One index compiled from repository conventions. Every row keeps its source, confidence, and connections.

Loading map…
47 resources, 106 relationships and 5 need review.

Graph format autocatalog/graph-v1

47 resources

  1. statements

    collection:default%2Fdefault/statements

    Extracted from source.

    Read from fixtures/brownfield-repo/statements.ts:8

  2. Generate statement

    command:default/generate-statement@1.0.0

    Generate a customer's monthly statement

    Declared by its owners.

    Read from fixtures/brownfield-repo/commands/generate-statement/autocatalog.json

  3. Refund payment

    command:payments/refund-payment@1.0.0

    Give a customer their money back when an order is cancelled.

    Declared by its owners.

    Read from examples/federation/payments/commands/refund-payment/autocatalog.json

  4. Refund payment

    command:payments/RefundPayment@1.0.0

    Give a customer their money back when an order cannot ship.

    Declared by its owners.

    Read from examples/docs-demo/repos/payments-service/commands/RefundPayment/autocatalog.json

  5. Agent catalogs

    document:docs/agents

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

    Declared by its owners.

    Read from docs/agents.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  6. Brownfield resources

    document:docs/brownfield-resources

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

    Declared by its owners.

    Read from docs/brownfield-resources.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  7. CLI reference

    document:docs/cli

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

    Declared by its owners.

    Read from docs/cli.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  8. autocatalog and EventCatalog

    document:docs/comparison

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

    Declared by its owners.

    Read from docs/comparison.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  9. Cross-domain delivery

    document:docs/cross-domain-delivery

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

    Declared by its owners.

    Read from docs/cross-domain-delivery.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  10. Delivery

    document:docs/delivery

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

    Declared by its owners.

    Read from docs/delivery.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  11. The docs convention

    document:docs/docs-convention

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

    Declared by its owners.

    Read from docs/docs-convention.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  12. Drift gating in CI

    document:docs/drift-ci

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

    Declared by its owners.

    Read from docs/drift-ci.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  13. Events from Avro and protobuf

    document:docs/events%2Favro-protobuf

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

    Declared by its owners.

    Read from docs/events/avro-protobuf.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  14. Fields

    document:docs/events%2Ffields

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

    Declared by its owners.

    Read from docs/events/fields.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  15. Importing an existing catalog

    document:docs/events%2Fimporting

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

    Declared by its owners.

    Read from docs/events/importing.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  16. Events from JSON Schema

    document:docs/events%2Fjson-schema

    Passive discovery over the schema files already in a repository.

    Declared by its owners.

    Read from docs/events/json-schema.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  17. Events from autotel-message-contract

    document:docs/events%2Fmessage-contracts

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

    Declared by its owners.

    Read from docs/events/message-contracts.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  18. Events from OpenAPI

    document:docs/events%2Fopenapi

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

    Declared by its owners.

    Read from docs/events/openapi.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  19. Events from Rust, Go, Java and .NET

    document:docs/events%2Fother-languages

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

    Declared by its owners.

    Read from docs/events/other-languages.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  20. Events from Pydantic

    document:docs/events%2Fpydantic

    The same catalog, extracted from Python models.

    Declared by its owners.

    Read from docs/events/pydantic.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  21. Validation

    document:docs/events%2Fvalidation

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

    Declared by its owners.

    Read from docs/events/validation.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  22. Versioning

    document:docs/events%2Fversioning

    How versions are stored, ordered, and diffed.

    Declared by its owners.

    Read from docs/events/versioning.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  23. Events from Zod

    document:docs/events%2Fzod

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

    Declared by its owners.

    Read from docs/events/zod.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  24. Federation

    document:docs/federation

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

    Declared by its owners.

    Read from docs/federation.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  25. Introduction

    document:docs/introduction

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

    Declared by its owners.

    Read from docs/introduction.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  26. MCP for coding agents

    document:docs/mcp

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

    Declared by its owners.

    Read from docs/mcp.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  27. Writing a plugin

    document:docs/plugins

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

    Declared by its owners.

    Read from docs/plugins.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  28. Production operation

    document:docs/production

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

    Declared by its owners.

    Read from docs/production.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  29. Quick start

    document:docs/quick-start

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

    Declared by its owners.

    Read from docs/quick-start.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  30. Retiring a field

    document:docs/retire

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

    Declared by its owners.

    Read from docs/retire.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  31. Catalog rules

    document:docs/rules

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

    Declared by its owners.

    Read from docs/rules.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  32. Runtime evidence with autotel

    document:docs/runtime-evidence

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

    Declared by its owners.

    Read from docs/runtime-evidence.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  33. The company site

    document:docs/site

    One command builds one site from every enrolled repository.

    Declared by its owners.

    Read from docs/site.md

    Owned by Maintainers

    • id extracted
    • repository extracted
    • url extracted

  34. PaymentCaptured

    event:autocatalog%2Fpayments/payment.captured@2.0.0

    A card payment was captured.

    Inferred.

    Read from experiments/04-message-contracts/repos/payments-service/src/payments/__contracts__/PaymentCaptured.approved.txt:1

    • examples extracted
    • id declared
    • summary declared
    • version declared

  35. payments.refund-replies

    queue:payments/payments.refund-replies

    Inferred. A person should confirm it.

  36. ledger.dead-letter

    queue:rabbitmq-exchange/ledger.dead-letter

    Extracted from source.

    Read from examples/federation/infra/rabbitmq/definitions.json:14

  37. payments

    queue:rabbitmq-exchange/payments

    Extracted from source.

    Read from examples/federation/infra/rabbitmq/definitions.json:5

  38. ledger.dead-letter

    queue:rabbitmq/ledger.dead-letter

    Extracted from source.

    Read from examples/federation/infra/rabbitmq/definitions.json:32

  39. ledger.payments

    queue:rabbitmq/ledger.payments

    Extracted from source.

    Read from examples/federation/infra/rabbitmq/definitions.json:25

  40. autocatalog

    repository:autocatalog

    Repository inferred from the catalog layout.

    Inferred.

    At commit 4f8a70a762d1

  41. autocatalog-monorepo

    service:autocatalog-monorepo

    Inferred. A person should confirm it.

  42. billing

    service:billing

    Inferred. A person should confirm it.

  43. EmailService

    service:EmailService

    Service inferred from Event producer and consumer declarations.

    Inferred.

    Read from experiments/04-message-contracts/repos/payments-service/src/payments/__contracts__/PaymentCaptured.approved.txt:1

  44. LedgerService

    service:LedgerService

    Service inferred from Event producer and consumer declarations.

    Inferred.

    Read from experiments/04-message-contracts/repos/payments-service/src/payments/__contracts__/PaymentCaptured.approved.txt:1

  45. OrderService

    service:OrderService

    Inferred. A person should confirm it.

  46. PaymentService

    service:PaymentService

    Service inferred from Event producer and consumer declarations.

    Inferred.

    Read from experiments/04-message-contracts/repos/payments-service/src/payments/__contracts__/PaymentCaptured.approved.txt:1

  47. statement-worker

    service:statement-worker

    Inferred. A person should confirm it.

Datastore ownership
Who writes and reads each collection or table, from code and runtime evidence. An unassigned owner needs a team decision.
1 datastore
ResourceOwnerWritersReadersObserved accesses
statementsdefault/defaultUnassigned
autocatalog-monorepo
None identifiedNo runtime evidence
autocatalog