Backstage
Use checked-in catalog declarations to understand service context and ownership during review.
Read the catalog files
Proofline reads multi-document Backstage YAML from a configured root or declared paths at a pinned GitHub commit. A repository source explicitly selects which annotation keys to retain.
The catalog gives a review declared context about the service and the team responsible for it. Pinning the files keeps that context attached to the revision that supplied it.
Follow ownership back to its declaration
A shared library change can send a reviewer through several service repositories. Catalog ownership declarations help identify the teams responsible for those components, with the source file available to inspect.
Collection makes no Backstage server calls and follows no remote substitutions or links. Catalog ownership is declared metadata; it does not grant repository access or establish the live deployment topology.
Discuss your evidence source
Tell us where this source lives and which environment it describes. We can help establish the collection scope alongside your repository and cloud connections.
Get started with GitHub