add-harness-component

To add a new layer to an existing project, use a harness add command to scaffold the necessary files. The integration validates against architectural constraints and dependency rules to prevent layer boundary conflicts.

Scaffolding a new component requires updating governance documents like harness.yaml and AGENTS.md. This enforces architectural governance by validating the new component against existing project constraints during the phase-based workflow.

Harness integration validation checks new code components against dependency rules and architectural constraints defined in harness.yaml. It updates governance documents and verifies the integration results before deployment to ensure no conflicts.

Yes, adding new documentation or skills requires an initialized harness project with no conflicting dependencies. The workflow validates against existing harness.yaml configurations before scaffolding the new elements.

Harness scaffolding supports adding layers, documents, components, or skills to an existing project. It determines what to add, collects requirements, and validates each element against dependency rules to ensure safe integration.

Updating AGENTS.md and harness.yaml enforces governance by recording the new harness element and its dependency constraints. This validation process prevents architectural conflicts and maintains project integrity during integration.