Skip to content

Final Verdict — R6

Tier 1 — tier1-yaml-first-authoring.md

SHIP

  • Schema inference fix checks out. The doc now correctly says omitted _meta.schema only infers the entity type, with no inferred version (tier1-yaml-first-authoring.md:1112-1121). That matches PreparePhase._resolve_schema(), which derives entity_type from _meta.schema or top-level key / parent directory only (packages/maid-engine/src/maid_engine/loader/phases/prepare.py:220-267).
  • Area glossary fix checks out. The doc now says area_id is runtime-writable, not read-only (tier1-yaml-first-authoring.md:24). That matches both admin APIs, which accept and persist area_id on create/update (packages/maid-stdlib/src/maid_stdlib/api/admin/world.py:568-589,637-646; packages/maid-engine/src/maid_engine/api/v1/world.py:1115-1139,1190-1198).

Tier 2 — tier2-ai-content-pipeline.md

NO SHIP

  • The doc still exposes a generic --area flag in the main maid ai generate options table:
  • tier2-ai-content-pipeline.md:372 — --area TEXT Parent area name for context (used in prompts)
  • That is not aligned with the doc's own Zone-first terminology note and examples, which correctly use --zone for room/area generation (tier2-ai-content-pipeline.md:690-700,703-704,4871-4872).
  • The codebase also reinforces --zone as the current authoring/export flag (packages/maid-stdlib/src/maid_stdlib/commands/building/export.py:149-152 and usage at :110).

Tier 3 — tier3-visual-tools.md

NO SHIP

  • The major UI mockups appear corrected to Zone, but stale non-API area wording still remains in editor-facing sections where the glossary says Zone is the primary concept:
  • tier3-visual-tools.md:2830-2832 — “area filtering” / “Use area_id (zone) filtering”
  • tier3-visual-tools.md:2886 — “area-based partitioning”
  • tier3-visual-tools.md:3024 — “Export area as YAML”
  • tier3-visual-tools.md:3081,3084 — “color-coded by area”, “filter by area/zone”
  • tier3-visual-tools.md:3108,3115,3165-3166,3316 — “Concurrent area editing”, “colored by area”, screen-reader “room name, area…”, “area filtering”
  • Those are not API-field explanations like area_id; they are residual conceptual/editor labels and are inconsistent with the document’s own glossary (tier3-visual-tools.md:21-22).

Cross-cutting

Area vs Zone consistency

NO SHIP

  • Tier 1 is consistent.
  • Tier 2 still mixes in --area at the CLI surface (tier2-ai-content-pipeline.md:372).
  • Tier 3 still has multiple non-API “area” references in Zone-oriented editor sections (tier3-visual-tools.md:2830,2886,3024,3081,3084,3108,3115,3166,3316).

Canonical format consistency

SHIP

  • I did not find a new factual mismatch here in the R6 spot-check.
  • Tier 1 still anchors canonical YAML on _meta.schema + components: with room exits/zone allowed as top-level fields (tier1-yaml-first-authoring.md:162-170 plus packages/maid-engine/src/maid_engine/loader/entity_types.py:7-13).
  • Tier 3 correctly distinguishes visual-editor loader-compatible export from current @export output (tier3-visual-tools.md:1077-1080,1147-1153,1188-1192; packages/maid-stdlib/src/maid_stdlib/commands/building/export.py:149-152).

No _schema remnants

SHIP

  • I found no top-level YAML _schema remnants in the three reviewed docs.
  • Remaining json_schema / self._schema occurrences in Tier 2 are internal code-example identifiers, not the old YAML field.