{ "model": { "rank": 4013, "code": "thing-q133194", "model_id": "vr.tr.kamikaze", "name": "Kamikaze", "purpose": "Enable an AI agent to identify, contextualise and assess records of Kamikaze as an organised military special-attack phenomenon while distinguishing formations, personnel, missions and later uses of the name.", "family": "Thing Registry", "category": "Society, people and institutions", "status": "research-draft", "kind": "thing", "plane": "SOC", "domain": "SOC.ORG", "industry": "", "version": "", "url": "/models/thing/q133194/", "tier": 2, "score": 79, "payload": { "layer": "wikidata", "aliases": [], "aliasCount": 0, "merged": 0, "knownIn": 79, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q133194", "url": "https://www.wikidata.org/wiki/Q133194", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T19:17:12Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 20, "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: 01a08799-5ce8-7a00-919e-367e3207a34c\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Kamikaze\nSense to describe: (none recorded)\nDomain code: SOC.ORG\nAlso known as: (none)\n\n\nContext for this batch of 695 things:\n# Batch 004: 1001 registe", "usd": 0, "recall": true }, "codex": { "seconds": 62.7, "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: 01a08799-5cf1-7652-a380-8d3d7e36dbfc\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Kamikaze\nRegistry id: vr.tr.kamikaze\nPlane / domain: SOC / SOC.ORG\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContex" } } }, "metaModel": { "id": "THING-Q133194", "registryId": "vr.tr.kamikaze", "name": "Kamikaze", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "SOC.ORG" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q133194/", "model": { "registry_id": "vr.tr.kamikaze", "name": "Kamikaze", "purpose": "Enable an AI agent to identify, contextualise and assess records of Kamikaze as an organised military special-attack phenomenon while distinguishing formations, personnel, missions and later uses of the name.", "definition": "In its usual military-historical sense, kamikaze refers to Japanese airmen and special-attack units that carried out deliberately fatal aircraft attacks against Allied ships during the closing phase of the Second World War.", "scope_statement": "Provisionally, this model owns the institutional organisation of Japanese Kamikaze air special-attack formations during the Second World War, including authority, membership, mission designation and historical continuity; the intended registry referent remains unresolved because no definition is recorded.", "in_scope": [ "Evidence establishing which military formation or institutional practice the registry name denotes", "Formation boundaries, parent commands and authority to designate special-attack units", "Personnel assignment, training status and evidence concerning consent or coercion", "Institutional designation of missions involving intended aircraft impact and pilot death", "Formation activation, reorganisation, cessation and subsequent historical attribution" ], "out_of_scope": [ "Aircraft engineering, weapon construction and attack execution procedures", "Complete biographies and psychological profiles of individual pilots", "General models of suicide attacks across different historical contexts", "Unrelated organisations, products or creative works named Kamikaze", "Meteorological events and earlier historical senses of the name", "Memorial institutions and commemorative works as independently governed entities" ], "distinguishing_features": [ "A matching institutional record must establish a connection to Japanese wartime air special-attack organisation; the name alone is insufficient.", "A formation requires evidence of collective organisation and command attachment; a pilot, aircraft or individual sortie is a related entity.", "Mission classification depends on evidence of intended fatal aircraft impact, rather than casualty rate or mission danger alone.", "Deliberately assigned special-attack service must be distinguished from an improvised final action during an otherwise conventional sortie.", "Shared terminology does not establish that separately commanded formations constituted one organisation." ], "characteristics": [ { "name": "Referent type", "kind": "category", "unit_or_values": "umbrella institutional practice | particular formation | personnel category | unresolved", "why_it_matters": "Determines whether the SOC.ORG placement describes the intended thing or conceals a classification mismatch." }, { "name": "Attested designation", "kind": "relation", "unit_or_values": "original-language name linked to issuing body, dated document and translation", "why_it_matters": "Separates contemporary identification from later labels and translation choices." }, { "name": "Command attachment", "kind": "relation", "unit_or_values": "parent service, command or formation, with effective dates and supporting evidence", "why_it_matters": "Establishes institutional boundaries without treating every Kamikaze-associated unit as one body." }, { "name": "Personnel assignment basis", "kind": "category", "unit_or_values": "documented volunteering | documented compulsory assignment | mixed or contested evidence | unknown", "why_it_matters": "Prevents assignment records from being treated as proof of freely given consent." }, { "name": "Mission intention", "kind": "category", "unit_or_values": "designated fatal-impact mission | conventional mission | improvised fatal action | disputed | unknown", "why_it_matters": "Distinguishes the intended special-attack role from outcomes reconstructed after a loss." }, { "name": "Institutional lifecycle", "kind": "state", "unit_or_values": "forming | training | operational | reorganised | ceased | unresolved, each time-qualified", "why_it_matters": "Supports historical state assessment without implying present operational existence." }, { "name": "Attributed personnel strength", "kind": "measurement", "unit_or_values": "persons, with date, formation boundary and inclusion rule", "why_it_matters": "Makes counts comparable while separating assigned personnel, trainees and mission participants." }, { "name": "Evidence agreement", "kind": "state", "unit_or_values": "corroborated | single-source | conflicting | unsupported", "why_it_matters": "Controls whether an agent may present an attribution as established or must preserve uncertainty." } ], "affordances": [ "Classify a record as a formation, person, mission or unrelated namesake before linking it.", "Trace a formation's command attachment and institutional changes through dated evidence.", "Compare accounts of personnel assignment while preserving uncertainty about consent and coercion.", "Distinguish designated special-attack missions from dangerous conventional sorties and improvised actions.", "Reconcile competing names, counts and attributions without erasing source disagreements.", "Produce historically bounded catalogue descriptions that distinguish documented roles from commemorative interpretation." ] }, "sources": [], "structure": { "bundles": [ { "id": "referent-and-designation", "name": "Referent and designation", "description": "Resolve what Kamikaze names in this registry and how that referent appears in historical records.", "rationale": "The entry lacks a definition, and its organisational placement cannot establish whether it denotes one formation or a broader practice.", "layers": [ { "id": "institutional-sense", "name": "Institutional sense", "description": "Test the provisional organisational interpretation against the originating registry evidence.", "findings": [ { "id": "referent-resolution", "name": "Referent resolution", "description": "Record whether the entry denotes a particular formation, an umbrella practice or a personnel category before making institutional identity claims.", "questions": [ { "text": "Which originating record or identifier establishes the intended sense of Kamikaze?", "kind": "provenance", "id": "referent-resolution-q01" }, { "text": "Does SOC.ORG describe the referent itself or only the military context associated with it?", "kind": "boundary", "id": "referent-resolution-q02" } ] } ] }, { "id": "historical-naming", "name": "Historical naming", "description": "Track original designations, translations and retrospective terminology.", "findings": [ { "id": "designation-equivalence", "name": "Designation equivalence", "description": "Treat equivalence between Kamikaze and other special-attack designations as a sourced, context-specific relationship.", "questions": [ { "text": "Which original-language designation appears in the relevant contemporary records, and who used it?", "kind": "provenance", "id": "designation-equivalence-q01" }, { "text": "In this record, does Kamikaze identify a named unit, a wider category or a later descriptive label?", "kind": "definition", "id": "designation-equivalence-q02" } ] } ] } ] }, { "id": "formation-and-command", "name": "Formation and command", "description": "Describe how the relevant special-attack formations were constituted, directed and changed.", "rationale": "Military command relationships and formation orders are more informative here than assuming independent corporate registration or legal personality.", "layers": [ { "id": "constituting-authority", "name": "Constituting authority", "description": "Identify evidence that establishes a formation and its special-attack role.", "findings": [ { "id": "formation-mandate", "name": "Formation mandate", "description": "Require dated evidence for formation identity, institutional authority and designation of its role.", "questions": [ { "text": "What order or other evidence establishes the formation and assigns its special-attack role?", "kind": "provenance", "id": "formation-mandate-q01" }, { "text": "Which command held authority over personnel assignment and mission authorisation during the period being described?", "kind": "definition", "id": "formation-mandate-q02" } ] } ] }, { "id": "continuity-and-cessation", "name": "Continuity and cessation", "description": "Distinguish changes within a formation from replacement, reassignment or termination.", "findings": [ { "id": "dated-organisational-boundaries", "name": "Dated organisational boundaries", "description": "Represent command transfers, name reuse and cessation without inferring continuity from a shared special-attack label.", "questions": [ { "text": "Which dated records distinguish reorganisation of this formation from creation of a different formation?", "kind": "boundary", "id": "dated-organisational-boundaries-q01" }, { "text": "What evidence establishes when its special-attack role or institutional existence ceased?", "kind": "provenance", "id": "dated-organisational-boundaries-q02" } ] } ] } ] }, { "id": "personnel-and-assignment", "name": "Personnel and assignment", "description": "Represent participation in special-attack service without collapsing institutional assignment into individual intention.", "rationale": "Pilot identity, support membership, assignment and consent answer different questions and require different evidence.", "layers": [ { "id": "participation-boundaries", "name": "Participation boundaries", "description": "Separate assigned pilots, trainees, supporting personnel and people recorded on particular missions.", "findings": [ { "id": "role-specific-membership", "name": "Role-specific membership", "description": "Attribute people and personnel totals to a stated role, formation and date.", "questions": [ { "text": "Does the evidence establish assignment as a special-attack pilot, another formation role or participation in a particular mission?", "kind": "boundary", "id": "role-specific-membership-q01" }, { "text": "Which roles and dates are included in a reported personnel total, and how are transfers or duplicate records handled?", "kind": "measurement", "id": "role-specific-membership-q02" } ] } ] }, { "id": "consent-and-testimony", "name": "Consent and testimony", "description": "Assess what records can establish about volunteering, compulsion and personal accounts.", "findings": [ { "id": "assignment-is-not-consent", "name": "Assignment and consent evidence", "description": "Keep administrative assignment, public statements and personal testimony distinct when assessing an individual's circumstances.", "questions": [ { "text": "What evidence supports a claim of volunteering or compulsory assignment, and under what conditions was it produced?", "kind": "provenance", "id": "assignment-is-not-consent-q01" }, { "text": "How should an agent describe participation when administrative records and personal testimony conflict?", "kind": "action", "id": "assignment-is-not-consent-q02" } ] } ] } ] }, { "id": "mission-attribution-and-historical-record", "name": "Mission attribution and historical record", "description": "Connect institutional roles to documented missions and assess subsequent claims without supplying operational guidance.", "rationale": "A formation's designation, a mission's intended character and its reported outcome must be evaluated separately.", "layers": [ { "id": "mission-classification", "name": "Mission classification", "description": "Identify evidence of assigned mission intention independently of whether an aircraft or pilot returned.", "findings": [ { "id": "designated-special-attack", "name": "Designated special attack", "description": "Classify a mission using evidence of its intended fatal-impact role; loss alone does not establish that classification.", "questions": [ { "text": "Which order, briefing record or corroborated account establishes the mission's intended special-attack character?", "kind": "provenance", "id": "designated-special-attack-q01" }, { "text": "What distinguishes this mission from a conventional sortie that ended in an improvised fatal attack?", "kind": "boundary", "id": "designated-special-attack-q02" } ] } ] }, { "id": "claims-and-retrospective-attribution", "name": "Claims and retrospective attribution", "description": "Evaluate reported mission totals, losses and later descriptions against their evidence and counting rules.", "findings": [ { "id": "reconciled-historical-claims", "name": "Reconciled historical claims", "description": "Preserve distinctions among wartime reports, corroborated outcomes and commemorative accounts, including unresolved disagreements.", "questions": [ { "text": "Does a reported total count planned missions, departures, attempted impacts or corroborated outcomes?", "kind": "measurement", "id": "reconciled-historical-claims-q01" }, { "text": "When contemporary records and later commemorative accounts disagree, which claims can be retained and which require explicit uncertainty?", "kind": "action", "id": "reconciled-historical-claims-q02" } ] } ] } ] }, { "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": [ "The name has no recorded sense; this answer assumes the common Second World War military meaning rather than another entity named Kamikaze.", "SOC.ORG fits the special-attack units, but kamikaze also denotes their personnel and attacks; it does not identify one organization with a single founding instrument.", "The term also refers historically to the 'divine wind' associated with the Mongol invasions of Japan; the intended registry referent should be checked before publication." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Kamikaze 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": [ "Imperial Japanese Navy special-attack aviation units", "Imperial Japanese Army special-attack aviation units" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Kamikaze 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": [ "Attacks intended to damage or sink Allied warships and transports by crashing explosive-laden aircraft into them.", "Organized deployment during the Philippines campaign and the battle for Okinawa." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Kamikaze 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": [ "The intended attack entailed the pilot's death.", "Aircraft could be intercepted or shot down before reaching their targets.", "Navigation errors, mechanical failures and fuel limitations could prevent attacks from reaching their targets.", "Successful strikes could cause shipboard fires, explosions, casualties and sinking." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Kamikaze 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": [ "English usage commonly groups Japanese suicide aviation attacks under 'kamikaze'; Japanese terminology also includes tokkōtai for special-attack units, a broader category extending beyond aviation." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Kamikaze 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": "Tokkōtai", "difference": "Special-attack units included aviation and other methods; kamikaze usually denotes the aviation subset in English." }, { "name": "Kaiten", "difference": "Kaiten were Japanese crewed suicide torpedoes, rather than aircraft or aviation units." }, { "name": "Conventional aerial attack", "difference": "A conventional attack normally provides for the aircrew's survival and return; a kamikaze strike makes the aircraft's deliberate impact the means of attack." }, { "name": "Loitering munition", "difference": "A loitering munition is an uncrewed weapon sometimes informally called a kamikaze drone; it is not a historical Japanese airman or military unit." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Kamikaze this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the originating registry record intend a specific military formation, the wider organised special-attack phenomenon or the pilots as a category?", "Does an existing Vercy world model already cover this referent, requiring a registry link rather than a separate publication?", "Which contemporary designations and formation boundaries justify the scope of the English label Kamikaze in this entry?", "Which accessible formation orders, personnel records and personal accounts can substantiate command relationships and assignment conditions?", "Should the resolved registry scope include non-aviation special-attack organisations, or should those remain neighbouring concepts?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 14, "questions": 22 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "organisation or institution", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a Kamikaze, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to identify, contextualise and assess records of Kamikaze as an organised military special-attack phenomenon while distinguishing formations, personnel, missions and later uses of the name.", "characteristics": { "substance": "social", "origin": "conceptual", "agency": "collective" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Described in 79 Wikipedia languages, which is a measure of how widely the thing is known, not of how important it is." ], "openQuestionsForResearch": [ "Which of the bundles below does a real task actually need, and which are ceremony?", "What does this thing have that the facets do not capture at all?", "Which neighbouring kind is most often confused with a Kamikaze, and on what evidence are they told apart?" ], "whatItIsMadeOf": "a social arrangement between people", "physicalCharacter": [ "Acts through people, and only through them.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "observe it, measure it, record its state" ], "howItIsRecognised": [ "Nothing to see. Recognised by name, register entry and the people acting in its name, and those change while it stays the same body." ], "relatedModels": [], "standing": "Described in 79 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one Kamikaze from another, and a Kamikaze from things that resemble it.", "rationale": "Recognition comes before every other claim. Without stable identity nothing else in the model can be trusted to be about the same thing twice.", "layers": [ { "id": "naming-and-identifiers", "name": "Names and identifiers", "description": "The names this thing goes by and the identifiers that survive translation and time.", "findings": [ { "id": "preferred-name-and-aliases", "name": "Preferred name, aliases and local names", "description": "Which name to use, which names mean the same thing, and which merely sound similar.", "questions": [ { "id": "preferred-name-and-aliases-q01", "text": "What identifies and describes the name of a Kamikaze, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "preferred-name-and-aliases-q02", "text": "Who or what asserted this about the name of a Kamikaze, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "preferred-name-and-aliases-q03", "text": "What may an agent decide or do once the name of a Kamikaze is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "stable-identifiers", "name": "Stable identifiers and external keys", "description": "Identifiers that keep pointing at this kind of thing across systems and languages.", "questions": [ { "id": "stable-identifiers-q01", "text": "What identifies and describes an identifier for a Kamikaze, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stable-identifiers-q02", "text": "Who or what asserted this about an identifier for a Kamikaze, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stable-identifiers-q03", "text": "What may an agent decide or do once an identifier for a Kamikaze is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "classification-and-granularity", "name": "Classification and granularity", "description": "Where a Kamikaze sits among kinds, and how finely a task needs to cut it.", "findings": [ { "id": "kind-and-parents", "name": "Kind, parents and neighbouring kinds", "description": "The classes this thing belongs to and the ones it is next to.", "questions": [ { "id": "kind-and-parents-q01", "text": "What identifies and describes the kind of a Kamikaze, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "kind-and-parents-q02", "text": "Who or what asserted this about the kind of a Kamikaze, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "kind-and-parents-q03", "text": "What may an agent decide or do once the kind of a Kamikaze is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "distinguishing-features", "name": "Distinguishing features", "description": "What separates a Kamikaze from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Kamikaze, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "distinguishing-features-q02", "text": "Who or what asserted this about what distinguishes a Kamikaze, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "distinguishing-features-q03", "text": "What may an agent decide or do once what distinguishes a Kamikaze is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "state-and-lifecycle", "name": "State and lifecycle", "description": "The states a Kamikaze passes through and the events that move it between them.", "rationale": "Most decisions about a thing depend on what state it is in now, which is a claim with a time on it, not a property.", "layers": [ { "id": "lifecycle-stages", "name": "Lifecycle stages", "description": "From coming into existence to ceasing to be one of these.", "findings": [ { "id": "stages-and-transitions", "name": "Stages and transitions", "description": "The stages worth naming and what moves a Kamikaze between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Kamikaze, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stages-and-transitions-q02", "text": "Who or what asserted this about the lifecycle of a Kamikaze, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stages-and-transitions-q03", "text": "What may an agent decide or do once the lifecycle of a Kamikaze is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "observations-and-status", "name": "Observations and current status", "description": "What is observed about a Kamikaze, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Kamikaze is recorded so that it can be superseded rather than overwritten.", "questions": [ { "id": "observation-record-q01", "text": "What identifies and describes an observation of a Kamikaze, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "observation-record-q02", "text": "Who or what asserted this about an observation of a Kamikaze, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "observation-record-q03", "text": "What may an agent decide or do once an observation of a Kamikaze is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "people-and-responsibility", "name": "People, roles and responsibility", "description": "Who stands in what relation to a Kamikaze.", "rationale": "Social things are defined by the relations people hold to them, and those relations change without the thing changing.", "layers": [ { "id": "roles-and-parties", "name": "Roles and parties", "description": "The roles that exist around a Kamikaze and who fills them.", "findings": [ { "id": "role-assignments", "name": "Role assignments and their validity", "description": "Who holds which role over a Kamikaze, from when, and on whose authority.", "questions": [ { "id": "role-assignments-q01", "text": "What identifies and describes a role over a Kamikaze, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "role-assignments-q02", "text": "Who or what asserted this about a role over a Kamikaze, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "role-assignments-q03", "text": "What may an agent decide or do once a role over a Kamikaze is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "ownership-and-accountability", "name": "Ownership and accountability", "description": "Who answers for a Kamikaze and who may decide about it.", "findings": [ { "id": "accountability", "name": "Accountability and decision rights", "description": "Where responsibility for a Kamikaze sits when something goes wrong.", "questions": [ { "id": "accountability-q01", "text": "What identifies and describes responsibility for a Kamikaze, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "accountability-q02", "text": "Who or what asserted this about responsibility for a Kamikaze, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "accountability-q03", "text": "What may an agent decide or do once responsibility for a Kamikaze is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "legal-identity", "name": "Legal identity and mandate", "description": "What Kamikaze is in law and what it exists to do.", "rationale": "Legal identity survives changes of name, address, staff and premises, which is exactly why it must be recorded separately from all of them.", "layers": [ { "id": "registration", "name": "Legal form and registration", "description": "Form, register, identifiers and jurisdiction.", "findings": [ { "id": "registration-record", "name": "Registration and identifiers", "description": "What names this body unambiguously in law.", "questions": [ { "id": "registration-record-q01", "text": "What legal form does Kamikaze take, in which register, under which identifier?", "kind": "definition" }, { "id": "registration-record-q02", "text": "What survives a rename, a merger or a move of premises, and what does not?", "kind": "boundary" } ] } ] }, { "id": "mandate", "name": "Mandate and governing instrument", "description": "The purpose it is bound to and the document that binds it.", "findings": [ { "id": "mandate-record", "name": "Mandate and its source", "description": "What it may do, and the instrument that says so.", "questions": [ { "id": "mandate-record-q01", "text": "What is the mandate of Kamikaze, and which founding or governing instrument grants it?", "kind": "provenance" }, { "id": "mandate-record-q02", "text": "What lies outside the mandate, and what should an agent do when asked for it?", "kind": "action" } ] } ] } ] }, { "id": "governance-and-membership", "name": "Governance, membership and decision rights", "description": "Who decides in Kamikaze and who belongs to it.", "rationale": "Authority inside an organisation is held by roles, not people, and an agent needs to know which role can commit it.", "layers": [ { "id": "decision-rights", "name": "Decision rights", "description": "Bodies, offices and what each may bind.", "findings": [ { "id": "authority-map", "name": "Who may bind the organisation", "description": "The offices that can commit it and their limits.", "questions": [ { "id": "authority-map-q01", "text": "Which bodies or offices of Kamikaze may take which decisions, and up to what limit?", "kind": "definition" }, { "id": "authority-map-q02", "text": "What evidence shows that a given person currently holds that office?", "kind": "provenance" } ] } ] }, { "id": "membership", "name": "Membership and affiliation", "description": "Who counts as part of it and on what terms.", "findings": [ { "id": "membership-rules", "name": "Membership and its evidence", "description": "Classes of member, how membership starts and ends.", "questions": [ { "id": "membership-rules-q01", "text": "What kinds of membership or affiliation does Kamikaze have, and how does each begin and end?", "kind": "definition" }, { "id": "membership-rules-q02", "text": "What may a member do in its name, and what may they not?", "kind": "action" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a Kamikaze came from and when it held.", "rationale": "A claim without a source and a time cannot be superseded, only overwritten, and an agent that overwrites loses the ability to explain itself.", "layers": [ { "id": "source-and-authority", "name": "Source and authority", "description": "Who said it, on what evidence, and how strongly.", "findings": [ { "id": "claim-provenance", "name": "Claim provenance and confidence", "description": "The authority behind each claim about a Kamikaze and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Kamikaze, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "claim-provenance-q02", "text": "Who or what asserted this about a claim about a Kamikaze, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "claim-provenance-q03", "text": "What may an agent decide or do once a claim about a Kamikaze is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "time-and-versions", "name": "Time, versions and supersession", "description": "When a claim was true, when it was learnt, and what replaced it.", "findings": [ { "id": "validity-and-supersession", "name": "Validity period and supersession", "description": "How an old claim about a Kamikaze is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Kamikaze, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "validity-and-supersession-q02", "text": "Who or what asserted this about the validity of a claim about a Kamikaze, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "validity-and-supersession-q03", "text": "What may an agent decide or do once the validity of a claim about a Kamikaze is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 6, "layers": 12, "findings": 14, "questions": 38 } } } }