odylith-registry-validate

You validate registry contracts by running a validator against your component inventory to check required frontmatter and contract schemas, producing a report of deviations for remediation. This ensures registry consistency and defensible component boundaries.

A registry contract audit checks component inventories against defined schemas to guarantee required fields are present and consistent. You need one during cross-repo onboarding of new components to detect drift and missing contracts.

You check for schema drift by running cross-repo audits that compare registry entries against defined contracts. The validator detects missing contracts and deviations, then generates automated remediation guidance for engineering teams.

Yes, the registry validator supports onboarding checks for new components by enforcing required frontmatter and contract schemas. It audits component inventories to ensure completeness and consistency before components are added to the registry.

A registry validation report contains deviations found during schema checks of component inventories, along with automated remediation guidance. It highlights missing required fields and contract drift to help engineering teams fix issues quickly.

No dependencies are required to run the registry contract validator. It operates standalone to validate component inventory contracts, enforce required frontmatter, and produce deviation reports without external tools.