Kamikaze
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.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
recalled by Codex without web access - no source was read
Researched by: Codex
Purpose and description
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.
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.
It can be 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..
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.
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
- 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
Characteristics
- Referent type
- umbrella institutional practice | particular formation | personnel category | unresolved Determines whether the SOC.ORG placement describes the intended thing or conceals a classification mismatch.
- Attested designation
- original-language name linked to issuing body, dated document and translation Separates contemporary identification from later labels and translation choices.
- Command attachment
- parent service, command or formation, with effective dates and supporting evidence Establishes institutional boundaries without treating every Kamikaze-associated unit as one body.
- Personnel assignment basis
- documented volunteering | documented compulsory assignment | mixed or contested evidence | unknown Prevents assignment records from being treated as proof of freely given consent.
- Mission intention
- designated fatal-impact mission | conventional mission | improvised fatal action | disputed | unknown Distinguishes the intended special-attack role from outcomes reconstructed after a loss.
- Institutional lifecycle
- forming | training | operational | reorganised | ceased | unresolved, each time-qualified Supports historical state assessment without implying present operational existence.
- Attributed personnel strength
- persons, with date, formation boundary and inclusion rule Makes counts comparable while separating assigned personnel, trainees and mission participants.
- Evidence agreement
- corroborated | single-source | conflicting | unsupported Controls whether an agent may present an attribution as established or must preserve uncertainty.
Where this came from
wikidata · CC0 1.0
Drafted structure
Bundle to layer to finding to question, as the second pass will find it: 5 bundles · 9 layers · 14 findings · 22 questions.
Referent and designation Resolve what Kamikaze names in this registry and how that referent appears in historical records.
The entry lacks a definition, and its organisational placement cannot establish whether it denotes one formation or a broader practice.
Institutional sense
Test the provisional organisational interpretation against the originating registry evidence.
Referent resolution
Record whether the entry denotes a particular formation, an umbrella practice or a personnel category before making institutional identity claims.
- Which originating record or identifier establishes the intended sense of Kamikaze? provenance
- Does SOC.ORG describe the referent itself or only the military context associated with it? boundary
Historical naming
Track original designations, translations and retrospective terminology.
Designation equivalence
Treat equivalence between Kamikaze and other special-attack designations as a sourced, context-specific relationship.
- Which original-language designation appears in the relevant contemporary records, and who used it? provenance
- In this record, does Kamikaze identify a named unit, a wider category or a later descriptive label? definition
Formation and command Describe how the relevant special-attack formations were constituted, directed and changed.
Military command relationships and formation orders are more informative here than assuming independent corporate registration or legal personality.
Constituting authority
Identify evidence that establishes a formation and its special-attack role.
Formation mandate
Require dated evidence for formation identity, institutional authority and designation of its role.
- What order or other evidence establishes the formation and assigns its special-attack role? provenance
- Which command held authority over personnel assignment and mission authorisation during the period being described? definition
Continuity and cessation
Distinguish changes within a formation from replacement, reassignment or termination.
Dated organisational boundaries
Represent command transfers, name reuse and cessation without inferring continuity from a shared special-attack label.
- Which dated records distinguish reorganisation of this formation from creation of a different formation? boundary
- What evidence establishes when its special-attack role or institutional existence ceased? provenance
Personnel and assignment Represent participation in special-attack service without collapsing institutional assignment into individual intention.
Pilot identity, support membership, assignment and consent answer different questions and require different evidence.
Participation boundaries
Separate assigned pilots, trainees, supporting personnel and people recorded on particular missions.
Role-specific membership
Attribute people and personnel totals to a stated role, formation and date.
- Does the evidence establish assignment as a special-attack pilot, another formation role or participation in a particular mission? boundary
- Which roles and dates are included in a reported personnel total, and how are transfers or duplicate records handled? measurement
Consent and testimony
Assess what records can establish about volunteering, compulsion and personal accounts.
Assignment and consent evidence
Keep administrative assignment, public statements and personal testimony distinct when assessing an individual's circumstances.
- What evidence supports a claim of volunteering or compulsory assignment, and under what conditions was it produced? provenance
- How should an agent describe participation when administrative records and personal testimony conflict? action
Mission attribution and historical record Connect institutional roles to documented missions and assess subsequent claims without supplying operational guidance.
A formation's designation, a mission's intended character and its reported outcome must be evaluated separately.
Mission classification
Identify evidence of assigned mission intention independently of whether an aircraft or pilot returned.
Designated special attack
Classify a mission using evidence of its intended fatal-impact role; loss alone does not establish that classification.
- Which order, briefing record or corroborated account establishes the mission's intended special-attack character? provenance
- What distinguishes this mission from a conventional sortie that ended in an improvised fatal attack? boundary
Claims and retrospective attribution
Evaluate reported mission totals, losses and later descriptions against their evidence and counting rules.
Reconciled historical claims
Preserve distinctions among wartime reports, corroborated outcomes and commemorative accounts, including unresolved disagreements.
- Does a reported total count planned missions, departures, attempted impacts or corroborated outcomes? measurement
- When contemporary records and later commemorative accounts disagree, which claims can be retained and which require explicit uncertainty? action
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Check these first
Recalled without web access and unsourced; every item is a lead to verify.
- 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.
- Which of these check these first hold for the sense of Kamikaze this model covers, and on what evidence? provenance
Kinds and varieties
Recalled without web access and unsourced; every item is a lead to verify.
- Imperial Japanese Navy special-attack aviation units
- Imperial Japanese Army special-attack aviation units
- Which of these kinds and varieties hold for the sense of Kamikaze this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- 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.
- Which of these real-world use hold for the sense of Kamikaze this model covers, and on what evidence? provenance
Failure modes and hazards
Recalled without web access and unsourced; every item is a lead to verify.
- 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.
- Which of these failure modes and hazards hold for the sense of Kamikaze this model covers, and on what evidence? provenance
Regional variation
Recalled without web access and unsourced; every item is a lead to verify.
- 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.
- Which of these regional variation hold for the sense of Kamikaze this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Recalled without web access and unsourced; every item is a lead to verify.
- Tokkōtai - Special-attack units included aviation and other methods; kamikaze usually denotes the aviation subset in English.
- Kaiten - Kaiten were Japanese crewed suicide torpedoes, rather than aircraft or aviation units.
- Conventional aerial attack - 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.
- Loitering munition - A loitering munition is an uncrewed weapon sometimes informally called a kamikaze drone; it is not a historical Japanese airman or military unit.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of Kamikaze this model covers, and on what evidence? provenance
What the second pass must settle
- 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?