Status: Draft
{
"run": {
"id": "2026-04-20T09-10-00Z-workpads-core-dirty",
"mode": "dirty-test",
"target": "/abs/path/to/repo",
"tier": "core",
"profiles": ["shared-core", "software"],
"timestamp": "2026-04-20T09:10:00Z"
},
"summary": {
"pass": 0,
"fail": 0,
"partial": 0,
"na": 0,
"error": 0,
"blockingFailures": 0
},
"results": [
{
"ruleId": "BASICS-EVID-002",
"status": "fail",
"severity": "high",
"observed": "No standalone event schema artifact found",
"evidence": [
{
"type": "file-check",
"path": "/abs/path/to/repo",
"detail": "searched known schema locations"
}
],
"remediation": "Publish event-schema.md with compatibility notes"
}
],
"confidence": {
"level": "medium-high",
"rationale": "deterministic file checks + partial command checks"
},
"limits": [
"no exhaustive command fuzzing",
"no long-duration resilience test"
]
}Rendered markdown should include:
- verdict
- scope and method
- hard findings (by severity)
- strengths
- tier readiness snapshot
- remediation plan
- confidence and limits
critical: immediate blocker for requested tier claimhigh: major conformance risk; usually blocking in strict modemedium: meaningful gap; not always blockinglow: improvement opportunityinfo: contextual observation
pass: explicit evidence meets rulefail: explicit evidence contradicts or missing required behaviorpartial: some evidence exists but insufficient for full passna: rule not applicable for target mode/profileerror: evaluator failed unexpectedly
With --strict, treat:
failon mandatory rules as blockingerroron mandatory evaluators as blockingpartialon mandatory rules as blocking (optional default for v0 strict)
- JSON:
basics-report-<run-id>.json - Markdown:
basics-report-<run-id>.md - Summary:
basics-summary-<run-id>.txt