Visual Coverage Map — Module 05
Canonical profile audited: .agents/visual-profiles/trainings/construction-plan-drafting-and-coordination.md from PR #4527, profile version 1, reviewed 2026-10-05. This PR consumes that profile as a read-only standard and does not modify it.
| Asset | Objective | Learning question | Medium choice / profile fit | Technical plausibility and authority | Semantic colors / construction-document language | Accessibility | Status |
|---|---|---|---|---|---|---|---|
| Four Sources of Project Constraints | 2 | What is the authority/source of each project input? | TrainingConceptDiagram — grid. Correct non-process medium for parallel information classes; avoids forcing a false workflow. | Categories are source-of-requirement classes, not physical design claims. Professional-boundary language is supported by R.A. 9266/R.A. 544 and the Supreme Court decision. | Neutral card language is appropriate; no discipline is identified by color alone. Uses controlled labels rather than decorative blueprint imagery. | Informative title/description; every class is text-labeled; meaning survives monochrome/light/dark themes. | Profile-aligned |
| jurisdiction-source-verification | 1,4 | How do I prove that a requirement is applicable and current? | Shared Flowchart. Appropriate because verification has a decision/recheck loop. | Jurisdiction, source currency, authority, and applicability are realistic regulatory-review actions. | Uses approval/verification gates consistent with profile workflow vocabulary; no fake permits, seals, or forms. | Shared renderer exposes title/description and labeled decision branches; no color-only status. | Profile-aligned |
| designable-envelope | 3 | How does a parcel become a constrained design space? | Shared Flowchart. Appropriate for sequential application of verified constraints; it is intentionally not a fake site plan. | Applies site, zoning, easement, accessibility, fire/life-safety, service, parking/loading, and circulation constraints without inventing numeric dimensions. | Construction-document terms are concise; no generated dimensions or universal setbacks are embedded. | Text node labels carry the complete meaning; success/hold states are also named. | Profile-aligned |
| regulatory-due-diligence | 1,3,4 | What sequence should be completed before preliminary design? | Shared Flowchart. Correct process medium for multi-stage screening and iteration. | Stages correspond to P.D. 1096/Revised-IRR source review, B.P. 344, fire, sanitation, environmental, utility, and special-site screening. | Uses review/issue/basis terminology from the canonical coordination vocabulary; disciplines are named in text rather than only by color. | Branch labels and node text provide a nonvisual process description. | Profile-aligned |
| predesign-hold-points | 5 | When must the team stop and resolve missing evidence? | Shared Flowchart. Correct for pass/hold decisions. | Hold gates are documentary/evidence decisions, not invented engineering acceptance criteria. | Warning/success semantics are redundant with “HOLD” and “Release” labels; no color-only pass/fail meaning. | Explicit question nodes and branch labels; concise cognitive load with one principal checking question per gate. | Profile-aligned |
Profile-level audit
- Primary visual modes: one deterministic comparison/grid plus four true review/decision workflows; this matches the profile's grid + shared-flowchart grammar.
- Technical plausibility: no visual invents dimensions, permit stamps, forms, or site geometry. Numeric building controls remain in source text, not generated visual text.
- Semantic discipline colors: no asset relies on discipline-specific color. Where the shared renderer uses state accents, text/position/branch labels duplicate the meaning.
- Construction-document language: labels use jurisdiction, source, review, hold, basis, and release terminology rather than decorative CAD/blueprint motifs.
- Accessibility: all assets have learner-facing titles/descriptions or shared-renderer equivalents; labels remain meaningful without color.
- Cognitive load: each asset has one principal question and does not overload multiple discipline overlays.
- Rendered-geometry limitation: source-level/profile alignment was audited; no browser rendering or production geometry inspection was performed in this non-main pass.