MyEzAI
ModelOps Demo
Public showcase
No login · private visitor sandbox · synthetic data
Model repo
Reset
Repository
VALIDATION-REPORT.md
Azure DevOps Demo Models · main
VALIDATION-REPORT.md
VALIDATION-REPORT.md · 1,182 bytes · read-only public source view
Back to folder
VALIDATION-REPORT.md
markdown
# Demo Model Repository — Validation Report Prepared: 2026-08-13 (America/Toronto) ## Catalogue coverage - 10 model definitions - 9 industry categories - 6 implementation technology families - 10 server-owned safe execution engines - Synthetic data and example code only ## Checks passed - Catalogue and all manifests parse as JSON - Required catalogue and manifest fields are present and consistent - Model keys, parameter keys, input keys, and output keys are unique - Every model includes representative source, sample configuration, sample inputs, expected-output documentation, PowerShell launcher, and Bash launcher - Every manifest exposes CSV and JSON outputs with safe relative paths - Every referenced sample input exists - Catalogue engine keys exactly match the universal runner allowlist - No credential-shaped values, merge markers, hidden control characters, or generated build folders - Python files compile and Bash launchers pass syntax validation ## Execution result `tools/smoke_all_models.py` completed all 10 models successfully. Each run produced CSV, JSON, and log artifacts; the VBA modernization model produced its additional assessment artifact.
Confirm action