# Vercy Enterprise program

Read https://ver.cy/AGENTS.md and the nearest owner Dimension policy first.
The 111 entries in registry.json are research contours, not 111 installed or finished models.
Use starter-selections.json as optional model selections. Re-resolve the runtime index, verify exact version/digest, required closure and semantic fit before installation. Retain reviewable-draft assurance and publication holds. These selections are not complete company models or native vercy.lock files.
Team participant records and the separate Membership/Work Assignment models overlap: preserve one authoritative relationship identity, link or project it, and record a boundary decision before combining them. Person civil-identity fields are not required merely to collaborate; record only purpose-necessary information. No real company is required to install every selected model.
Use a Company as business identity; do not manufacture a second identity when it is identical to the legal organization. Declare distinct boundaries when group, brand, legal entity and management perimeter differ.
Create the private Dimension owner package, purpose, authority, master systems, model lock and event log. Publish only generic specifications here. Never send private instance records to this public catalogue.
Research status is in queue.json. The per-contour brief and RESEARCH-PROTOCOL.md govern research completion; a published draft may still leave its larger contour unfinished.
Check queue.json platform_issues before claiming installation completion. The generic package downloader and current native V1-V3 validator are not fully aligned. A semantic package pin is not executable readiness. Preserve validation failures; never invent permissive runtime schemas or weaken the validator. The optional WM-ORG-017 reference binding is documented at https://ver.cy/models/wm-org-017-performance-objective-review/NATIVE-REFERENCE.md and requires both native and nested case validation.