# Map Product

- Name: Map Product
- Catalogue ID: WM-DAT-003
- Registry ID: vr.wm-dat-003
- Type: Published Vercy entity
- Version: 0.1.0-reviewable.20261006
- Specification: https://ver.cy/models/wm-dat-003-map-product/spec.yaml
- Storage type: format-independent; select a binding in the page constructor
- Interface: https://ver.cy/models/wm-dat-003-map-product/#template-builder
- Processes: https://ver.cy/processes/
- Model agent protocol: https://ver.cy/model-agent-protocol.md
- Research evidence: https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-dat-003

Read this file first, then `spec.yaml`. Traverse Bundle to Layer to Finding to
Questions and Artifacts. The specification is published, while its research
assurance remains `reviewable-draft`. Do not claim canonical completeness
while `researchAdjudication.publicationHolds` is non-empty. Preserve source
references, master-system identity and access rules.

## Five-facet gate

Before creating or changing an instance, inspect the specification for explicit
coverage of: identity and class; direct properties; recognition and observation;
capabilities, behaviour and possible actions; context and evidence. Treat each
facet as required, optional, not applicable with a reason, or delegated through
a pinned model reference. Do not invent physical properties for abstract
objects. For physical measurements preserve units, tolerances, method,
conditions, observation time, uncertainty and provenance.

Keep capability, behaviour, state, transition, affordance, operation,
precondition, effect, reversibility, permission, constraint, hazard and failure
mode distinct. Resolve delegated child models and master systems instead of
copying their domains into this model.

## Agent lifecycle route

1. **Fill:** read the nearest owner and Dimension policies, resolve master
   identities, ask only for missing facts or authority, then record facts,
   hypotheses and unknowns distinctly with evidence and observation time.
2. **Extend:** propose a versioned extension when the published bundles and
   layers cannot express a required concept. Preserve stable IDs and namespace
   ownership; do not silently widen the model boundary.
3. **Edit:** validate authority, purpose, current version and concurrency before
   mutation. Preserve history and provenance. Treat access expansion, external
   writes and material side effects as confirmation-gated actions.
4. **Validate:** run schema, semantic, reference, permission, evidence and
   five-facet checks before and after a write. Report unresolved references,
   lossy projections, stale observations and publication holds.
5. **Retire:** deprecate and supersede through the declared lifecycle. Preserve
   immutable history and resolvable references. Require confirmation before
   deletion, destructive migration or irreversible external action.

Autonomous work is limited to policy-authorized reading, local population of
confirmed facts, validation, indexing and non-destructive maintenance. Propose
schema changes and new imports. Require confirmation for publication, broader
access, external writes, deletion and irreversible effects. Follow the model
agent protocol and the nearest local `AGENTS.md` whenever their rules are more
restrictive.

## Local package assurance

This package was generated locally only. Publication lifecycle metadata does
not establish remote availability. Research assurance is reviewable-draft and
noncanonical. Codex is the sole active provider; the local no-tools self-audit
is not independent external review.

Preserve these holds in downstream use:

- Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts; the separate local Codex no-tools self-audit is not an independent second-provider review.
- Source and version verification remains incomplete. All eight admitted URLs yielded browser text for selected evidence, but direct HTTP checks were not attempted under the owner-reported sandbox block: zero measured HTTP 200 responses, no measured status codes. OGC sources are overview pages, linked full specifications were not retrieved, and the spatial best-practices source is a draft. The coordinator must run check_sources.py and review versions and claims separately.
- Executable nested instance schemas, state vocabularies, pinned model bindings, spatial validation, DCAT/PROV mappings and WMS/tile/style conformance fixtures remain incomplete. Research validation is not implementation or interoperability certification.
- Adopting profiles must resolve source and product rights, attribution, exposure, retention, portrayal of disputed content, accountable authority and intended-use fitness. This draft does not approve navigation, emergency or legal use.
- Specialist cartographic coverage remains incomplete, including nautical and aviation charts, dynamic reproduction, tactile and accessible portrayal, indoor maps and temporal animation. No universal scale, update cadence or quality threshold is asserted.
- Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft.

Preserving issued revision identity does not require indefinite retention of
protected payloads. Follow the specification and adopting retention policy for
lawful erasure, redacted evidence and minimal tombstones.