gaia-val-validate

To validate artifact claims against a codebase, provide the artifact path to trigger deterministic validation. It cross-references file existence, configurations, and structural claims with repository ground-truth to generate evidence-backed findings.

Codebase validation verifies factual claims about files and structures in an artifact against repository state. You need it for software compliance checks, code audits, and release readiness to ensure documentation accurately reflects the actual codebase.

Yes, you can verify non-binary file contents during a code audit. The validation process performs content verification for non-binary files, alongside path normalization and existence checks, to confirm artifact claims match repository ground-truth.

Cross-referencing artifact claims with memory ground-truth data requires loading memory context before validation. The process applies deterministic, forked-context validation to compare claims against loaded ground-truth, producing evidence-backed discrepancy findings.

Yes, there is a 40-file scanning cap when validating repository structures. This limitation ensures deterministic validation performance while performing path normalization, existence checks, and content verification across the scanned files.

Path normalization is essential when checking file existence claims because it standardizes path formats before validation. This ensures accurate existence checks and content verification when validating an artifact against the actual codebase structure.