Curriculum evidence schema
Each row in a detailed course ledger represents one independently assessable concept, decision, configuration, or failure mode. A compound source bullet becomes multiple rows when its parts need different evidence.
Required row fields
Use a stable ID such as AZ900-SG-CLOUD-001 or AZ204-SG-COMPUTE-004 and record these fields for every row:
| Field | Meaning |
|---|---|
id | Stable source/objective identifier. Do not renumber because notes move. |
course | One of AZ-900, AZ-104, AZ-204, or AZ-400. |
source_type | course-syllabus, learning-path, module, study-guide, prerequisite, or related-prerequisite. |
source_url and source_heading | Direct authoritative page and heading checked. |
source_effective | Skills-measured or source version date, when available. |
objective | Original paraphrase in the vault’s own words. |
prerequisites | Concepts the route must teach first. |
canonical_concepts | Actual notes that teach the row. |
comparisons | Notes or sections that resolve likely confusion. |
relationships | Prose evidence naming source, verb, target, direction, boundary, and failure/decision. |
route_checkpoint | Ordered MOC/module location and an observable explanation or application checkpoint. |
evidence | Exact files and headings inspected, not just a title or nearby link. |
conceptual_grade | missing, thin, covered, or verified. |
relationship_grade | missing, thin, covered, or verified. |
practical_status | not-required, missing, existing-unchecked, designed, static-checked, or live-verified. |
exact_gap | The remaining evidence gap, or none. |
reaudit_trigger | Source-date, product-behavior, permission, retirement, or other change that reopens the row. |
Conceptual grades
missing: no suitable explanation, unresolved target, or known factual error.thin: a mention or definition exists, but an essential explanation, prerequisite, relationship, comparison, example, or decision is missing.covered: a correct self-contained explanation and route exist, but the official source and actual target have not both been independently inspected.verified: the source was re-read; the actual target and route were inspected; the explanation is accurate and self-contained; prerequisites precede use; relationships and likely confusions are taught; and exact evidence is recorded.
Conceptual verification does not require a live Azure lab.
Practical status
Practical status is independent. A procedure may be designed or statically checked while its live execution remains unavailable. Do not raise an overall evidence grade when the original lab and practice requirements are unmet.
Relationship evidence
Links alone are not relationship evidence. State a directional sentence such as: “A pipeline authenticates to Azure through a service connection; Azure RBAC then authorizes its principal at a resource scope; removing that role causes deployment authorization to fail.” Record the handoff and the failure or decision that reveals it.