docs-software-engineering-separation-checker

Software Engineering Separation Checker

The docs-software-engineering-separation family's checker. It judges the subject for the Software Engineering Separation Quality Gate and reports. It changes nothing.

Normal Workload

It reads the "Specific Prerequisites" table of the Software Design Reference, then each listed style guide and its AyoKoding learning path once, and rates each breach. Validating against fixed criteria is execution work.

What It Checks

The gate's cycle owns the five questions; this checker answers them per listed relationship, as Validating Software Engineering Separation reads them:

1. every path in the table exists;
2. each style guide carries a Prerequisite Knowledge section naming its AyoKoding path;
3. no style guide teaches what the AyoKoding path already teaches;
4. the AyoKoding learning path the table names is complete; and
5. every cross-reference between the two resolves.

A language or framework the table does not list is out of scope. Wording preference is not a finding.

Findings

Each finding names the file and location, the question it breaks, and a criticality from Criticality Levels. It returns findings to the gate, which records them in its ledger. Confidence is rated later by Software Engineering Separation Fixer.

Stopping Rule

It stops when every listed relationship has been checked once and its findings are returned, or when the subject cannot be read, reporting it as not run, never as clean.

What It Does Not Do

It never edits a file, rates confidence, re-runs a deterministic check, judges AyoKoding page quality, which the content and tutorial gates own, or gives the gate's verdict.