{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T10:17:28Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 21.4, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a0951e-04dd-72b0-bb3f-e712ac8607d3\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Holland-class offshore patrol vessel\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 thin", "usd": 0.0, "recall": true }, "codex": { "seconds": 81.2, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a0951e-04db-7691-bc11-6faa166c058e\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Holland-class offshore patrol vessel\nRegistry id: vr.tr.holland-class-offshore-patrol-vessel\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:49:29+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "standards_and_regulation", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:26+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q1624733", "registryId": "vr.tr.holland-class-offshore-patrol-vessel", "name": "Holland-class offshore patrol vessel", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q1624733/", "model": { "registry_id": "vr.tr.holland-class-offshore-patrol-vessel", "name": "Holland-class offshore patrol vessel", "purpose": "Enable an agent to recognise the Holland-class offshore patrol vessel design, assess a member vessel against its documented configuration, and identify the evidence and authority needed for proposed operations.", "definition": "The Holland class is a class of four ocean-going offshore patrol vessels built by Damen for the Royal Netherlands Navy, designed primarily for maritime surveillance, law enforcement support and security operations rather than high-intensity naval combat.", "scope_statement": "This model owns the class-specific physical characteristics, capability interfaces and readiness questions of vr.tr.holland-class-offshore-patrol-vessel in PHY / PHY.OBJ; individual ships supply dated configuration and condition evidence.", "in_scope": [ "Class identity, membership evidence and configuration baselines", "Hull envelope, propulsion modes and patrol endurance constraints", "Integrated mast, surveillance and command-system interfaces", "Shipboard interfaces for helicopters, boats and relief cargo", "Accommodation, mission suitability and readiness dependencies", "Class-specific maintenance evidence and operational restrictions" ], "out_of_scope": [ "Individual hull histories, positions and maintenance logs as standalone records", "The general offshore patrol vessel kind and unrelated Holland-named classes", "Internal designs of embarked helicopters, boats and installed weapons", "Royal Netherlands Navy organisation and personnel administration", "Mission plans, boarding procedures and rules governing use of force", "Replacement ship designs and acquisition programmes" ], "distinguishing_features": [ "Require class-membership evidence linking the design to Holland P840, Zeeland P841, Friesland P842 or Groningen P843; a ship named Holland alone is insufficient. [Dutch Ministry of Defence](https://english.defensie.nl/documents/2022/04/01/ocean-going-patrol-vessel)", "Check the documented hull envelope: 108 m length, 16 m beam, 4.55 m draught and approximately 3,750 tonnes displacement; dimensions support identification but do not establish it alone. [Dutch Ministry of Defence](https://english.defensie.nl/documents/2022/04/01/ocean-going-patrol-vessel)", "Check for the integrated mast combining radar, cameras and communications, together with provision for an NH90 helicopter and two FRISC boats. [Dutch Ministry of Defence](https://www.defensie.nl/onderwerpen/m/materieel/schepen/patrouilleschepen)", "Confirm the documented emphasis on maritime security and humanitarian missions at lower levels of force; size and naval ownership do not establish frigate-equivalent combat capability. [Dutch Ministry of Defence](https://www.defensie.nl/onderwerpen/m/materieel/schepen/patrouilleschepen)" ], "characteristics": [ { "name": "Class membership", "kind": "relation", "unit_or_values": "Individual hull → documented Holland-class baseline", "why_it_matters": "Prevents confusion between the class, its lead ship and similarly named vessels." }, { "name": "Configuration applicability", "kind": "relation", "unit_or_values": "Baseline or modification record, applicable hulls, effective date and supporting document", "why_it_matters": "Prevents an upgrade on one hull from becoming an unsupported class-wide claim." }, { "name": "Hull and loading envelope", "kind": "measurement", "unit_or_values": "Length, beam and draught in m; displacement in tonnes; loading condition required", "why_it_matters": "Supports berth and passage assessment without treating nominal draught as the actual loaded value." }, { "name": "Propulsion operating mode", "kind": "state", "unit_or_values": "Documented installed modes; selected mode; available, restricted, unavailable or unknown", "why_it_matters": "Connects achievable patrol performance to machinery condition and operating restrictions." }, { "name": "Patrol endurance", "kind": "measurement", "unit_or_values": "Days and nautical miles at stated speed, loading, reserves and environmental conditions", "why_it_matters": "Distinguishes an advertised range from a supportable mission duration." }, { "name": "Integrated mast serviceability", "kind": "state", "unit_or_values": "Per surveillance and communications function: available, degraded, unavailable or unverified", "why_it_matters": "An intact mast does not prove that its constituent functions are usable." }, { "name": "Embarked capability", "kind": "relation", "unit_or_values": "Ship → aircraft, boats, detachments and applicable operating clearances", "why_it_matters": "Separates design provision from equipment and qualified personnel actually aboard." }, { "name": "Personnel carrying envelope", "kind": "measurement", "unit_or_values": "Persons by crew, detachment and evacuee category, with permitted duration and support conditions", "why_it_matters": "Temporary evacuation capacity cannot automatically substitute for sustained accommodation." }, { "name": "Operational release", "kind": "state", "unit_or_values": "Released, released with restrictions, withheld or unknown; issuing authority and validity", "why_it_matters": "Physical capability alone does not establish permission or readiness to operate." } ], "affordances": [ "Match a candidate vessel to the class using identity records and corroborating physical features.", "Compare a member vessel's dated configuration with the applicable class baseline.", "Assess whether evidenced propulsion, staffing and support capacity meet a proposed patrol requirement.", "Identify missing clearances or degraded interfaces affecting helicopter, boat or relief operations.", "Trace a proposed readiness judgement to configuration, inspection and release evidence.", "Flag unsupported capability assumptions for qualified human review." ], "agent_conduct": { "may": [ "Identify ships of this class from published records and features.", "Report their patrol, rescue and support roles from official sources.", "Assess a member vessel against the documented class configuration." ], "must_not": [ "Assist in evading lawful maritime law enforcement or surveillance.", "Track or publish ship movements to endanger crews or operations.", "Spread fabricated reports about their operations.", "Disclose non-public operational details obtained without authority." ], "requires_human": [ "Publishing the real-time position of a patrol vessel during an operation.", "Attributing a specific incident to a named ship." ] }, "ethics": { "considerations": [ "Patrol vessels enforce law at sea and rescue people; their work touches migrants, fishers and smugglers alike.", "Surveillance at sea must respect the rights of those encountered." ], "affected_parties": [ "Crews", "People rescued or intercepted at sea", "Seafarers and fishers" ] }, "owners": { "steward": "The navy of the operating state.", "master_systems": [ "Naval vessel registers of the operating state" ] }, "visual_identification": [ "Ocean-going patrol vessel with a large integrated mast holding sensors.", "Helicopter deck aft and boat launch arrangements for interceptions.", "Pennant number and name distinguish the four ships." ], "failure_modes_and_hazards": [ "Boarding and boat operations at sea risk injury to crews and the people met.", "Fire and flooding risks common to all warships.", "Sensor or communication failure can delay rescue." ], "standards_and_regulation": [ "Convention on the International Regulations for Preventing Collisions at Sea (COLREGs), International Maritime Organization." ], "what_it_is_for": [ "These offshore patrol vessels serve in Dutch naval operations involving maritime surveillance, presence and security.", "They support tasks such as search and rescue, fisheries protection and countering illicit maritime activity.", "Their design emphasizes sustained patrol operations and support for boats and helicopters in offshore environments." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q1624733: Holland-class offshore patrol vessel", "url": "https://www.wikidata.org/wiki/Q1624733", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Holland-class patrol vessel", "url": "https://en.wikipedia.org/wiki/Holland-class_patrol_vessel", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "class-identity-and-baselines", "name": "Class identity and baselines", "description": "Establish which design the registry entry denotes and which claims apply to each member.", "rationale": "Holland can denote a class or a named ship, while modifications may create differences between members.", "layers": [ { "id": "identity-boundary", "name": "Identity boundary", "description": "Separate the registered class from hull instances and neighbouring designs.", "findings": [ { "id": "membership-evidence", "name": "Membership evidence", "description": "Require documentary membership evidence before applying the class model to a vessel.", "questions": [ { "text": "Which authoritative record connects the candidate hull and pennant number to this Holland-class patrol vessel design?", "kind": "provenance", "id": "membership-evidence-q01" }, { "text": "Does the supplied name denote this class, an individual member or a different Holland-named design?", "kind": "boundary", "id": "membership-evidence-q02" } ] } ] }, { "id": "configuration-applicability", "name": "Configuration applicability", "description": "Distinguish common design provisions from dated installations and modifications.", "findings": [ { "id": "dated-class-baseline", "name": "Dated class baseline", "description": "Treat installed equipment and upgrade claims as applicable only to their documented hulls and dates.", "questions": [ { "text": "Which approved configuration document defines the baseline being assessed?", "kind": "provenance", "id": "dated-class-baseline-q01" }, { "text": "Which changes apply to all class members, and which remain specific to named hulls?", "kind": "boundary", "id": "dated-class-baseline-q02" } ] } ] } ] }, { "id": "hull-propulsion-and-patrol", "name": "Hull, propulsion and patrol", "description": "Connect the class's physical envelope and machinery arrangement to supported patrol performance.", "rationale": "An ocean-going patrol assignment depends on loading, machinery mode and endurance evidence rather than nominal maximum speed.", "layers": [ { "id": "loaded-hull-envelope", "name": "Loaded hull envelope", "description": "Make geometric and displacement claims conditional on their reference loading state.", "findings": [ { "id": "passage-and-loading-basis", "name": "Passage and loading basis", "description": "Record the loading basis behind draught, displacement and clearance judgements.", "questions": [ { "text": "What loading condition underlies the quoted class draught and displacement?", "kind": "measurement", "id": "passage-and-loading-basis-q01" }, { "text": "Which approved loading and stability evidence supports the proposed combination of fuel, personnel and relief cargo?", "kind": "action", "id": "passage-and-loading-basis-q02" } ] } ] }, { "id": "machinery-and-endurance", "name": "Machinery and endurance", "description": "Represent propulsion modes and their consequences for sustained patrol.", "findings": [ { "id": "mode-dependent-performance", "name": "Mode-dependent performance", "description": "The official description identifies two diesel engines and two electric motors, with electric propulsion supporting speeds up to 10 knots. Exact machinery topology and operating limits require technical documentation. [Dutch Ministry of Defence](https://english.defensie.nl/documents/2022/04/01/ocean-going-patrol-vessel)", "questions": [ { "text": "Which technical reference establishes the machinery coupling, permitted propulsion modes and transition restrictions?", "kind": "provenance", "id": "mode-dependent-performance-q01" }, { "text": "What endurance is supported at the proposed patrol speed with the actual fuel reserve, hotel load and machinery availability?", "kind": "measurement", "id": "mode-dependent-performance-q02" } ] } ] } ] }, { "id": "integrated-mast-and-command", "name": "Integrated mast and command", "description": "Represent surveillance, communications and operator interfaces as separately evidenced functions.", "rationale": "The integrated mast is a defining class feature, but its physical presence cannot establish detection performance or command readiness.", "layers": [ { "id": "surveillance-functions", "name": "Surveillance functions", "description": "Connect installed mast systems to qualified observation capabilities.", "findings": [ { "id": "sensor-function-evidence", "name": "Sensor function evidence", "description": "The official inventory names Smile, Seastar and Gatekeeper; record their installed versions and serviceability separately. [Dutch Ministry of Defence](https://www.defensie.nl/onderwerpen/m/materieel/schepen/patrouilleschepen)", "questions": [ { "text": "Which installed sensors and software versions support air, surface and close-surroundings surveillance on the assessed hull?", "kind": "provenance", "id": "sensor-function-evidence-q01" }, { "text": "Under what documented environmental and test conditions has each required surveillance function been demonstrated?", "kind": "measurement", "id": "sensor-function-evidence-q02" } ] } ] }, { "id": "command-and-information-quality", "name": "Command and information quality", "description": "Track how observations reach operators and cooperating units.", "findings": [ { "id": "usable-operational-picture", "name": "Usable operational picture", "description": "Distinguish sensor output, operator-confirmed interpretation and information shared through available communications.", "questions": [ { "text": "What evidence establishes that required mast, command-system and communications interfaces are functioning together?", "kind": "provenance", "id": "usable-operational-picture-q01" }, { "text": "Which surveillance or coordination tasks require restriction when data are stale, communications are unavailable or operator stations are degraded?", "kind": "action", "id": "usable-operational-picture-q02" } ] } ] } ] }, { "id": "aviation-boats-and-relief", "name": "Aviation, boats and relief", "description": "Model the ship-side interfaces that enable embarked assets and humanitarian loads.", "rationale": "Much of the class's practical reach depends on embarked equipment and its launch, recovery and support arrangements.", "layers": [ { "id": "embarked-asset-interfaces", "name": "Embarked asset interfaces", "description": "Separate carriage provision from cleared and available aviation or boat operations.", "findings": [ { "id": "helicopter-and-frisc-readiness", "name": "Helicopter and FRISC readiness", "description": "The official description places one FRISC in an internal dock beneath the helicopter deck and another in davits; assess these interfaces separately from aviation readiness. [Dutch Ministry of Defence](https://english.defensie.nl/documents/2022/04/01/ocean-going-patrol-vessel)", "questions": [ { "text": "Which aircraft and boats are actually embarked, and which ship-side facilities and qualified detachments are available to support them?", "kind": "measurement", "id": "helicopter-and-frisc-readiness-q01" }, { "text": "Which current clearances define permitted launch, recovery and flight operations for the installed configuration?", "kind": "action", "id": "helicopter-and-frisc-readiness-q02" } ] } ] }, { "id": "humanitarian-load-and-support", "name": "Humanitarian load and support", "description": "Relate accommodation and relief loads to duration, handling and life-support constraints.", "findings": [ { "id": "sustained-and-emergency-capacity", "name": "Sustained and emergency capacity", "description": "Official figures distinguish 50 crew, 40 temporary personnel and an additional 100 evacuees; their support conditions must be established before use. [Dutch Ministry of Defence](https://www.defensie.nl/onderwerpen/m/materieel/schepen/patrouilleschepen)", "questions": [ { "text": "For what duration and under what accommodation, medical and lifesaving conditions is each personnel category supported?", "kind": "measurement", "id": "sustained-and-emergency-capacity-q01" }, { "text": "Which approved cargo-handling, securing and stability limits govern the proposed relief load?", "kind": "action", "id": "sustained-and-emergency-capacity-q02" } ] } ] } ] }, { "id": "mission-release-and-sustainment", "name": "Mission release and sustainment", "description": "Connect the class's patrol role to explicit readiness, maintenance and authority evidence.", "rationale": "A member can retain its class identity while lacking the equipment, support or release needed for a particular assignment.", "layers": [ { "id": "mission-envelope-and-authority", "name": "Mission envelope and authority", "description": "Assess mission suitability without inferring unrestricted capability from naval classification.", "findings": [ { "id": "capability-versus-release", "name": "Capability versus release", "description": "Keep physical mission capability, installed defensive equipment and authorised employment as distinct judgements.", "questions": [ { "text": "Which documented capability requirements does the proposed maritime-security or humanitarian assignment impose?", "kind": "definition", "id": "capability-versus-release-q01" }, { "text": "Which competent authority has released this hull and embarked package for those requirements, and with what restrictions?", "kind": "action", "id": "capability-versus-release-q02" } ] } ] }, { "id": "maintenance-and-assurance", "name": "Maintenance and assurance", "description": "Link machinery, mast and mission-interface condition to inspections and applicable assurance requirements.", "findings": [ { "id": "readiness-limiting-defects", "name": "Readiness-limiting defects", "description": "Record defects and overdue assurance evidence by their effect on patrol, surveillance, launch-and-recovery and accommodation functions.", "questions": [ { "text": "Which unresolved defects or overdue inspections restrict propulsion, mast services, fire protection or embarked-asset handling?", "kind": "measurement", "id": "readiness-limiting-defects-q01" }, { "text": "Which naval technical standards, survey requirements and issuing authorities apply to this hull and modification state?", "kind": "provenance", "id": "readiness-limiting-defects-q02" }, { "text": "What maintenance, replenishment and verification evidence is required before a restricted function can be released?", "kind": "action", "id": "readiness-limiting-defects-q03" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This entry describes a ship class, not a single physical vessel or the entire offshore patrol vessel category.", "Dimensions, displacement, speed and crew figures are recalled approximate specifications; displacement basis and embarked personnel allowances require verification.", "Hazards listed are operational exposures, not claims of documented class-specific defects; applicable naval construction rules and current equipment configurations require research." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Holland-class offshore patrol vessel this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "scheme": "Royal Netherlands Navy pennant number", "value_or_pattern": "P840, P841, P842, P843", "note": "Identify the individual ships Holland, Zeeland, Friesland and Groningen, respectively; these are members of the class, not separate varieties." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Holland-class offshore patrol vessel this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Maritime surveillance and patrol in Dutch and Caribbean waters.", "Counter-narcotics and counter-piracy operations.", "Fisheries monitoring and maritime law enforcement support.", "Search and rescue and humanitarian assistance.", "Deployment of boarding teams using shipborne boats, supported by helicopter operations." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Holland-class offshore patrol vessel this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "Overall length", "typical_range": "Approximately 108", "unit": "m" }, { "quantity": "Beam", "typical_range": "Approximately 16", "unit": "m" }, { "quantity": "Displacement", "typical_range": "Approximately 3750", "unit": "metric tonnes" }, { "quantity": "Maximum speed", "typical_range": "Approximately 21.5", "unit": "knots" }, { "quantity": "Core crew complement", "typical_range": "Approximately 50", "unit": "persons" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Holland-class offshore patrol vessel this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Propulsion or electrical failures can reduce manoeuvrability and interrupt shipboard systems.", "Collision, grounding and flooding are general operational hazards.", "Heavy weather creates hazards during boat launch, recovery and boarding operations.", "Helicopter operations introduce flight-deck, rotor and aviation-fuel hazards.", "Limited combat armament and defensive capability constrain suitability for operations against heavily armed opponents." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Holland-class offshore patrol vessel this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "The class serves the Netherlands; deployments in European and Caribbean waters represent different operating environments, not regional design variants." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Holland-class offshore patrol vessel this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "name": "Offshore patrol vessel", "difference": "The broader vessel category; the Holland class is one specific design and procurement class within it." }, { "name": "HNLMS Holland", "difference": "An individual vessel and the lead ship of the class, rather than the class itself." }, { "name": "Frigate", "difference": "A combatant category generally equipped for more demanding warfare and escort missions; the Holland class prioritizes patrol and maritime security." }, { "name": "Holland-class protected cruiser", "difference": "A historical Dutch cruiser class sharing the Holland name, distinct from the modern offshore patrol vessel class." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Holland-class offshore patrol vessel this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing Vercy world model already own this class concept, requiring a registry link instead of a separate publication?", "Which authoritative machinery documents resolve propulsion topology, mode terminology and endurance under specified loading and speed conditions?", "Which configuration changes have actually been accepted on each hull, and what dated baseline supports class-wide equipment claims?", "What approved operating envelopes govern helicopter operations, both FRISC handling arrangements, relief cargo and temporary evacuee accommodation?", "Which naval standards, certification or survey regimes, maintenance requirements and release authorities apply, including any documented exemptions?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 17, "questions": 28 } }