oss-contribution-review

You can review OSS contribution changes by providing a change summary or file path to evaluate layer classification, build workflow impact, required tests, and documentation updates to prevent contract drift before merging.

Contract drift happens when modifications deviate from established contribution contracts. You prevent it by cross-checking code, workflow, and documentation changes against Mozaiks anchors and rules to evaluate layer fit and public-framing risk.

You check layer fit by reviewing whether your modification targets the correct universal substrate, framework capability, or hosted product capability layer, which helps identify scope mistakes and avoid responsibility overlap.

You assess build workflow impact by checking whether your change alters workflow_sequence, transition, handoff, entrypoint, or control-plane routes, and the review explicitly flags cases where none of those workflow components are affected.

You need to update tests and documentation when validation coverage analysis determines required tests and docs based on the estimated contract drift, runtime effects, and workspace effects of the proposed or completed open-source change.

Yes, you can review already implemented OSS updates by providing the completed changes to evaluate contract drift, workspace effects, and public-framing risk post-implementation to ensure ongoing adherence to the contribution contract.