# Output format

Crosscheck uses semi-structured Markdown: stable headings and labeled bullets,
but readable prose over rigid JSON.

## Runner capability report

```markdown
# Runner capabilities

## Prose Complete harnesses

### <harness name>

- Status: available | unavailable | uncertain
- How discovered:
- Help inspected:
- Model-list command inspected:
- Notes:

## Runners

### <runner name>

- Status: available | unavailable | skipped | uncertain
- Prose Complete harness:
- Command:
- Invocation profile:
- Help inspected:
- Model-list command inspected:
- Safety classification:
- Gaps:

## Candidate model roster

### <exact candidate model ID>

- Prose Complete harness:
- Runner:
- Invocation profile:
- Provider/gateway:
- Model family:
- Generation:
- Variant:
- Availability: listed | user-pinned | uncertain
- Evidence:
```

## Lane report

```markdown
# lane-1

- Status: active | skipped | failed
- Runner:
- Invocation profile:
- Model target:
- Model family:
- Focus:

## Findings

### F001

- Claim:
- Location:
- Evidence:
- Impact:
- Confidence:
- Suggested fix direction:
- Uncertainties:
- Assumptions:

## Coverage Notes

## Non-findings / rejected concerns
```

## Candidate ledger

```markdown
# Candidate Ledger

## C001

- Source lanes:
- Claim:
- Location:
- Evidence:
- Proposed severity:
- Proposed confidence:
- Related candidates:
- Uncertainties:
- Assumptions:
```

## Lane plan

```markdown
# Lane plan

## Reviewer lanes

### lane-1

- Status: active | skipped
- Runner:
- Invocation profile:
- Model target:
- Model family:
- Focus:
- Safety class:
- Validator invocations:

## Validator invocations

### validator-1

- Covers reviewer lane:
- Runner:
- Invocation profile:
- Model target:
- Model family:
- Workspace copy:
- Reused validator profile: yes | no
```

## Validation report

Allowed verdicts: `accept`, `reject`, `weaken`, `needs-human-check`,
`duplicate-of`, and `out-of-scope`.

```markdown
# Validation report

## C001

- Verdict:
- Validator evidence:
- Reasoning summary:
- Confidence adjustment:
- Notes:
```

Novel validator concerns go under `Possible follow-up`, not into findings.

## Final review packet

```markdown
# Crosscheck

## Summary

## Findings

### F001: concise title

- Severity:
- Confidence:
- Candidate IDs:
- Source lanes:
- Validator status:
- Evidence:
- Suggested fix direction:

## Needs human judgment

## Rejected or downgraded candidates

## Coverage

- Reviewed workspace:
- Runners discovered:
- Lanes active/skipped:
- Validator invocations planned/run:
- Skipped runner reasons:
- Model families represented:
- Execution mode:
- Guardrail caveats:
- Validator mode/degradation:
- Safety violations:

## Limitations

## Suggested next steps
```