validate-upstream

Automate upstream documentation validation by running deterministic assertions against official sources to check accuracy and deprecation status. This process requires a project-root directory for local file access and an assertion engine to execute the validation checks.

Layered validation is a structured review process that supports L0, L1, and L2 project layers to comprehensively check documentation correctness. L1 specifically runs deterministic assertions to evaluate accuracy and identify deprecation status against upstream sources.

Validate specific documentation by providing a unique slug identifier to the validation engine. This targets individual documents at the project root, running the necessary assertions to verify their accuracy and compliance against the official upstream documentation.

Yes, an assertion engine is required to execute the validation checks against upstream documentation. It processes the deterministic assertions that verify whether your local project files maintain accuracy and reflect the correct deprecation status.

Automatically check documentation deprecation status by running Layer 1 deterministic assertions against upstream official sources. This validation ensures your project files accurately reflect current deprecation statuses without requiring manual review.

Deterministic assertions provide Layer 1 validation for accuracy and deprecation status but require a project-root directory for local file access. They may not cover nuanced compliance checks without properly configured assertions for each specific upstream source.