basilisk
Enable an agent to recognise a basilisk as a represented legendary creature, distinguish tradition-specific variants, and assess which descriptions and uses are supported.
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 agent to recognise a basilisk as a represented legendary creature, distinguish tradition-specific variants, and assess which descriptions and uses are supported.
A basilisk is a legendary creature of European tradition, generally represented as a serpent or reptilian hybrid whose gaze, breath, or venom can kill, with its appearance and powers varying across accounts.
It can be Disambiguate a basilisk mention before linking it to the registry entry.; Construct a source-qualified profile for a particular basilisk tradition or adaptation.; Compare depictions while preserving disagreements about anatomy and powers.; Check whether a proposed illustration or narrative matches a selected account.; Trace which accounts support an attributed power or countermeasure.; Flag unsupported combinations and unresolved creature identifications for review..
Distinguishing features
The referent is a legendary creature concept rather than a living animal, product or titled work sharing its name.
Identification is supported by a source naming or explicitly equating the creature with a basilisk; a dangerous serpent-like appearance alone is insufficient.
Claims about appearance and lethal effects are attached to a particular account rather than treated as universal identifying traits.
A cockatrice identification requires evidence of equivalence in the relevant tradition; visual resemblance alone does not establish identity.
A character or creature in an adaptation is linked to the wider concept only when naming, attribution or documented derivation supports that relationship.
Scope
+ The legendary creature sense of basilisk and evidence identifying that sense
+ Descriptions of its appearance, origin, powers and vulnerabilities within named traditions
+ Boundaries between basilisk variants and neighbouring creature concepts
+ Representations that transmit or reinterpret the basilisk concept
+ Attribution and uncertainty needed to use basilisk descriptions responsibly
- Living animals called basilisks and their biological classification
- Independent models of books, films, games or other works titled Basilisk
- Complete bibliographic descriptions of editions, files and physical copies
- General models of legendary creatures, serpents or monsters
- Real toxicology, animal handling and medical treatment
- Thought experiments or technical products that reuse the name
Characteristics
- Referent sense
- legendary creature concept | named fictional individual | titled work | biological namesake | other namesake | unresolved Prevents an agent from combining unrelated referents under one registry name.
- Attested designation
- Source passage or image label linked to its recorded name, language and translation Makes basilisk identification traceable instead of relying on resemblance.
- Tradition or adaptation context
- Named account, cultural tradition or fictional setting with supporting evidence Keeps incompatible descriptions meaningful within their own contexts.
- Depicted body form
- Source-described anatomy; controlled values established after research; unknown permitted Supports comparison without imposing one canonical appearance.
- Attributed harmful mechanism
- Source-specific account of trigger, transmission and effect; unstated or disputed permitted Distinguishes what an account claims the creature does from an agent's assumptions.
- Attributed countermeasure
- Claimed protection, vulnerability or defeat condition linked to its account Prevents one tradition's solution from being applied across every representation.
- Basilisk-cockatrice relationship
- explicit equivalence | explicit distinction | partial overlap | later identification | unresolved Records a consequential identity boundary without silently merging concepts.
- Description support
- directly attested | attributed through a secondary source | interpretive | disputed | unverified Determines whether an agent may assert, qualify or withhold a description.
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 · 13 findings · 21 questions.
Basilisk identity Establish which referent a basilisk mention identifies and where the creature concept ends.
The registry lacks a definition, so the name and domain alone cannot settle its intended sense.
Referent resolution
Separate the legendary creature from works, animals and other namesakes.
Creature sense evidence
Require contextual evidence before treating a basilisk mention as this legendary creature concept.
- Does the registry's originating record identify a legendary creature, a particular work or another namesake? definition
- Which passage, label or identifier supports linking this mention to the creature concept? provenance
Neighbouring creature boundaries
Record contextual distinctions and equivalences with cockatrices and other creatures.
Cockatrice equivalence
Treat basilisk-cockatrice equivalence as a claim requiring attribution, rather than a default synonym rule.
- Does the relevant account distinguish basilisk from cockatrice or explicitly equate them? boundary
- Is the equivalence present in the original account, a translation or a later interpretation? provenance
Embodied creature profile Describe the basilisk's represented body and origin within a specified account.
Recognition requires a contextual profile because the model must not assume one universal anatomy or origin story.
Anatomy and identification
Capture bodily features explicitly described or visibly represented.
Attested body features
Separate source-supported bodily features from additions made by illustrators, translators or adapters.
- What body form, limbs, head features and markings does this account actually describe or depict? definition
- Which features support basilisk identification, and which could equally belong to another creature? boundary
Origin and life history
Keep attributed birth conditions, development and habitat tied to their narrative context.
Origin account
Record an origin or habitat only when the selected account supplies one; absence is not a licence to import another version.
- What does this account state about how the basilisk comes into existence and where it lives? definition
- Which source supports each origin condition, and does it belong to the same variant as the recorded anatomy? provenance
Powers and encounter rules Represent what a basilisk is said to do and the conditions under which an encounter changes outcome.
An agent comparing stories or checking an adaptation needs explicit triggers and limits, rather than a generic label such as deadly monster.
Harmful effects
Distinguish attributed mechanisms, targets and outcomes.
Effect trigger and result
Model any claimed gaze, contact, breath or other effect only as specified by its account.
- What initiates the harmful effect, who or what is affected, and what outcome is explicitly stated? definition
- Does the account specify direction of looking, distance, delay or exceptions, or leave these conditions unstated? measurement
Resistance and defeat
Capture attributed protections and defeat conditions without assuming they work in every version.
Countermeasure conditions
Distinguish a countermeasure demonstrated in the narrative from advice, speculation or a rule introduced by an adaptation.
- Which protection or defeat method is stated, and what evidence within the account establishes its effectiveness? provenance
- Under the selected account's rules, may an agent use this countermeasure in a reconstruction, or must its effectiveness remain unresolved? action
Transmission and representation Track how accounts and adaptations transmit, alter or interpret the basilisk concept.
The informational creature concept must remain distinct from individual depictions and the works carrying them.
Accounts and derivation
Connect descriptions to identifiable accounts and document supported relationships between versions.
Claim-bearing account
Locate the passage or image carrying each basilisk claim while delegating full work and edition metadata to neighbouring models.
- Which identifiable passage or image supports this description, and which edition or translation was consulted? provenance
- Is a later depiction demonstrably derived from this account, or is the relationship only inferred from similarity? provenance
Interpretation and reuse
Keep symbolic readings and creative recombinations distinguishable from attributed creature descriptions.
Qualified representation
Support illustrations, summaries and adaptations that identify their chosen variant and disclose unsupported combinations.
- Is a proposed symbolic meaning stated by the source, supported by contextual scholarship or introduced by the interpreter? provenance
- Should the proposed depiction be labelled as following a particular account, combining variants or creating a new adaptation? 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 legendary-creature sense is assumed; no recorded sense establishes whether the registry instead intends a particular creative work.
- The INF.MED domain and batch classification warrant checking the original registry record before adopting this definition.
- Appearance, lethal powers, and the boundary with the cockatrice should be checked against individual historical sources.
- Which of these check these first hold for the sense of basilisk this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- Subject of literary, artistic, and heraldic representation.
- Creature adapted in fantasy fiction, games, and other entertainment.
- Which of these real-world use hold for the sense of basilisk 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.
- Accounts of lethal powers describe folklore, not documented biological hazards.
- The name can be confused with living basilisk lizards or with titled creative works.
- Which of these failure modes and hazards hold for the sense of basilisk this model covers, and on what evidence? provenance
Regional variation
Recalled without web access and unsourced; every item is a lead to verify.
- Classical Mediterranean accounts emphasize a deadly serpent; later European representations also include creatures with avian features.
- Which of these regional variation hold for the sense of basilisk 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.
- cockatrice - Usually depicted as a rooster-serpent hybrid; historical usage overlaps with basilisk, so the distinction depends on the source.
- basilisk lizard - A living lizard of the genus Basiliscus, rather than a legendary creature.
- Basilisk - A title used for creative works, including manga and anime; a specific work requires authorship or other identifying context.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of basilisk this model covers, and on what evidence? provenance
What the second pass must settle
- Does vr.tr.basilisk originate from a record for the legendary creature, or does INF.MED indicate a particular titled work?
- Does an existing Vercy world model already cover this creature concept and require this registry entry to link to it?
- Which directly inspected accounts should establish the initial set of basilisk variants and their historical relationships?
- Where do sources distinguish basilisk from cockatrice, and where do translations or adaptations equate them?
- Which appearance, power, origin and symbolic claims can be directly supported, and which widely repeated claims must remain unverified?