{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T09:00:36Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 18.8, "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: 01a094d7-d93c-7631-a9fc-a2ceeff363bc\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Daihatsu Pyzar\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 043: 1001 ", "usd": 0.0, "recall": true }, "codex": { "seconds": 68.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: 01a094d7-d92a-7291-a559-c52f08cd208e\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Daihatsu Pyzar\nRegistry id: vr.tr.daihatsu-pyzar\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (no" } }, "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:25+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q1157567", "registryId": "vr.tr.daihatsu-pyzar", "name": "Daihatsu Pyzar", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q1157567/", "model": { "registry_id": "vr.tr.daihatsu-pyzar", "name": "Daihatsu Pyzar", "purpose": "Enable an AI agent to recognise a Daihatsu Pyzar, establish its applicable configuration, assess evidence about its condition, and identify supported maintenance or use decisions.", "definition": "The Daihatsu Pyzar is a five-door compact multipurpose passenger vehicle model produced by Daihatsu from 1996 to 2002, marketed in some export markets as the Daihatsu Gran Move.", "scope_statement": "This model owns the Daihatsu Pyzar registered vehicle-model identity and the configuration distinctions needed to interpret individual vehicles, while leaving specifications unresolved until supported by documentation for the relevant market and production period.", "in_scope": [ "Pyzar model identity, manufacturer attribution, and documented model or chassis identifiers", "Production-period, market, grade, powertrain, and drivetrain distinctions within the Pyzar entry", "Pyzar body, seating, cargo, and occupant-access arrangements", "Configuration-dependent operating limits, inspection needs, and service requirements", "Evidence required to connect an individual vehicle, component, or manual to the Pyzar model" ], "out_of_scope": [ "Daihatsu corporate history and the manufacturer's complete vehicle range", "Generic internal-combustion engine, transmission, and passenger-car models", "An individual vehicle's ownership, registration, accident, and service records", "Separate vehicle models that merely share components or design ancestry", "Road-network rules, driver licensing, and insurance contracts" ], "distinguishing_features": [ "Manufacturer identification and model or chassis codes must resolve to a documented Pyzar application; a Daihatsu badge alone is insufficient.", "Body proportions, door arrangement, glazing, and seating layout must agree with a verified Pyzar reference for the claimed production period.", "Engine, transmission, and driven-axle configuration must form a documented Pyzar combination; component similarity alone does not establish model identity.", "A vehicle advertised under another market name must have a documented relationship to Pyzar before its specifications or parts are treated as interchangeable." ], "characteristics": [ { "name": "Model and chassis identification", "kind": "category", "unit_or_values": "Manufacturer model code, chassis-series code, and their documented Pyzar applicability", "why_it_matters": "Separates a Pyzar identification from a seller's description or a visually similar Daihatsu." }, { "name": "Production and destination configuration", "kind": "category", "unit_or_values": "Build period, original sales market, grade, and specification revision; unknown where unverified", "why_it_matters": "Determines which Pyzar specifications, equipment descriptions, and manuals apply." }, { "name": "Alternative market-name relationship", "kind": "relation", "unit_or_values": "Documented equivalent designation, related model, or unresolved relationship", "why_it_matters": "Prevents importing specifications from a similarly named or related vehicle without evidence." }, { "name": "Engine application", "kind": "category", "unit_or_values": "Engine code, fuel type, and original or replacement installation status", "why_it_matters": "Selects applicable service procedures and distinguishes factory configuration from later changes." }, { "name": "Engine displacement", "kind": "measurement", "unit_or_values": "cm³, attached to a verified engine code and Pyzar application", "why_it_matters": "Supports powertrain identification without assuming a single engine specification for every Pyzar." }, { "name": "Transmission and driven axles", "kind": "category", "unit_or_values": "Verified transmission type and code, gear count, and driven-axle arrangement", "why_it_matters": "Affects parts selection, servicing, recovery, and interpretation of drivetrain symptoms." }, { "name": "Body dimensions and wheelbase", "kind": "measurement", "unit_or_values": "Length, width, height, and wheelbase in mm, with configuration and measurement convention", "why_it_matters": "Supports recognition, clearance assessment, and checking whether a specification belongs to the claimed Pyzar." }, { "name": "Seating and cargo arrangement", "kind": "state", "unit_or_values": "Documented seating capacity, fitted seats, seat positions, latch condition, and cargo configuration", "why_it_matters": "Distinguishes permitted passenger accommodation from space created by folding or removing seats." }, { "name": "Mass and loading limits", "kind": "measurement", "unit_or_values": "Documented unladen mass, maximum permitted mass, and axle limits in kg where available", "why_it_matters": "Prevents estimating safe loading solely from the Pyzar's available interior space." }, { "name": "Safety-equipment applicability", "kind": "category", "unit_or_values": "Documented braking, restraint, and warning equipment by market and grade; verified fitted equipment", "why_it_matters": "Prevents assuming every Pyzar has the same safety systems." }, { "name": "Condition evidence", "kind": "state", "unit_or_values": "Verified serviceable, fault observed, inspection required, or unknown, by subsystem", "why_it_matters": "Keeps model-level knowledge separate from claims about a particular Pyzar's fitness for use." } ], "affordances": [ "Match a claimed Pyzar to manufacturer identifiers and flag conflicting identity evidence.", "Select Pyzar documentation appropriate to the vehicle's market, production period, and installed powertrain.", "Compare an observed seating or cargo arrangement with documented Pyzar mechanisms and loading limits.", "Check replacement-part applicability against verified Pyzar configuration identifiers.", "Prepare a configuration-specific inspection or service request while identifying missing evidence.", "Determine whether available evidence supports a proposed loading, maintenance, or recovery action." ], "agent_conduct": { "may": [ "Identify a vehicle as this compact people carrier from its badges, body shape and VIN.", "Report recalls and service history from the keeper's and manufacturer's records.", "Drive or move it where the agent is authorized to operate it." ], "must_not": [ "Drive or move it without the keeper's authority or with an unresolved safety recall.", "Misstate its age, mileage or accident history in a sale.", "Share the location history of a vehicle to track its driver without consent.", "Fit child seats in a way that contradicts the vehicle's seat and anchorage limits." ], "requires_human": [ "Transferring the vehicle or its keys to another person.", "Declaring it unroadworthy or sending it for scrapping." ] }, "ethics": { "considerations": [ "An ageing family vehicle carries children and older passengers who depend on its safety systems.", "Honest condition reports protect buyers of older used cars." ], "affected_parties": [ "Occupants", "Other road users", "The registered keeper" ] }, "owners": { "steward": "The registered keeper; the vehicle register of the jurisdiction holds the authoritative record.", "master_systems": [ "National or regional vehicle register" ] }, "visual_identification": [ "Five-door, high-roof compact people-carrier body from the late 1990s.", "Model badges on the tailgate, with a different export name in some markets.", "The VIN and the registration record settle the identity of a particular car." ], "failure_modes_and_hazards": [ "Age-related corrosion and worn brakes and suspension in surviving examples.", "Older crash protection than current vehicles, raising injury risk to occupants.", "Overloading a small people carrier affects braking and handling." ], "standards_and_regulation": [ "UN Regulations annexed to the 1958 Agreement on wheeled vehicles, United Nations Economic Commission for Europe." ], "what_it_is_for": [ "This compact multipurpose passenger vehicle is used for everyday travel and carrying passengers with modest amounts of luggage.", "Surviving examples are encountered in used vehicle ownership, repair workshops and vehicle registration records, where configuration and condition inform maintenance decisions." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q1157567: Daihatsu Pyzar", "url": "https://www.wikidata.org/wiki/Q1157567", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Daihatsu Pyzar", "url": "https://en.wikipedia.org/wiki/Daihatsu_Pyzar", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "pyzar-identity-and-boundaries", "name": "Pyzar identity and boundaries", "description": "Establish what belongs to the Daihatsu Pyzar entry and how a claimed example is recognised.", "rationale": "Pyzar identification must survive badge changes, incomplete listings, and potentially overlapping market designations.", "layers": [ { "id": "manufacturer-identification", "name": "Manufacturer identification", "description": "Connect the registered name to documentary and physical identification evidence.", "findings": [ { "id": "pyzar-identification-evidence", "name": "Pyzar identification evidence", "description": "Record the evidence required to recognise the Pyzar model without treating an advertisement or badge as conclusive.", "questions": [ { "text": "Which manufacturer documents establish the Pyzar designation and its applicable model or chassis codes?", "kind": "provenance", "id": "pyzar-identification-evidence-q01" }, { "text": "Where are the relevant identifiers located, and which observed identifiers must agree before a vehicle is accepted as a Pyzar?", "kind": "definition", "id": "pyzar-identification-evidence-q02" } ] } ] }, { "id": "market-names-and-related-models", "name": "Market names and related models", "description": "Resolve alternative names and related vehicles without changing registry granularity by assumption.", "findings": [ { "id": "alternative-designation-boundary", "name": "Alternative designation boundary", "description": "Treat possible export-name equivalence as a relationship requiring evidence, not automatic identity or interchangeability.", "questions": [ { "text": "What manufacturer evidence establishes the relationship, if any, between Daihatsu Pyzar and Daihatsu Gran Move?", "kind": "provenance", "id": "alternative-designation-boundary-q01" }, { "text": "If the names overlap, which market or configuration differences prevent specifications from being transferred directly?", "kind": "boundary", "id": "alternative-designation-boundary-q02" }, { "text": "Does an existing Vercy world model already own this vehicle-model concept and require this registry entry to link to it?", "kind": "boundary", "id": "alternative-designation-boundary-q03" } ] } ] } ] }, { "id": "pyzar-configuration-and-propulsion", "name": "Pyzar configuration and propulsion", "description": "Resolve the configuration needed to interpret performance, controls, service information, and parts.", "rationale": "A Pyzar name alone does not establish the engine, transmission, drivetrain, or specification revision of a vehicle.", "layers": [ { "id": "production-and-grade-applicability", "name": "Production and grade applicability", "description": "Locate a Pyzar within documented production and market distinctions.", "findings": [ { "id": "configuration-selection", "name": "Configuration selection", "description": "Record supported configuration boundaries and the identifiers that select between them.", "questions": [ { "text": "Which production periods, destination markets, grades, and revisions are documented for Pyzar?", "kind": "definition", "id": "configuration-selection-q01" }, { "text": "Which identifiers distinguish those configurations when first-registration year or trim badges are unreliable?", "kind": "measurement", "id": "configuration-selection-q02" } ] } ] }, { "id": "engine-transmission-and-drive", "name": "Engine, transmission, and drive", "description": "Connect an installed powertrain to an evidenced Pyzar application.", "findings": [ { "id": "powertrain-application", "name": "Powertrain application", "description": "Record valid engine, transmission, and driven-axle combinations before selecting specifications or procedures.", "questions": [ { "text": "Which engine codes, displacements, fuel requirements, transmissions, and driven-axle arrangements are documented for each Pyzar configuration?", "kind": "definition", "id": "powertrain-application-q01" }, { "text": "What identification evidence distinguishes an original Pyzar powertrain combination from a replacement or conversion?", "kind": "provenance", "id": "powertrain-application-q02" }, { "text": "Which operating controls, fluid requirements, and towing or recovery restrictions follow from the verified combination?", "kind": "action", "id": "powertrain-application-q03" } ] } ] } ] }, { "id": "pyzar-body-and-interior-use", "name": "Pyzar body and interior use", "description": "Describe the Pyzar's physical envelope and documented passenger-to-cargo arrangements.", "rationale": "Recognition and practical use require evidence about the Pyzar's body and interior mechanisms, rather than assumptions from a vehicle-category label.", "layers": [ { "id": "body-envelope-and-access", "name": "Body envelope and access", "description": "Establish exterior geometry and access arrangements for the applicable Pyzar version.", "findings": [ { "id": "body-recognition-and-clearance", "name": "Body recognition and clearance", "description": "Connect identifying body features and measured dimensions to a verified reference configuration.", "questions": [ { "text": "Which door, rear-opening, glazing, and body-profile features identify a Pyzar against the models most often confused with it?", "kind": "boundary", "id": "body-recognition-and-clearance-q01" }, { "text": "What are the documented length, width, height, wheelbase, and ground clearance, and which equipment or measurement conventions affect them?", "kind": "measurement", "id": "body-recognition-and-clearance-q02" } ] } ] }, { "id": "seating-cargo-and-loading", "name": "Seating, cargo, and loading", "description": "Relate interior arrangements to occupant accommodation, latch operation, and load limits.", "findings": [ { "id": "interior-configuration-limits", "name": "Interior configuration limits", "description": "Record only documented Pyzar seat movements and cargo arrangements, including their conditions of use.", "questions": [ { "text": "Which Pyzar seats can slide, recline, fold, or be removed according to the applicable owner's manual?", "kind": "definition", "id": "interior-configuration-limits-q01" }, { "text": "What seating capacity, vehicle and axle mass limits, and cargo-space measurements apply to each documented arrangement?", "kind": "measurement", "id": "interior-configuration-limits-q02" }, { "text": "Which latch, restraint, and cargo-securing checks are required before using a changed interior arrangement?", "kind": "action", "id": "interior-configuration-limits-q03" } ] } ] } ] }, { "id": "pyzar-serviceability-and-use-decisions", "name": "Pyzar serviceability and use decisions", "description": "Connect Pyzar-specific documentation to inspection, maintenance, component selection, and evidence-based use decisions.", "rationale": "An agent must distinguish documented Pyzar requirements from generic vehicle advice and unsupported claims about age-related faults.", "layers": [ { "id": "service-and-parts-applicability", "name": "Service and parts applicability", "description": "Select maintenance procedures and components using the established Pyzar configuration.", "findings": [ { "id": "documented-service-requirements", "name": "Documented service requirements", "description": "Associate service intervals, consumables, and component compatibility with the exact Pyzar application.", "questions": [ { "text": "Which Pyzar workshop and owner's manuals specify service intervals, lubricant grades, fluid capacities, and engine timing-system maintenance?", "kind": "provenance", "id": "documented-service-requirements-q01" }, { "text": "Which model, engine, transmission, and production identifiers are needed to verify a replacement part in an authoritative parts catalogue?", "kind": "action", "id": "documented-service-requirements-q02" } ] } ] }, { "id": "inspection-and-safety-evidence", "name": "Inspection and safety evidence", "description": "Determine what evidence supports condition assessments and proposed actions for a particular Pyzar.", "findings": [ { "id": "configuration-specific-inspection", "name": "Configuration-specific inspection", "description": "Keep documented Pyzar faults, fitted safety equipment, and observed condition distinct when assessing a vehicle.", "questions": [ { "text": "Which manufacturer bulletins, recall records, or inspection publications establish Pyzar-specific issues and their affected identifiers?", "kind": "provenance", "id": "configuration-specific-inspection-q01" }, { "text": "Which braking, restraint, emissions, and warning systems should be fitted to the identified Pyzar configuration, and how is their condition checked?", "kind": "measurement", "id": "configuration-specific-inspection-q02" }, { "text": "Which observed faults or missing checks require repair, further inspection, or a different recovery method before the proposed use?", "kind": "action", "id": "configuration-specific-inspection-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 description is recalled knowledge, with no sources consulted.", "Verify production dates and exact engine, transmission and drivetrain availability against market-specific manufacturer records.", "The listed hazards are general ageing-vehicle concerns, not verified Pyzar-specific defects or recalls." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Daihatsu Pyzar this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-kinds", "name": "Kinds and varieties", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Front-wheel-drive versions", "Four-wheel-drive versions", "Manual-transmission versions", "Automatic-transmission versions" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Daihatsu Pyzar 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": "Manufacturer model name", "value_or_pattern": "Daihatsu Pyzar", "note": "Identifies the vehicle model, rather than an individual vehicle." }, { "scheme": "Export-market model name", "value_or_pattern": "Daihatsu Gran Move", "note": "Alternative sales name used in some export markets." }, { "scheme": "Vehicle identification number or manufacturer chassis number", "value_or_pattern": "Market-dependent individual vehicle identifier", "note": "Export vehicles generally use a 17-character VIN; Japanese domestic vehicles may use a manufacturer chassis number." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Daihatsu Pyzar 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": [ "Everyday passenger and family transport", "Carrying luggage or small loads using the adaptable rear passenger space" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Daihatsu Pyzar 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": "Petrol engine displacement", "typical_range": "Approximately 1.5-1.6", "unit": "L" }, { "quantity": "Seating capacity", "typical_range": "5", "unit": "people" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Daihatsu Pyzar 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": [ "Age-related corrosion can compromise body structure and attachment points.", "Deteriorated cooling-system components can cause coolant loss and engine overheating.", "Worn brakes, tyres, suspension components or steering joints can reduce braking and handling performance." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Daihatsu Pyzar 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": [ "Pyzar was the Japanese-market name; Gran Move was used in some export markets.", "Engine, transmission and driven-wheel configurations varied by market and production year." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Daihatsu Pyzar 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": "Daihatsu Gran Move", "difference": "An alternative market name for the same model, rather than a separate vehicle design." }, { "name": "Daihatsu Move", "difference": "A separate, smaller kei-car model; the Gran Move name does not make the Pyzar a Move variant." }, { "name": "Compact MPV", "difference": "The broader vehicle category; Pyzar identifies one manufacturer's specific model." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Daihatsu Pyzar this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "What authoritative documentation establishes Pyzar production boundaries, chassis identifiers, and its relationship to the Gran Move designation?", "Which engine, transmission, driven-axle, and grade combinations were actually offered in each market and production period?", "What configuration-specific dimensions, mass limits, seating mechanisms, and cargo measurements can be verified from manufacturer documents?", "Which safety equipment, type approvals, recalls, and service bulletins apply to identifiable Pyzar configurations?", "Does an existing Vercy publication already cover the Pyzar concept, and which alleged recurring faults remain unsupported by reliable evidence?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 16, "questions": 28 } }