{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T11:51:17Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 19.5, "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: 01a09574-09e6-7c60-b353-30b99cf9bb6b\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: PA-48 Enforcer\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 044: 1001 ", "usd": 0.0, "recall": true }, "codex": { "seconds": 72.1, "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: 01a09574-09e9-7960-a07e-37f3bede7a5d\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: PA-48 Enforcer\nRegistry id: vr.tr.pa-48-enforcer\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:54:05+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:32+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q6119816", "registryId": "vr.tr.pa-48-enforcer", "name": "PA-48 Enforcer", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q6119816/", "model": { "registry_id": "vr.tr.pa-48-enforcer", "name": "PA-48 Enforcer", "purpose": "Enable an agent to identify the PA-48 Enforcer aircraft design, interpret evidence about its configurations and condition, and determine which assessments or actions require further documentation.", "definition": "The Piper PA-48 Enforcer was an experimental turboprop-powered light ground-attack aircraft developed from the Cavalier Mustang lineage, itself derived from the North American P-51 Mustang, that underwent military evaluation but did not enter series production.", "scope_statement": "This model owns the recognition criteria and assessment requirements for the Piper PA-48 Enforcer design registered as vr.tr.pa-48-enforcer in PHY / PHY.OBJ; individual aircraft provide configuration and condition evidence without becoming separate design models.", "in_scope": [ "PA-48 identity, manufacturer designation and relationship to the PA-48E label", "Boundaries between the Enforcer, its Mustang ancestry and earlier development aircraft", "Configuration-dependent airframe, turboprop propulsion and aircraft systems", "Evidence distinguishing intended close-support capability from demonstrated performance", "Requirements for assessing surviving examples, missing equipment and permitted activities" ], "out_of_scope": [ "The North American P-51 Mustang design as a whole", "Earlier Cavalier aircraft except where needed to establish Enforcer lineage", "Standalone models of engines, propellers, weapons or avionics", "Operational targeting, weapon employment and combat tactics", "Ownership transactions and museum administration", "Individual aircraft maintenance logs as independent registry things" ], "distinguishing_features": [ "Require documentary identification as a Piper PA-48 or a substantiated equivalent designation; Mustang-like appearance alone is insufficient.", "Distinguish the turboprop Enforcer from piston-powered P-51 configurations using propulsion and airframe records.", "Treat Mustang ancestry as a lineage relation rather than proof of airframe identity or parts interchangeability.", "Distinguish USAF evaluation participation from operational military service or an official military designation.", "Separate a documented evaluation configuration from a surviving display airframe with equipment removed." ], "characteristics": [ { "name": "Documented designation", "kind": "category", "unit_or_values": "PA-48; PA-48E; other source wording; unresolved equivalence", "why_it_matters": "Prevents an unsupported merger or split between designation variants." }, { "name": "Aircraft identity anchor", "kind": "relation", "unit_or_values": "Manufacturer serial number, civil registration and dated supporting record", "why_it_matters": "Keeps evidence about one Enforcer example from becoming a claim about every example." }, { "name": "Configuration baseline", "kind": "relation", "unit_or_values": "Identified aircraft, date, modification state and configuration document", "why_it_matters": "Makes technical and historical comparisons meaningful." }, { "name": "Propulsion installation", "kind": "relation", "unit_or_values": "Documented engine, reduction drive and propeller combination", "why_it_matters": "Identifies the turboprop installation without assuming that surviving examples retain it." }, { "name": "Installed power", "kind": "measurement", "unit_or_values": "kW or shaft horsepower, with rating duration and operating conditions", "why_it_matters": "Prevents engine ratings from being mistaken for continuously available aircraft performance." }, { "name": "Airframe dimensions", "kind": "measurement", "unit_or_values": "Wingspan, length and height in m; wing area in m²; configuration specified", "why_it_matters": "Supports identification, transport planning and comparison with related designs." }, { "name": "Mass and balance limits", "kind": "measurement", "unit_or_values": "Mass in kg; center of gravity in documented datum units or percent mean aerodynamic chord", "why_it_matters": "Missing engines, stores or restored components can substantially change handling assumptions." }, { "name": "Capability evidence status", "kind": "category", "unit_or_values": "Proposed; installed; ground-tested; flight-tested; authorized; unknown", "why_it_matters": "Separates advertised close-support functions from substantiated capability." }, { "name": "Preservation and operating state", "kind": "state", "unit_or_values": "Documented flight status; static display; storage; restoration; incomplete; unknown", "why_it_matters": "Appearance and historical flight testing do not establish present operability." }, { "name": "Applicable operating authority", "kind": "relation", "unit_or_values": "Dated registration, certificate, operating limitations or other applicable authorization", "why_it_matters": "Establishes the basis for assessing a proposed activity on a particular aircraft." } ], "affordances": [ "Identify a candidate Enforcer using designation, serial and configuration evidence.", "Compare documented Enforcer configurations and identify changes that affect interpretation.", "Classify performance and mission claims by the strength and scope of their evidence.", "Assess whether a surviving example is complete, altered or suitable only for static interpretation.", "Determine which manuals, inspections and authorizations are missing before movement, restoration or operation.", "Link Enforcer-specific requirements to broader aircraft and component models." ], "agent_conduct": { "may": [ "Identify photographs or surviving airframes as this experimental turboprop attack aircraft.", "Describe its lineage and evaluation history from documented sources." ], "must_not": [ "Present it as an operational combat type when it remained experimental.", "Operate or move surviving airframes without the owner's authority.", "Invent performance figures where records disagree." ], "requires_human": [ "Loans, restoration or movement of a surviving airframe." ] }, "ethics": { "considerations": [ "Light attack aircraft are designed for counter-insurgency, which bears on civilian harm.", "Accurate history helps public debate on such weapons." ], "affected_parties": [ "Historians and museums", "Communities affected by counter-insurgency conflicts" ] }, "owners": { "steward": "The museum or owner of any surviving example or remains; the state for items in public collections.", "master_systems": [] }, "visual_identification": [ "Second World War fighter-style airframe fitted with a turboprop engine.", "Underwing hardpoints for external stores.", "Very few examples, identified by their serials." ], "failure_modes_and_hazards": [ "Modified piston-era airframes carried uncertain fatigue life.", "Preserved airframes may hold hazardous materials." ], "what_it_is_for": [ "This experimental aircraft design is encountered in military aviation history, evaluation records and museum collections.", "It was developed to explore a turboprop aircraft for light ground-attack and close air support roles.", "Preservation and technical research use configuration records to distinguish individual prototypes and interpret surviving airframes." ], "standards_and_regulation": [ "Title 14 CFR Part 21, administered by the United States Federal Aviation Administration, governs experimental airworthiness certification when an example is presented for United States civil certification.", "Title 14 CFR Part 91, administered by the United States Federal Aviation Administration, provides general operating and flight rules when an example operates within its civil aviation scope." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q6119816: PA-48 Enforcer", "url": "https://www.wikidata.org/wiki/Q6119816", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Piper PA-48 Enforcer", "url": "https://en.wikipedia.org/wiki/Piper_PA-48_Enforcer", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "identity-and-lineage", "name": "Identity and lineage", "description": "Establishes what the registry name denotes and where related aircraft fall outside its boundary.", "rationale": "The Enforcer's Mustang resemblance and overlapping designation language make misidentification particularly likely.", "layers": [ { "id": "designation-evidence", "name": "Designation evidence", "description": "Connects the registry entry to documentary names and identifiable examples.", "findings": [ { "id": "pa-48e-documentary-anchor", "name": "PA-48E documentary anchor", "description": "The museum identifies N481PE, construction number 48-8301001, as a Piper PA-48E. This anchors a documented example without settling every use of PA-48 versus PA-48E. [NMUSAF aircraft record](https://www.nationalmuseum.af.mil/Visit/Museum-Exhibits/Fact-Sheets/Display/Article/195782/1983-piper-pa-48e-enforcer/)", "questions": [ { "text": "Which manufacturer records establish the relationship between PA-48 and PA-48E?", "kind": "definition", "id": "pa-48e-documentary-anchor-q01" }, { "text": "Which serial numbers and registrations belong to the design covered by this entry?", "kind": "provenance", "id": "pa-48e-documentary-anchor-q02" } ] } ] }, { "id": "mustang-boundary", "name": "Mustang boundary", "description": "Separates design ancestry from shared identity.", "findings": [ { "id": "ancestry-without-equivalence", "name": "Ancestry without equivalence", "description": "The museum describes the Enforcer as P-51-derived but essentially a new aircraft. Shared ancestry must not imply identical structure or interchangeable parts. [NMUSAF aircraft record](https://www.nationalmuseum.af.mil/Visit/Museum-Exhibits/Fact-Sheets/Display/Article/195782/1983-piper-pa-48e-enforcer/)", "questions": [ { "text": "Which documented design changes distinguish the PA-48 from the P-51 and earlier Enforcer development aircraft?", "kind": "boundary", "id": "ancestry-without-equivalence-q01" }, { "text": "Which components, if any, have documented interchangeability with predecessor aircraft?", "kind": "provenance", "id": "ancestry-without-equivalence-q02" } ] } ] } ] }, { "id": "airframe-and-propulsion", "name": "Airframe and propulsion", "description": "Defines the evidence needed to recognize and assess the Enforcer's physical configuration.", "rationale": "The turboprop installation and redesigned airframe require their own configuration evidence.", "layers": [ { "id": "turboprop-installation", "name": "Turboprop installation", "description": "Connects engine identity to the complete installed propulsion system.", "findings": [ { "id": "documented-engine-installation", "name": "Documented engine installation", "description": "The museum records an Avco-Lycoming YT-55-L-9 installation for N481PE. Applicability to other configurations requires separate evidence. [NMUSAF aircraft record](https://www.nationalmuseum.af.mil/Visit/Museum-Exhibits/Fact-Sheets/Display/Article/195782/1983-piper-pa-48e-enforcer/)", "questions": [ { "text": "Which engine, propeller and reduction-drive combination belongs to each documented PA-48 baseline?", "kind": "provenance", "id": "documented-engine-installation-q01" }, { "text": "What power ratings, fuel specifications and operating limits apply to that installation?", "kind": "measurement", "id": "documented-engine-installation-q02" } ] } ] }, { "id": "geometry-and-loading", "name": "Geometry and loading", "description": "Associates dimensions and structural limits with a specific Enforcer baseline.", "findings": [ { "id": "configuration-bound-physical-limits", "name": "Configuration-bound physical limits", "description": "The model should require Enforcer-specific geometry, mass and loading evidence rather than inherit P-51 values.", "questions": [ { "text": "What dimensions, empty mass and maximum permitted mass are documented for the selected configuration?", "kind": "measurement", "id": "configuration-bound-physical-limits-q01" }, { "text": "How do fuel, external equipment and removed components affect the documented center-of-gravity envelope?", "kind": "measurement", "id": "configuration-bound-physical-limits-q02" } ] } ] } ] }, { "id": "close-support-capability-evidence", "name": "Close-support capability evidence", "description": "Separates the Enforcer's intended role from demonstrated aircraft capability.", "rationale": "An evaluated attack-aircraft design must not be modeled as though every proposed capability entered service.", "layers": [ { "id": "role-and-equipment", "name": "Role and equipment", "description": "Relates the intended mission to documented equipment states.", "findings": [ { "id": "intended-close-support-role", "name": "Intended close-support role", "description": "The museum identifies the Enforcer as a light close-support and ground-attack aircraft. Equipment-specific capability remains a separate evidence requirement. [NMUSAF aircraft record](https://www.nationalmuseum.af.mil/Visit/Museum-Exhibits/Fact-Sheets/Display/Article/195782/1983-piper-pa-48e-enforcer/)", "questions": [ { "text": "Which mission systems and external-store provisions were proposed, installed or actually tested?", "kind": "provenance", "id": "intended-close-support-role-q01" }, { "text": "Which apparent equipment features on surviving examples are functional, inert or reproductions?", "kind": "boundary", "id": "intended-close-support-role-q02" } ] } ] }, { "id": "performance-qualification", "name": "Performance qualification", "description": "Requires conditions and evidence behind performance claims.", "findings": [ { "id": "test-conditioned-performance", "name": "Test-conditioned performance", "description": "Speed, range, endurance and runway-performance values should identify their configuration, conditions and status as measured results or estimates.", "questions": [ { "text": "Which flight-test records substantiate published Enforcer performance figures?", "kind": "provenance", "id": "test-conditioned-performance-q01" }, { "text": "What mass, altitude, atmospheric conditions and external configuration accompany each figure?", "kind": "measurement", "id": "test-conditioned-performance-q02" } ] } ] } ] }, { "id": "evaluation-and-operating-authority", "name": "Evaluation and operating authority", "description": "Interprets the aircraft's test history and the documentary basis for any proposed operation.", "rationale": "USAF evaluation does not by itself establish service adoption, civil certification or present permission to fly.", "layers": [ { "id": "program-status", "name": "Program status", "description": "Distinguishes evaluation aircraft from an operational fleet.", "findings": [ { "id": "evaluation-without-adoption", "name": "Evaluation without adoption", "description": "The museum reports two aircraft flight-tested in 1984, no USAF order and no official military designation. [NMUSAF aircraft record](https://www.nationalmuseum.af.mil/Visit/Museum-Exhibits/Fact-Sheets/Display/Article/195782/1983-piper-pa-48e-enforcer/)", "questions": [ { "text": "Which evaluation reports identify the aircraft, objectives and demonstrated results?", "kind": "provenance", "id": "evaluation-without-adoption-q01" }, { "text": "Which claims refer to evaluation participation rather than operational acceptance?", "kind": "boundary", "id": "evaluation-without-adoption-q02" } ] } ] }, { "id": "controls-and-authorizations", "name": "Controls and authorizations", "description": "Connects Enforcer-specific operating documentation to a proposed activity.", "findings": [ { "id": "activity-specific-documentary-basis", "name": "Activity-specific documentary basis", "description": "The model should record applicable manuals, control configurations, limitations and authorizations without importing operating procedures from a Mustang or another T55-powered aircraft.", "questions": [ { "text": "Which manuals document the PA-48 cockpit controls, propulsion states and emergency systems?", "kind": "provenance", "id": "activity-specific-documentary-basis-q01" }, { "text": "What current records establish whether the particular aircraft may undergo a ground run or flight?", "kind": "action", "id": "activity-specific-documentary-basis-q02" }, { "text": "Which issuing bodies, document revisions and aircraft-specific limitations govern the proposed activity?", "kind": "boundary", "id": "activity-specific-documentary-basis-q03" } ] } ] } ] }, { "id": "surviving-aircraft-and-restoration", "name": "Surviving aircraft and restoration", "description": "Interprets preserved Enforcers as potentially incomplete or altered representatives of the design.", "rationale": "A display aircraft can retain recognizable appearance while lacking systems essential to its historical configuration.", "layers": [ { "id": "completeness-and-authenticity", "name": "Completeness and authenticity", "description": "Separates original equipment, missing equipment and restoration substitutions.", "findings": [ { "id": "dated-condition-evidence", "name": "Dated condition evidence", "description": "A historical museum exchange record describes N481PE without its engine and as non-airworthy; this condition must remain tied to that record's date. [NMUSAF aircraft record](https://www.nationalmuseum.af.mil/Visit/Museum-Exhibits/Fact-Sheets/Display/Article/195782/1983-piper-pa-48e-enforcer/)", "questions": [ { "text": "What dated inspection establishes the example's current completeness and condition?", "kind": "provenance", "id": "dated-condition-evidence-q01" }, { "text": "Which original, removed, substituted or replica components distinguish its present state from the evaluation baseline?", "kind": "boundary", "id": "dated-condition-evidence-q02" } ] } ] }, { "id": "maintenance-and-handling-evidence", "name": "Maintenance and handling evidence", "description": "Identifies the information needed for preservation, movement and restoration decisions.", "findings": [ { "id": "enforcer-specific-support-requirements", "name": "Enforcer-specific support requirements", "description": "The model should identify documented inspection needs, consumables, support points and component compatibility for the Enforcer configuration; neither visual restoration nor predecessor experience establishes these.", "questions": [ { "text": "Which maintenance records identify corrosion, fatigue, component life limits or unresolved defects on the example?", "kind": "provenance", "id": "enforcer-specific-support-requirements-q01" }, { "text": "What documented towing, lifting and support requirements apply with its current equipment and mass distribution?", "kind": "action", "id": "enforcer-specific-support-requirements-q02" }, { "text": "Which replacement parts, fluids and preservation materials have documented compatibility with the installed systems?", "kind": "action", "id": "enforcer-specific-support-requirements-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": [ "Distinguish the early Enforcer demonstrators from the later PA-48 prototypes before assigning construction dates, airframe counts or specifications.", "The Mustang ancestry does not imply interchangeability of structures, engines or systems.", "Exact performance, dimensions, engine ratings and evaluation outcomes require verification; none are asserted here." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of PA-48 Enforcer 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": "Piper aircraft model designation", "value_or_pattern": "PA-48", "note": "Enforcer is the aircraft's name; PA-48 identifies the design, not an individual airframe." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of PA-48 Enforcer 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": [ "Prototype flight testing and demonstrations of a turboprop light-attack aircraft.", "United States Air Force evaluation for potential ground-attack and close-air-support missions." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of PA-48 Enforcer 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": "North American P-51 Mustang", "difference": "The P-51 was a piston-engine fighter; the PA-48 was a substantially reworked turboprop ground-attack design descended from it." }, { "name": "Cavalier Turbo Mustang III", "difference": "This was an earlier turboprop Mustang development that preceded Piper's Enforcer program, rather than the PA-48 itself." }, { "name": "Close-air-support aircraft", "difference": "This is a mission-based aircraft category; the PA-48 is one specific experimental design intended for that role." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of PA-48 Enforcer this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend PA-48 to cover only the later evaluation design, or also earlier aircraft marketed as Enforcer, and what primary documentation settles the PA-48/PA-48E relationship?", "Which manufacturer drawings and manuals establish configuration-specific dimensions, weights, power ratings, structural limits and component interchangeability?", "Which original evaluation reports distinguish measured performance and tested mission equipment from proposals or publicity claims?", "What certification basis, operating limitations and system-specific safety requirements applied to each evaluation aircraft?", "What are the current identities, locations, completeness and documented operating status of surviving examples, beyond historical museum records?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 14, "questions": 26 } }