jarvis-validate

Validate JaRVIS data directory health by running automated checks across journals, memories, and identity fields to enforce required frontmatter, section presence, and table structures. The scripts surface formatting issues and guide fixes to prevent broken data entries.

Broken memories or journals in a JaRVIS project are caused by missing required sections, malformed entries, and invalid version formats. Validating the data directory identifies these formatting issues and enforces required frontmatter to prevent data corruption.

Yes, you can run JaRVIS data validation in CI pipelines to ensure artifacts stay healthy and consistent. Execute the included validation scripts against your JaRVIS directory to automate health checks and catch missing sections before deployment.

JaRVIS validation checks both Consolidated and Recent memories along with journals, identity keys, and growth logs. It enforces required frontmatter, section presence, table structures, and version formats across the entire data directory.

The best way to fix malformed identity entries in JaRVIS is to run the validation workflow, which surfaces specific formatting issues and provides guidance on fixes. It enforces required frontmatter and section presence across identity fields.

Automated JaRVIS data integrity checks are limited to validating structural formatting, required frontmatter, section presence, and table structures. They enforce version formats and guide fixes but apply only to artifacts within the JaRVIS data directory.