vx-repo-contractv1.0.0

A platform engineering team runs the shared checker in CI to enforce the vx repo contract across all internal repositories. They pin the tooling checkout to a known revision and use the baseline profile with --fail-on error. This catches missing AGENTS.md, wrong-case justfiles, and invalid root artifacts before merge.

A maintainer of a community project adopts the vx repo contract to standardize contribution guidelines. They use the strict profile locally to find duplicate scripts and root-level temporary files. The AGENTS.md symlink rule ensures AI agent instructions stay canonical across derived files.

An engineering productivity group uses the checker to clean up root artifacts, deprecated files, and duplicate justfile recipes across a large monorepo. They run the strict profile and promote selected warnings to errors via --error-rule. This reduces tooling drift and improves developer onboarding.

A team integrating AI coding agents reviews repositories for agent instruction compliance. They verify that AGENTS.md exists and that derived agent files are either symlinks or carry the provenance marker. The vx-repo-contract skill provides the exact checker commands to validate these conditions.

In a regulated environment, a release engineer uses the vx repo contract checker as a mandatory gate before releasing artifacts. The strict profile with --fail-on warning blocks any deviation from the contract, ensuring traceable and reproducible repository structures. This supports audit requirements for build provenance.

The vx-repo-contract checker and shared contract are open source, but the maintainers offer paid support contracts for enterprises needing custom rule sets, priority bug fixes, and integration assistance. Revenue comes from annual support subscriptions and consulting hours.

A hosted service wraps the vx-repo-contract checker to provide dashboards, historical compliance trends, and team-level policy management. Customers connect their Git repositories and receive automated scans with actionable reports. Revenue is based on per-repository or per-seat monthly fees.

An enterprise bundle includes the checker, custom rule development, CI/CD pipeline integration, and training for platform teams. It is sold as an annual license with a fixed number of repositories and support SLAs. Revenue is generated from annual license fees.