Contract Governance

Documentation Map

• Overview

• Quick Start

• Installation

• Configuration

• Operations

• Troubleshooting

• Release Notes

• Compatibility

• Architecture

• API Reference

• Security

• Integrations

• Capabilities

• Data Model

• Roadmap

• Project Plan

• Contract Governance

• OSS Inventory

• Channel: latest

• Source repo: JaddaHelpifyr/jhf-shuttle

Contract Governance

This page summarizes how jhf-shuttle handles contract governance without creating competing truth.

Repo-Owned Truth

jhf-shuttle owns and versions:

• its CLI and optional API surfaces
• its runtime stack contract
• its repo-local projection/application validation helpers
• its QA-facing feature registry
• its runtime verification and evidence scripts

Consumed Truth

jhf-shuttle consumes the following truth read-only:

• Fabric contract families, registry, matrix, schemas, and readiness surfaces
• OpenClaw environment/runtime materialization
• upstream n8n release and compatibility signals

Governance Rule

If a contract family is Fabric-owned, jhf-shuttle may validate against it, materialize local evidence around it, and document how it is consumed. It must not create a second closure/lifecycle truth for that family.

Verify Paths

• python scripts/run_fabric_contract_governance_checks.py
• python scripts/check_n8n_projection_contract.py
• python scripts/check_n8n_application_contract.py
• python scripts/run_release_matrix_checks.py

Related Documents

• Feature Registry (docs/MODULE_FEATURES.md)
• Fabric Tool Profile (docs/FABRIC_TOOL_PROFILE.md)
• Runtime Stack Contract (docs/RUNTIME_STACK_CONTRACT.md)
• Overview

AGPLv3. Learn more at helpifyr.com.