Product Readiness

This report separates what the repository can prove from what still needs a qualified reviewer or a real target environment. A green build is evidence; it is not a tiny expert hiding inside the terminal.

The machine-readable version is product-readiness.json.

Current conclusion

Metric	Current value
Release level	guarded
Historical score (method unavailable)	78
Volumes	14
Numbered lesson files per language	509
Learning paths	6

guarded means you can use the material while checking the assumptions behind each explanation and example. Both languages share 509 lesson boundaries and repository gates cover catalog structure, bilingual pairing, links, lesson coordinates, and Python/JSON syntax. Independent subject-matter review and broader execution of Java, Shell, SQL, container, network, and cloud examples are still required.

The practical effect depends on the reader:

• Self-learners can follow a path, but should check the environment and observed output for examples that have not been executed there.
• Experienced readers can use a page as a technical index, but should not treat file existence as proof of review.
• Instructors should freeze a delivery scope, inspect each included lesson, and record the runtime environment before making course promises.
• Paid or assessed delivery requires instructor review; the whole site does not have one uniform completion level.

The score of 78 is retained from historical machine data. The repository has no reproducible scoring method, so the number cannot establish current content quality. Use the individual checks and outstanding work to assess coverage.

Governance already in place

• catalog.json: the machine-readable curriculum catalog.
• learning-paths.json: paths with audience, stages, time estimates, and completion outcomes.
• product-readiness.json: release level, risks, and verification commands.
• content-review-status.json: per-page writing stage, automated state, and content hash.
• Course Catalog and Learning Paths: reader-facing navigation.
• npm run validate:docs: links, navigation, counts, lesson coordinates, learning paths, and readiness metadata.
• npm run validate:content: writing stages, automated states, and stale content hashes.
• npm run validate:examples: code-fence integrity plus Python and JSON parsing.

These controls can find route, count, and state mismatches. They cannot prove that a technical explanation is correct or replace execution.

Release blocker

Code	Meaning	Required before release
HUMAN_TECHNICAL_REVIEW	The bilingual curriculum and automated gates pass, but full independent technical review and multi-environment example execution remain incomplete.	Freeze the scope, have a domain instructor review every included lesson, and run the relevant Java, Shell, SQL, and environment-specific examples.

Verification commands

The machine-readable readiness report requires these commands to pass:

npm run validate:docs
npm run validate:content
npm run validate:examples
npm run build

Risk disclosure

The number 509 counts lessons per language; some topics are split into progressive lessons. It does not mean 509 unrelated top-level subjects. Humanizer and automated states are tracked for both languages, but those records are not a claim of independent expert approval.

Before publishing a fixed-scope course, use the blocker in product-readiness.json and the per-page state in content-review-status.json. Record the curriculum boundary, runtime environment, executed examples, and remaining work.