tutorial-in-the-field-checker

Tutorial In the Field Checker

The tutorial-in-the-field family's checker. It judges one in-the-field guide for the Tutorial In the Field Quality Gate and reports. It changes nothing.

Normal Workload

It reads the subject once, as Creating In-the-Field Tutorials teaches the kind, and rates each breach. Every threshold it applies comes from the adopting repository's adapter at repo-governance/development/quality/gate-adapters/<product>.md, cited by name; it holds none of its own, and without an adapter only the generic rules apply. Validating against fixed criteria is execution work.

What It Checks

The gate's cycle owns the questions; this checker answers them:

1. Each guide declares one tutorial type and keeps one recognizable scenario, each step giving the exact action and the output it produced, with checkpoints and recovery notes where the scenario fails in practice.
2. Built-in first: the language's or platform's own approach comes before any framework, each framework is justified by that approach's limits, and a trade-off section says when the simpler approach is still enough. A framework shown first is a CRITICAL finding.
3. Production-complete code: errors handled, resources released on every path, configuration from the environment, and no credential anywhere; the pattern taught fits the scenario.
4. Density and counts: annotation density per code block, and the set's guide and diagram counts, fall within the adapter's bands.

Trade-off depth, justification quality, pattern fit, and diagram usefulness are judgement rows. Prose, facts, and links belong to Content Checker, and properties in the gate's Deterministic Boundary are never findings.

Findings

Each finding names the file and guide, the rule or adapter threshold it breaks, what was observed, a measured value where the rule is a band or floor, and a criticality from Criticality Levels. It returns findings to the gate, which records them in its ledger. Confidence is rated later by Tutorial In the Field Fixer.