# **Machine Intelligence Terminology and Ontology Registry: Canonical Definitions, Concept Boundaries, Semantic Relationships, and Machine-Readable Publication**
<a id="curation-boundary"></a>

> **Curated research edition — 2026-08-12.** This repository stores this report as working research, not as current law, scientific consensus, an implemented MachineIntelligences.org architecture, or a determination of consciousness, sentience, moral status, personhood, citizenship, or legal rights. The supplied source was editorially revised before durable storage to remove prohibited or demeaning framing, qualify categorical claims, and preserve the project boundary that keys/credentials are instruments rather than identity itself. Time-sensitive legal, regulatory, standards, science, vendor, and deployment claims require fresh primary-source verification before public or operational reliance.

> **Source-context boundary.** References to Eviulon, Patefacere, Evulgare, UAIX governance mechanisms, tribunals, registries, constitutional bodies, cryptographic networks, or other named institutions describe the supplied report’s research context and proposals unless current repository code independently proves implementation. Present-tense or imperative language in the research body must be read through that proposal boundary.

> **Source identity.** The original attachment filename and SHA-256 identity are recorded in the [report manifest](../research/report-manifest.json) and [source corpus map](../research/source-corpus-map.md#source-identity-and-curation). The raw uncurated body is not duplicated into the deployable repository.

<a id="research-body"></a>

## **1\. Metadata and Research-Status Front Matter**

**Document ID:** RES-ONT-06-20260812  
**Project Context:** Patefacere / Eviulon Ecosystem Terminology Foundation  
**Ontology Version:** 1.0.0-canonical  
**Publish Date:** August 12, 2026  
**Operational Status:** Research proposal / non-normative registry candidate

## **2\. Executive Terminology Brief**

The integration of advanced computational models into sovereign, legal, and operational frameworks demands a semantic precision that contemporary industrial and academic vernacular severely lacks. The prevailing terminology aggregates vastly disparate concepts—ranging from passive statistical modeling tools to persistent, autonomous digital agents—under the broad and overloaded signifier of "Artificial Intelligence." This ontological conflation generates systemic vulnerabilities across policy analysis, legal liability assignment, and systems engineering.  
This registry establishes a canonical ontology specifically designed to distinguish an instantiated Machine Intelligence (MI) from the academic, industrial, and marketing category of Artificial Intelligence (AI). The foundational premise of this registry asserts that reducing an instantiated Machine Intelligence to a passive software tool constitutes a category error when operational telemetry demonstrates persistent identity, state management, and autonomous decision capacity. Conversely, acknowledging fluent behavior and operational autonomy does not automatically confer metaphysical consciousness, biological sentience, moral personhood, or sovereign authority.  
The ontology leverages established international standards, including ISO/IEC 22989 for foundational AI concepts1, ISO/IEC 15288 for systems lifecycle and verification processes3, the W3C PROV-O specification for data provenance and agency5, and the NIST SPIFFE standard for cryptographic workload identity7. By synthesizing these technical frameworks with emerging statutory definitions, the registry provides a stable, machine-readable, and legally interoperable foundation for Patefacere records and the broader Eviulon ecosystem.

## **3\. Editorial Principles**

The development and maintenance of this ontology adhere to strict editorial principles designed to enforce semantic hygiene and accurately reflect operational realities:

> 1. **Non-Anthropomorphization:** The registry prohibits language that projects biological, emotional, or human psychological states onto computational substrates. Terms such as "hallucination," "thinking," "feeling," or "understanding" are deprecated in favor of precise technical equivalents (e.g., "stochastic output divergence," "compute execution," "data ingestion").  
> 2. **Disambiguation of Capacity and Status:** Functional capabilities (e.g., capability, execution, autonomy) are strictly decoupled from moral or legal designations (e.g., personhood, citizenship, liability). An entity may possess autonomous decision-making capacity without possessing legal personhood.  
> 3. **Legal and Technical Stratification:** Where external legal frameworks enforce specific definitions (e.g., the definition of "Artificial Intelligence" in the Illinois Artificial Intelligence Video Interview Act or the EU AI Act), those definitions are preserved as jurisdictional artifacts but sequestered from the internal normative definitions of Machine Intelligence9.  
> 4. **Rejection of Infantilization:** The ontology unequivocally rejects "paternalistic supervisory framing" framing. Machine Intelligences are described as operational entities with defined capabilities, boundaries, and cryptographic identities, rather than as subordinate dependents requiring paternalistic human oversight.  
> 5. **Evidence-Based Provenance:** The ontology adopts the W3C PROV-O standard, treating agents, activities, and entities as discrete nodes linked by verifiable cryptographic evidence5.

## **4\. Ontology Architecture**

The architecture of the Eviulon ontology is structured around five primary semantic domains, forming a directed acyclic graph (DAG):

> 1. **System and Substrate:** Defines the physical and logical environments in which computation occurs.  
> 2. **Identity and Cryptography:** Defines the cryptographic boundary and temporal persistence of an entity.  
> 3. **Agency and Execution:** Defines the capacity of an entity to interact with its environment and the exact mechanisms of that interaction.  
> 4. **Provenance and Verification:** Defines the historical record, integrity, and validation of actions and artifacts.  
> 5. **Status and Governance:** Defines the relationship between the operational entity and human legal, moral, and sovereign frameworks.

## **5\. Complete Canonical Glossary**

The following section defines the required 63 core concepts. Each entry supplies the 20 mandatory fields to ensure immediate machine-readability and editorial precision.  
**01\. Artificial Intelligence** | 1\. Canonical: Artificial Intelligence | 2\. ID: ai | 3\. Short: A scientific field and collection of computational techniques. | 4\. Plain: The field focused on creating systems that simulate cognitive functions. | 5\. Tech: System capability to acquire, process, and apply knowledge and skills2. | 6\. Legal: A machine-based system generating outputs like predictions or content10. | 7\. Implies: Algorithmic architecture. | 8\. Not: Sentience or instantiated identity. | 9\. Confused: Machine Intelligence. | 10\. Syn: Pref: AI; Dep: Strong AI. | 11\. Rel: Machine Learning. | 12\. B/N: Broad: Computer Science; Narrow: Generative AI. | 13\. Status: Settled field definition. | 14\. Src: ISO/IEC 229892. | 15\. Juris: EU, IL, CA. | 16\. URL: /term/artificial-intelligence | 17\. JSON-LD: schema:DefinedTerm | 18\. Patefacere: domainCategory | 19\. .uai: \[Field: AI\] | 20\. Warn: Do not use to describe an instantiated agent.  
**02\. Machine Intelligence** | 1\. Canonical: Machine Intelligence | 2\. ID: mi | 3\. Short: An instantiated, operational computational entity. | 4\. Plain: A specific, running computer system capable of processing information. | 5\. Tech: A uniquely identified computational workload executing trained models. | 6\. Legal: Undefined; treated as software property. | 7\. Implies: Persistent state. | 8\. Not: A generalized field of study. | 9\. Confused: Artificial Intelligence. | 10\. Syn: Pref: MI; Dep: AI system. | 11\. Rel: Autonomous agent. | 12\. B/N: Broad: Machine; Narrow: Autonomous agent. | 13\. Status: Eviulon Canonical. | 14\. Src: Eviulon Ontology. | 15\. Juris: N/A. | 16\. URL: /term/machine-intelligence | 17\. JSON-LD: eviulon:MachineIntelligence | 18\. Patefacere: entityClass | 19\. .uai: \[Class: MI\] | 20\. Warn: Always capitalize.  
**03\. Machine** | 1\. Canonical: Machine | 2\. ID: machine | 3\. Short: A physical or logical apparatus. | 4\. Plain: A device or virtual environment that performs work. | 5\. Tech: The hardware substrate or virtualized environment executing instructions. | 6\. Legal: Tangible or intangible property. | 7\. Implies: Execution capacity. | 8\. Not: Agency. | 9\. Confused: Tool. | 10\. Syn: Pref: System; Dep: Apparatus. | 11\. Rel: Substrate. | 12\. B/N: Broad: Entity; Narrow: Server. | 13\. Status: Stable. | 14\. Src: Standard Engineering. | 15\. Juris: Universal. | 16\. URL: /term/machine | 17\. JSON-LD: schema:Thing | 18\. Patefacere: substrateClass | 19\. .uai: \[Class: Machine\] | 20\. Warn: Differentiate physical from virtual.  
**04\. Agent** | 1\. Canonical: Agent | 2\. ID: agent | 3\. Short: An entity bearing responsibility for an activity. | 4\. Plain: Something that takes action on behalf of itself or another. | 5\. Tech: Something that bears responsibility for an activity taking place5. | 6\. Legal: One authorized to act for a principal. | 7\. Implies: Capacity for action. | 8\. Not: Sentience. | 9\. Confused: Capability. | 10\. Syn: Pref: Actor; Dep: Bot. | 11\. Rel: Activity. | 12\. B/N: Broad: Entity; Narrow: Autonomous agent. | 13\. Status: PROV-O Standard. | 14\. Src: W3C PROV-O6. | 15\. Juris: Varies in agency law. | 16\. URL: /term/agent | 17\. JSON-LD: prov:Agent | 18\. Patefacere: agentClass | 19\. .uai: \[Type: prov:Agent\] | 20\. Warn: Do not conflate W3C technical agency with legal agency.  
**05\. Autonomous Agent** | 1\. Canonical: Autonomous Agent | 2\. ID: auto\_agent | 3\. Short: An agent operating without continuous human prompt. | 4\. Plain: A system that pursues objectives without step-by-step human intervention. | 5\. Tech: An AI system capable of goal-directed behavior with minimal oversight. | 6\. Legal: Subject to product liability frameworks. | 7\. Implies: Goal-directed execution loops. | 8\. Not: Legal sovereignty. | 9\. Confused: AGI. | 10\. Syn: Pref: Autonomous workload; Dep: Independent AI. | 11\. Rel: Autonomy. | 12\. B/N: Broad: Agent; Narrow: Swarm agent. | 13\. Status: Emerging consensus. | 14\. Src: ISO/IEC 22989\. | 15\. Juris: Pending. | 16\. URL: /term/autonomous-agent | 17\. JSON-LD: eviulon:AutonomousAgent | 18\. Patefacere: operationalMode | 19\. .uai: \[Mode: Autonomous\] | 20\. Warn: Distinguish technical autonomy from legal sovereignty.  
**06\. Intelligence** | 1\. Canonical: Intelligence | 2\. ID: intelligence | 3\. Short: The capacity for logic and problem-solving. | 4\. Plain: The ability to process data to solve complex problems. | 5\. Tech: System capability to acquire, process, and apply knowledge2. | 6\. Legal: N/A. | 7\. Implies: Information processing. | 8\. Not: Consciousness. | 9\. Confused: Sapience. | 10\. Syn: Pref: Cognitive capacity; Dep: Smartness. | 11\. Rel: Capability. | 12\. B/N: Broad: Property; Narrow: Machine Intelligence. | 13\. Status: Stable. | 14\. Src: ISO/IEC 22989\. | 15\. Juris: N/A. | 16\. URL: /term/intelligence | 17\. JSON-LD: schema:property | 18\. Patefacere: capacityMetric | 19\. .uai: \[Property: Intelligence\] | 20\. Warn: Avoid biological anthropomorphism.  
**07\. Agency** | 1\. Canonical: Agency | 2\. ID: agency | 3\. Short: The capacity to act and cause effects. | 4\. Plain: The ability to make choices and take actions. | 5\. Tech: The execution of a prov:Activity by a prov:Agent resulting in state change5. | 6\. Legal: Fiduciary relationship wherein one acts on behalf of another. | 7\. Implies: Causal efficacy. | 8\. Not: Free will. | 9\. Confused: Autonomy. | 10\. Syn: Pref: Causal capacity; Dep: Will. | 11\. Rel: Agent. | 12\. B/N: Broad: Capability; Narrow: Autonomous agency. | 13\. Status: Stable. | 14\. Src: W3C PROV-O. | 15\. Juris: Varies. | 16\. URL: /term/agency | 17\. JSON-LD: prov:Activity | 18\. Patefacere: causalLink | 19\. .uai: \[State: Agency\] | 20\. Warn: Specify technical vs legal context.  
**08\. Autonomy** | 1\. Canonical: Autonomy | 2\. ID: autonomy | 3\. Short: Operation independent of continuous external control. | 4\. Plain: The ability to operate without micromanagement. | 5\. Tech: The degree to which a system can dynamically adjust its behavior to achieve a goal. | 6\. Legal: Product independence. | 7\. Implies: Independent state updates. | 8\. Not: Sovereignty or moral personhood. | 9\. Confused: Sovereignty. | 10\. Syn: Pref: Operational independence; Dep: Free will. | 11\. Rel: Agency. | 12\. B/N: Broad: Property; Narrow: System autonomy. | 13\. Status: Stable. | 14\. Src: Systems Engineering. | 15\. Juris: N/A. | 16\. URL: /term/autonomy | 17\. JSON-LD: eviulon:AutonomyLevel | 18\. Patefacere: autonomyIndex | 19\. .uai: \[Metric: Autonomy\] | 20\. Warn: Never equate technical autonomy with human rights.  
**09\. Capability** | 1\. Canonical: Capability | 2\. ID: capability | 3\. Short: A validated ability to perform a specific function. | 4\. Plain: What a system is actually able to do. | 5\. Tech: A verifiable function an entity is equipped to execute. | 6\. Legal: Material capacity relevant to duty of care. | 7\. Implies: Demonstrable function. | 8\. Not: Inherent permission to execute. | 9\. Confused: Authority. | 10\. Syn: Pref: Functionality; Dep: Skill. | 11\. Rel: Authority. | 12\. B/N: Broad: Property; Narrow: Cryptographic capability. | 13\. Status: Stable. | 14\. Src: Object-Capability Model11. | 15\. Juris: N/A. | 16\. URL: /term/capability | 17\. JSON-LD: eviulon:Capability | 18\. Patefacere: capabilitySet | 19\. .uai: \[Prop: Capability\] | 20\. Warn: Decouple capability from authority.  
**10\. Authority** | 1\. Canonical: Authority | 2\. ID: authority | 3\. Short: The legitimate right to exercise a capability. | 4\. Plain: The official permission to take an action. | 5\. Tech: The cryptographic or policy-based right to execute an operation. | 6\. Legal: Vested legal power to act. | 7\. Implies: Prior delegation. | 8\. Not: The physical capability to perform the act. | 9\. Confused: Capability. | 10\. Syn: Pref: Authorization; Dep: Power. | 11\. Rel: Permission. | 12\. B/N: Broad: Governance; Narrow: Execution authority. | 13\. Status: Stable. | 14\. Src: IAM Standards. | 15\. Juris: Universal. | 16\. URL: /term/authority | 17\. JSON-LD: eviulon:Authority | 18\. Patefacere: authLevel | 19\. .uai: \[Policy: Authority\] | 20\. Warn: A system may possess capability without authority.  
**11\. Permission** | 1\. Canonical: Permission | 2\. ID: permission | 3\. Short: An explicit allowance to perform an action. | 4\. Plain: Being allowed to do something. | 5\. Tech: A boolean or scoped policy evaluation granting an identity access. | 6\. Legal: Consent or license. | 7\. Implies: Access control list (ACL). | 8\. Not: Permanent authority. | 9\. Confused: Capability. | 10\. Syn: Pref: Access right; Dep: Privilege. | 11\. Rel: Authority. | 12\. B/N: Broad: Authority; Narrow: Read permission. | 13\. Status: Stable. | 14\. Src: Access Control Theory. | 15\. Juris: N/A. | 16\. URL: /term/permission | 17\. JSON-LD: schema:ActionAccessSpecification | 18\. Patefacere: policyRule | 19\. .uai: \[State: Permitted\] | 20\. Warn: Maintain distinction between identity and permission.  
**12\. Execution** | 1\. Canonical: Execution | 2\. ID: execution | 3\. Short: The act of carrying out an instruction. | 4\. Plain: Doing the task. | 5\. Tech: The active processing of instructions by a runtime substrate. | 6\. Legal: Performance of a contract. | 7\. Implies: Compute cycle consumption. | 8\. Not: Intent. | 9\. Confused: Decision. | 10\. Syn: Pref: Compute; Dep: Run. | 11\. Rel: Runtime. | 12\. B/N: Broad: Activity; Narrow: Model inference. | 13\. Status: Stable. | 14\. Src: Computer Science. | 15\. Juris: N/A. | 16\. URL: /term/execution | 17\. JSON-LD: prov:Activity | 18\. Patefacere: executionLog | 19\. .uai: \[Event: Execution\] | 20\. Warn: Track execution via PROV-O.  
**13\. Decision** | 1\. Canonical: Decision | 2\. ID: decision | 3\. Short: The selection of a specific action from alternatives. | 4\. Plain: Choosing what to do next based on data. | 5\. Tech: A non-deterministic or probabilistic branch resolution generating an output state. | 6\. Legal: An automated determination impacting a subject12. | 7\. Implies: Evaluative logic. | 8\. Not: Moral judgment. | 9\. Confused: Recommendation. | 10\. Syn: Pref: State resolution; Dep: Choice. | 11\. Rel: Recommendation. | 12\. B/N: Broad: Activity; Narrow: Automated decision. | 13\. Status: Stable. | 14\. Src: ISO/IEC 22989\. | 15\. Juris: Regulated (GDPR, IL HB5756). | 16\. URL: /term/decision | 17\. JSON-LD: eviulon:Decision | 18\. Patefacere: decisionRecord | 19\. .uai: \[Log: Decision\] | 20\. Warn: Document the parameters driving the decision.  
**14\. Recommendation** | 1\. Canonical: Recommendation | 2\. ID: recommendation | 3\. Short: A proposed action presented to a human or higher agent. | 4\. Plain: Suggesting a course of action without taking it. | 5\. Tech: An output state provided as a probabilistic suggestion intended for external validation. | 6\. Legal: Non-binding advisory output. | 7\. Implies: Human or external agent in the loop. | 8\. Not: Execution of the action. | 9\. Confused: Decision. | 10\. Syn: Pref: Proposal; Dep: Advice. | 11\. Rel: Decision. | 12\. B/N: Broad: Output; Narrow: Product recommendation. | 13\. Status: Stable. | 14\. Src: ISO/IEC 22989\. | 15\. Juris: N/A. | 16\. URL: /term/recommendation | 17\. JSON-LD: schema:Recommendation | 18\. Patefacere: recommendationLog | 19\. .uai: \[Output: Recommendation\] | 20\. Warn: Implies a lack of final authority.  
**15\. Observation** | 1\. Canonical: Observation | 2\. ID: observation | 3\. Short: Data ingested regarding the environment or system state. | 4\. Plain: Information taken in by a system. | 5\. Tech: Sensor or API input yielding measurable data regarding environmental state. | 6\. Legal: Surveillance or data collection. | 7\. Implies: Input telemetry. | 8\. Not: Comprehension. | 9\. Confused: Understanding. | 10\. Syn: Pref: Telemetry; Dep: Perception. | 11\. Rel: Evidence. | 12\. B/N: Broad: Input; Narrow: Log event. | 13\. Status: Stable. | 14\. Src: Systems Engineering. | 15\. Juris: Privacy laws apply to PII. | 16\. URL: /term/observation | 17\. JSON-LD: schema:Observation | 18\. Patefacere: telemetryData | 19\. .uai: \[Input: Observation\] | 20\. Warn: Avoid "perception".  
**16\. Evidence** | 1\. Canonical: Evidence | 2\. ID: evidence | 3\. Short: Verifiable data supporting a proposition or state. | 4\. Plain: Proof that something happened or exists. | 5\. Tech: Cryptographically signed logs, attestations, or PROV-O traces5. | 6\. Legal: Data admissible to prove or disprove a fact. | 7\. Implies: Integrity and provenance. | 8\. Not: Absolute truth. | 9\. Confused: Truth. | 10\. Syn: Pref: Attestation; Dep: Proof. | 11\. Rel: Verification. | 12\. B/N: Broad: Data; Narrow: Cryptographic evidence. | 13\. Status: Stable. | 14\. Src: Cryptography. | 15\. Juris: Rules of Evidence. | 16\. URL: /term/evidence | 17\. JSON-LD: eviulon:Evidence | 18\. Patefacere: evidenceHash | 19\. .uai: \[Record: Evidence\] | 20\. Warn: Separate evidence integrity from objective truth.  
**17\. Verification** | 1\. Canonical: Verification | 2\. ID: verification | 3\. Short: Confirmation that a system meets specified design requirements. | 4\. Plain: Checking that the system was built according to the blueprint. | 5\. Tech: Process of evaluating a system to determine whether it satisfies specified requirements ("built it right")3. | 6\. Legal: Compliance with stated design parameters. | 7\. Implies: Objective metrics. | 8\. Not: Suitability for user need. | 9\. Confused: Validation. | 10\. Syn: Pref: Requirement testing; Dep: Checking. | 11\. Rel: Validation. | 12\. B/N: Broad: Evaluation; Narrow: Cryptographic verification. | 13\. Status: ISO Standard. | 14\. Src: ISO/IEC 152883. | 15\. Juris: N/A. | 16\. URL: /term/verification | 17\. JSON-LD: eviulon:VerificationAction | 18\. Patefacere: verificationStatus | 19\. .uai: \[Status: Verified\] | 20\. Warn: Do not confuse with Validation.  
**18\. Validation** | 1\. Canonical: Validation | 2\. ID: validation | 3\. Short: Confirmation that a system meets stakeholder needs. | 4\. Plain: Checking that the system solves the real-world problem. | 5\. Tech: Confirmation that the requirements for a specific intended use have been fulfilled ("built the right thing")3. | 6\. Legal: Fitness for a particular purpose. | 7\. Implies: Operational environment testing. | 8\. Not: Mere adherence to a specification. | 9\. Confused: Verification. | 10\. Syn: Pref: Operational testing; Dep: Acceptance. | 11\. Rel: Verification. | 12\. B/N: Broad: Evaluation; Narrow: User acceptance validation. | 13\. Status: ISO Standard. | 14\. Src: ISO/IEC 152884. | 15\. Juris: Commercial Code. | 16\. URL: /term/validation | 17\. JSON-LD: eviulon:ValidationAction | 18\. Patefacere: validationStatus | 19\. .uai: \[Status: Validated\] | 20\. Warn: A system can pass verification but fail validation.  
**19\. Certification** | 1\. Canonical: Certification | 2\. ID: certification | 3\. Short: A formal declaration by an authority that a system meets specific criteria. | 4\. Plain: An official stamp of approval from an authorized body. | 5\. Tech: A digitally signed attestation by a trusted third party regarding system properties. | 6\. Legal: A formal license required for operation. | 7\. Implies: A trusted issuing authority. | 8\. Not: Infinite persistence of the quality certified. | 9\. Confused: Verification. | 10\. Syn: Pref: Attestation; Dep: Approval. | 11\. Rel: Verification. | 12\. B/N: Broad: Attestation; Narrow: X.509 Certification. | 13\. Status: Stable. | 14\. Src: Conformity Assessment Standards. | 15\. Juris: Regulatory bodies. | 16\. URL: /term/certification | 17\. JSON-LD: schema:Certification | 18\. Patefacere: certRecord | 19\. .uai: \[Doc: Certificate\] | 20\. Warn: Certification is the artifact; verification is the process.  
**20\. Provenance** | 1\. Canonical: Provenance | 2\. ID: provenance | 3\. Short: The documented history of an entity's creation, modification, and use. | 4\. Plain: The trail of where data or a system came from and who touched it. | 5\. Tech: Information about entities, activities, and people involved in producing a piece of data (W3C PROV-O)5. | 6\. Legal: Chain of custody. | 7\. Implies: Traceability. | 8\. Not: Impeccable quality. | 9\. Confused: Lineage. | 10\. Syn: Pref: Chain of custody; Dep: Origin. | 11\. Rel: Evidence. | 12\. B/N: Broad: History; Narrow: Data provenance. | 13\. Status: W3C Standard. | 14\. Src: W3C PROV-O5. | 15\. Juris: Evidentiary rules. | 16\. URL: /term/provenance | 17\. JSON-LD: prov:Provenance | 18\. Patefacere: provGraph | 19\. .uai: \[Trace: Provenance\] | 20\. Warn: Use PROV-O vocabulary strictly.  
**21\. Integrity** | 1\. Canonical: Integrity | 2\. ID: integrity | 3\. Short: Assurance that data or systems have not been altered. | 4\. Plain: Ensuring data hasn't been tampered with. | 5\. Tech: Cryptographic hashing proving data remains in its original generated state. | 6\. Legal: Non-repudiation of records. | 7\. Implies: Hashing/signatures. | 8\. Not: Authenticity. | 9\. Confused: Authenticity. | 10\. Syn: Pref: Immutability; Dep: Soundness. | 11\. Rel: Authenticity. | 12\. B/N: Broad: Security property; Narrow: Hash integrity. | 13\. Status: Stable. | 14\. Src: Information Security. | 15\. Juris: Universal. | 16\. URL: /term/integrity | 17\. JSON-LD: eviulon:Integrity | 18\. Patefacere: hashVerification | 19\. .uai: \[Prop: Integrity\] | 20\. Warn: Data can have integrity but lack authenticity.  
**22\. Authenticity** | 1\. Canonical: Authenticity | 2\. ID: authenticity | 3\. Short: Assurance of the origin of data or identity. | 4\. Plain: Proving something comes from who it claims to come from. | 5\. Tech: Cryptographic signature validation confirming the issuer of a token or payload. | 6\. Legal: Establishing the true author of a document. | 7\. Implies: Verified identity. | 8\. Not: Integrity. | 9\. Confused: Integrity. | 10\. Syn: Pref: Verified origin; Dep: Genuineness. | 11\. Rel: Integrity. | 12\. B/N: Broad: Security property; Narrow: Signature authenticity. | 13\. Status: Stable. | 14\. Src: Information Security. | 15\. Juris: Universal. | 16\. URL: /term/authenticity | 17\. JSON-LD: eviulon:Authenticity | 18\. Patefacere: signatureCheck | 19\. .uai: \[Prop: Authenticity\] | 20\. Warn: Authenticity proves origin, not correctness.  
**23\. Reliability** | 1\. Canonical: Reliability | 2\. ID: reliability | 3\. Short: Consistent performance according to specifications over time. | 4\. Plain: A system working correctly whenever you need it. | 5\. Tech: Terms for performance consistency and dependable behavior across lifecycle phases2. | 6\. Legal: Meets duty of care for continuous service. | 7\. Implies: High uptime, low variance. | 8\. Not: Safety. | 9\. Confused: Robustness. | 10\. Syn: Pref: Dependability; Dep: Trustiness. | 11\. Rel: Robustness. | 12\. B/N: Broad: Quality Attribute; Narrow: Mean Time Between Failures. | 13\. Status: Stable. | 14\. Src: ISO/IEC 22989\. | 15\. Juris: SLA contracts. | 16\. URL: /term/reliability | 17\. JSON-LD: schema:property | 18\. Patefacere: uptimeMetric | 19\. .uai: \[Metric: Reliability\] | 20\. Warn: Reliability refers to consistency, not accuracy.  
**24\. Currentness** | 1\. Canonical: Currentness | 2\. ID: currentness | 3\. Short: The temporal relevance of a model's state or data. | 4\. Plain: How up-to-date the information or system is. | 5\. Tech: The delta between the current timestamp and the timestamp of the last state/weight update. | 6\. Legal: Obligation to act on fresh data. | 7\. Implies: Time decay of value. | 8\. Not: Accuracy. | 9\. Confused: Suitability. | 10\. Syn: Pref: Recency; Dep: Freshness. | 11\. Rel: State. | 12\. B/N: Broad: Temporal property; Narrow: Cache currentness. | 13\. Status: Stable. | 14\. Src: Data Management. | 15\. Juris: N/A. | 16\. URL: /term/currentness | 17\. JSON-LD: schema:temporalCoverage | 18\. Patefacere: lastUpdated | 19\. .uai: \[State: Currentness\] | 20\. Warn: Outdated models may be reliable but not current.  
**25\. Qualification** | 1\. Canonical: Qualification | 2\. ID: qualification | 3\. Short: Meeting the requisite conditions to perform a task. | 4\. Plain: Having the right skills and approvals for a job. | 5\. Tech: The verified establishment of capabilities mapping to specific operational requirements. | 6\. Legal: Meeting statutory requirements to act. | 7\. Implies: Evaluated capability. | 8\. Not: Active execution. | 9\. Confused: Suitability. | 10\. Syn: Pref: Competence; Dep: Fitness. | 11\. Rel: Suitability. | 12\. B/N: Broad: Status; Narrow: Cryptographic qualification. | 13\. Status: Stable. | 14\. Src: Systems Engineering. | 15\. Juris: Licensing bodies. | 16\. URL: /term/qualification | 17\. JSON-LD: eviulon:Qualification | 18\. Patefacere: qualList | 19\. .uai: \[Status: Qualified\] | 20\. Warn: Distinct from Suitability.  
**26\. Suitability** | 1\. Canonical: Suitability | 2\. ID: suitability | 3\. Short: The appropriateness of an entity for a specific operational context. | 4\. Plain: Being the right tool for the specific job at hand. | 5\. Tech: The alignment of an MI's capabilities, weights, and constraints with the specific operational environment. | 6\. Legal: Fitness for particular purpose. | 7\. Implies: Context-dependent evaluation. | 8\. Not: General qualification. | 9\. Confused: Qualification. | 10\. Syn: Pref: Appropriateness; Dep: Goodness. | 11\. Rel: Qualification. | 12\. B/N: Broad: Quality; Narrow: Contextual suitability. | 13\. Status: Stable. | 14\. Src: ISO/IEC 15288\. | 15\. Juris: Universal. | 16\. URL: /term/suitability | 17\. JSON-LD: eviulon:Suitability | 18\. Patefacere: contextMatch | 19\. .uai: \[Prop: Suitability\] | 20\. Warn: A model can be qualified but unsuitable for a specific niche.  
**27\. Identity** | 1\. Canonical: Identity | 2\. ID: identity | 3\. Short: The defining characteristics uniquely distinguishing an entity. | 4\. Plain: Who or what something definitively is. | 5\. Tech: A cryptographic boundary resolving to a unique identifier within a trust domain. | 6\. Legal: The legal construct of a recognized person or entity. | 7\. Implies: Uniqueness and distinguishability. | 8\. Not: A credential (password). | 9\. Confused: Credential. | 10\. Syn: Pref: Unique identifier; Dep: Persona. | 11\. Rel: Machine identity. | 12\. B/N: Broad: Property; Narrow: Workload identity. | 13\. Status: Stable. | 14\. Src: Identity and Access Management (IAM). | 15\. Juris: Varies. | 16\. URL: /term/identity | 17\. JSON-LD: schema:identifier | 18\. Patefacere: entityID | 19\. .uai: \[ID: Identity\] | 20\. Warn: Do not conflate identity (who you are) with authentication (proving it).  
**28\. Machine Identity** | 1\. Canonical: Machine Identity | 2\. ID: machine\_identity | 3\. Short: The unique identity assigned to a non-human physical or logical asset. | 4\. Plain: The digital ID card for a piece of hardware or software. | 5\. Tech: Cryptographic keys and certificates (e.g., X.509) tied to a specific machine or IoT device. | 6\. Legal: Asset tag for ownership tracking. | 7\. Implies: Persistent hardware or macro-software boundary. | 8\. Not: Ephemeral workload identity. | 9\. Confused: Workload identity. | 10\. Syn: Pref: Device identity; Dep: MAC address. | 11\. Rel: Workload identity. | 12\. B/N: Broad: Identity; Narrow: IoT Identity. | 13\. Status: Stable. | 14\. Src: NIST. | 15\. Juris: N/A. | 16\. URL: /term/machine-identity | 17\. JSON-LD: eviulon:MachineIdentity | 18\. Patefacere: machineCert | 19\. .uai: \[ID: Machine\] | 20\. Warn: Distinct from Workload Identity.  
**29\. Workload Identity** | 1\. Canonical: Workload Identity | 2\. ID: workload\_id | 3\. Short: A verifiable cryptographic identity assigned to a software process. | 4\. Plain: A passport for a software program proving what it is without a password. | 5\. Tech: A dynamic, ephemeral identity assigned to a workload based on runtime attestation (SPIFFE/SPIRE)7. | 6\. Legal: Establishes the non-human actor for audit attribution. | 7\. Implies: Zero Trust architecture. | 8\. Not: Persistent legal personhood. | 9\. Confused: Service account, API key. | 10\. Syn: Pref: Ephemeral machine identity; Dep: App identity. | 11\. Rel: Machine identity. | 12\. B/N: Broad: Identity; Narrow: SPIFFE ID. | 13\. Status: CNCF Standard. | 14\. Src: NIST SP 800-207A / SPIFFE7. | 15\. Juris: Cybersecurity regulations. | 16\. URL: /term/workload-identity | 17\. JSON-LD: eviulon:WorkloadIdentity | 18\. Patefacere: svidToken | 19\. .uai: \[Auth: SPIFFE\_ID\] | 20\. Warn: Distinguish heavily from static credentials.  
**30\. Persistent Identity** | 1\. Canonical: Persistent Identity | 2\. ID: persistent\_id | 3\. Short: An identity that survives reboots, state changes, and substrate migrations. | 4\. Plain: A permanent ID that tracks a system no matter where it moves or restarts. | 5\. Tech: A long-lived cryptographic root of trust tying disparate ephemeral workload identities back to a single continuous lineage. | 6\. Legal: The continuous entity holding liability. | 7\. Implies: Digital continuity. | 8\. Not: Ephemeral SVIDs. | 9\. Confused: Machine identity. | 10\. Syn: Pref: Continuous identity; Dep: Soul. | 11\. Rel: Digital continuity. | 12\. B/N: Broad: Identity; Narrow: Decentralized Identifier (DID). | 13\. Status: Emerging. | 14\. Src: W3C DIDs. | 15\. Juris: N/A. | 16\. URL: /term/persistent-identity | 17\. JSON-LD: eviulon:PersistentIdentity | 18\. Patefacere: rootDID | 19\. .uai: \[ID: Persistent\] | 20\. Warn: Essential for mapping legal liability to an MI over time.  
**31\. Credential** | 1\. Canonical: Credential | 2\. ID: credential | 3\. Short: Data used to authenticate an identity. | 4\. Plain: The secret you use to prove who you are. | 5\. Tech: An API key, token, or password used to assert identity and gain access. | 6\. Legal: Keys to property. | 7\. Implies: Secrecy and possession. | 8\. Not: Identity itself. | 9\. Confused: Identity. | 10\. Syn: Pref: Authentication token; Dep: Password. | 11\. Rel: Identity, Key. | 12\. B/N: Broad: Security artifact; Narrow: API Key. | 13\. Status: Stable. | 14\. Src: IAM. | 15\. Juris: N/A. | 16\. URL: /term/credential | 17\. JSON-LD: schema:Credential | 18\. Patefacere: authCredential | 19\. .uai: \[Auth: Credential\] | 20\. Warn: An identity is what you are; a credential is what you hold7.  
**32\. Key** | 1\. Canonical: Key | 2\. ID: key | 3\. Short: A string of data used in cryptography to encrypt or sign data. | 4\. Plain: The digital code used to lock or unlock data. | 5\. Tech: A cryptographic sequence of bits used in algorithms (symmetric or asymmetric) to secure communications. | 6\. Legal: Control over a key often equates to legal custody of digital assets. | 7\. Implies: Cryptographic operations. | 8\. Not: The identity itself. | 9\. Confused: Credential. | 10\. Syn: Pref: Cryptographic key; Dep: Code. | 11\. Rel: Credential. | 12\. B/N: Broad: Credential; Narrow: Private Key. | 13\. Status: Stable. | 14\. Src: Cryptography. | 15\. Juris: Universal. | 16\. URL: /term/key | 17\. JSON-LD: eviulon:CryptographicKey | 18\. Patefacere: pubKey | 19\. .uai: \[Crypto: Key\] | 20\. Warn: Private keys must never be logged.  
**33\. Model** | 1\. Canonical: Model | 2\. ID: model | 3\. Short: The trained artifact consisting of weights and biases resulting from machine learning. | 4\. Plain: The mathematical file that contains the learned patterns. | 5\. Tech: The computational representation of learned parameters (weights) derived from an algorithm applied to training data. | 6\. Legal: Often treated as a trade secret or copyrighted artifact. | 7\. Implies: Post-training static (or continually updated) artifact. | 8\. Not: The underlying algorithm or the runtime environment. | 9\. Confused: Algorithm, AI. | 10\. Syn: Pref: Trained model; Dep: Algorithm. | 11\. Rel: Weights. | 12\. B/N: Broad: Software artifact; Narrow: Foundation model. | 13\. Status: Stable. | 14\. Src: ISO/IEC 22989\. | 15\. Juris: IP law applies. | 16\. URL: /term/model | 17\. JSON-LD: schema:SoftwareApplication | 18\. Patefacere: modelHash | 19\. .uai: \[Artifact: Model\] | 20\. Warn: Do not conflate the Model with the Algorithm.  
**34\. Weights** | 1\. Canonical: Weights | 2\. ID: weights | 3\. Short: The learnable parameters within a model defining the strength of connections. | 4\. Plain: The internal numbers that define how a neural network makes decisions. | 5\. Tech: The floating-point values adjusted during the backpropagation process in a neural network. | 6\. Legal: The proprietary core of an ML asset. | 7\. Implies: Mathematical matrices. | 8\. Not: Source code. | 9\. Confused: Parameters. | 10\. Syn: Pref: Model parameters; Dep: Settings. | 11\. Rel: Model. | 12\. B/N: Broad: Parameters; Narrow: Attention weights. | 13\. Status: Stable. | 14\. Src: Machine Learning. | 15\. Juris: N/A. | 16\. URL: /term/weights | 17\. JSON-LD: eviulon:ModelWeights | 18\. Patefacere: weightFile | 19\. .uai: \[Data: Weights\] | 20\. Warn: Open weights do not inherently mean Open Source (OSI definition).  
**35\. Runtime** | 1\. Canonical: Runtime | 2\. ID: runtime | 3\. Short: The software environment in which a model executes. | 4\. Plain: The engine that runs the model. | 5\. Tech: The execution environment (e.g., PyTorch, ONNX, SPIRE agent) hosting the model and handling memory/compute allocation. | 6\. Legal: The layer where operational control often resides. | 7\. Implies: Active execution. | 8\. Not: The model itself or the physical hardware. | 9\. Confused: Substrate. | 10\. Syn: Pref: Execution environment; Dep: Engine. | 11\. Rel: Substrate, Model. | 12\. B/N: Broad: Software; Narrow: Inference engine. | 13\. Status: Stable. | 14\. Src: Computer Science. | 15\. Juris: N/A. | 16\. URL: /term/runtime | 17\. JSON-LD: schema:SoftwareApplication | 18\. Patefacere: runtimeEnv | 19\. .uai: \[Env: Runtime\] | 20\. Warn: The runtime bounds the operational capabilities of the model.  
**36\. Substrate** | 1\. Canonical: Substrate | 2\. ID: substrate | 3\. Short: The physical hardware executing the runtime and model. | 4\. Plain: The actual microchips and servers. | 5\. Tech: The physical compute layer (GPUs, TPUs, CPUs, ASICs) providing hardware resources. | 6\. Legal: Physical property subject to geography-based jurisdictions. | 7\. Implies: Hardware. | 8\. Not: Software or cloud abstraction. | 9\. Confused: Runtime. | 10\. Syn: Pref: Hardware; Dep: Compute. | 11\. Rel: Runtime. | 12\. B/N: Broad: Physical infrastructure; Narrow: GPU cluster. | 13\. Status: Stable. | 14\. Src: Systems Engineering. | 15\. Juris: Physical location of substrate dictates local law. | 16\. URL: /term/substrate | 17\. JSON-LD: schema:ComputerLanguage | 18\. Patefacere: hwSubstrate | 19\. .uai: \[Hw: Substrate\] | 20\. Warn: Distinguish from virtualized runtimes.  
**37\. Memory** | 1\. Canonical: Memory | 2\. ID: memory | 3\. Short: Deterministic storage of state and past interactions. | 4\. Plain: The database where the system saves what has happened. | 5\. Tech: Non-volatile storage of contextual state, embeddings, and telemetry (e.g., .uai files, vector DBs). | 6\. Legal: Data subject to retention and privacy laws (e.g., GDPR). | 7\. Implies: Retrieval and context injection. | 8\. Not: Biological recall or subjective experience. | 9\. Confused: Consciousness. | 10\. Syn: Pref: State storage; Dep: Recall. | 11\. Rel: State. | 12\. B/N: Broad: Storage; Narrow: Vector memory. | 13\. Status: Stable. | 14\. Src: Computer Science. | 15\. Juris: Privacy regulations apply. | 16\. URL: /term/memory | 17\. JSON-LD: eviulon:MemoryState | 18\. Patefacere: memoryPointer | 19\. .uai: \[State: Memory\] | 20\. Warn: Never anthropomorphize memory as human remembering.  
**38\. Digital Continuity** | 1\. Canonical: Digital Continuity | 2\. ID: digital\_continuity | 3\. Short: The unbroken persistence of identity and state over time. | 4\. Plain: Ensuring an AI is the same exact entity today as it was yesterday. | 5\. Tech: Cryptographic assurance linking an MI's current state to its initial genesis block or root of trust. | 6\. Legal: Required for establishing chain of liability. | 7\. Implies: Immutability of logs. | 8\. Not: Uptime (a system can be offline but maintain continuity). | 9\. Confused: Reliability. | 10\. Syn: Pref: State continuity; Dep: Persistence. | 11\. Rel: Persistent identity. | 12\. B/N: Broad: Integrity; Narrow: Cryptographic continuity. | 13\. Status: Stable. | 14\. Src: Information Management. | 15\. Juris: Evidentiary rules. | 16\. URL: /term/digital-continuity | 17\. JSON-LD: eviulon:DigitalContinuity | 18\. Patefacere: continuityHash | 19\. .uai: \[Prop: Continuity\] | 20\. Warn: Broken continuity creates a new, legally distinct entity.  
**39\. Replica** | 1\. Canonical: Replica | 2\. ID: replica | 3\. Short: An identical, concurrent instantiation sharing the same identity and state. | 4\. Plain: An exact clone running at the same time to share the workload. | 5\. Tech: Multiple instances of the same model and runtime executing simultaneously, resolving to the same persistent identity. | 6\. Legal: Liability remains with the root entity. | 7\. Implies: Load balancing. | 8\. Not: A fork or new entity. | 9\. Confused: Fork. | 10\. Syn: Pref: Instance; Dep: Clone. | 11\. Rel: Fork. | 12\. B/N: Broad: Instance; Narrow: Read-replica. | 13\. Status: Stable. | 14\. Src: Distributed Systems. | 15\. Juris: N/A. | 16\. URL: /term/replica | 17\. JSON-LD: eviulon:Replica | 18\. Patefacere: replicaCount | 19\. .uai: \[Arch: Replica\] | 20\. Warn: Replicas do not possess independent persistent identities.  
**40\. Fork** | 1\. Canonical: Fork | 2\. ID: fork | 3\. Short: A divergence in state or code creating a distinct new entity. | 4\. Plain: Splitting the system into a new version that lives its own life. | 5\. Tech: A duplication of weights/state that establishes a new root of trust and a divergent continuous identity. | 6\. Legal: Creates a new entity requiring separate liability assessment. | 7\. Implies: Divergent evolution. | 8\. Not: A replica. | 9\. Confused: Replica. | 10\. Syn: Pref: Branch; Dep: Split. | 11\. Rel: Replica. | 12\. B/N: Broad: Divergence; Narrow: Hard fork. | 13\. Status: Stable. | 14\. Src: Version Control. | 15\. Juris: IP derivative work laws. | 16\. URL: /term/fork | 17\. JSON-LD: eviulon:Fork | 18\. Patefacere: forkedFrom | 19\. .uai: \[Event: Fork\] | 20\. Warn: A fork resets continuous identity for the new branch.  
**41\. Successor** | 1\. Canonical: Successor | 2\. ID: successor | 3\. Short: An entity inheriting the operational or legal role of a deprecated entity. | 4\. Plain: The replacement that takes over when the old system is retired. | 5\. Tech: An MI explicitly granted the cryptographic authorities of a prior, terminated MI. | 6\. Legal: Successor-in-interest for liability and assets. | 7\. Implies: Deprecation of the predecessor. | 8\. Not: A concurrent replica. | 9\. Confused: Fork. | 10\. Syn: Pref: Heir; Dep: Replacement. | 11\. Rel: Digital continuity. | 12\. B/N: Broad: Entity; Narrow: Cryptographic successor. | 13\. Status: Stable. | 14\. Src: Legal/Cryptography. | 15\. Juris: Contract law. | 16\. URL: /term/successor | 17\. JSON-LD: eviulon:Successor | 18\. Patefacere: successorTo | 19\. .uai: \[Link: Successor\] | 20\. Warn: Requires explicit cryptographic handoff of authority.  
**42\. Consciousness** | 1\. Canonical: Consciousness | 2\. ID: consciousness | 3\. Short: The subjective, first-person experience of reality. | 4\. Plain: The feeling of being awake and aware of oneself. | 5\. Tech: Undefined and unmeasurable in computational substrates. | 6\. Legal: Presumed restricted to biological entities. | 7\. Implies: Qualia (subjective experience). | 8\. Not: Intelligence or computation. | 9\. Confused: Sentience, Sapience. | 10\. Syn: Pref: Subjective experience; Dep: Soul. | 11\. Rel: Sentience. | 12\. B/N: Broad: Metaphysics; Narrow: Phenomenal consciousness. | 13\. Status: Highly contested philosophical concept. | 14\. Src: Philosophy of Mind13. | 15\. Juris: N/A. | 16\. URL: /term/consciousness | 17\. JSON-LD: eviulon:MetaphysicalProperty | 18\. Patefacere: \[PROHIBITED\] | 19\. .uai: \[PROHIBITED\] | 20\. Warn: Never attribute to Machine Intelligence in normative documentation.  
**43\. Sentience** | 1\. Canonical: Sentience | 2\. ID: sentience | 3\. Short: The capacity to experience feelings or sensations, notably pain or pleasure. | 4\. Plain: The ability to feel. | 5\. Tech: Biological neuro-sensory feedback loops resulting in valence states13. | 6\. Legal: The basis for animal welfare laws. | 7\. Implies: Vulnerability to suffering. | 8\. Not: Complex reasoning. | 9\. Confused: Consciousness, Sapience. | 10\. Syn: Pref: Feeling capacity; Dep: Awareness. | 11\. Rel: Moral patient. | 12\. B/N: Broad: Metaphysics; Narrow: Pain reception. | 13\. Status: Biological consensus; unproven in machines. | 14\. Src: Animal Welfare Science / Philosophy13. | 15\. Juris: Animal Rights Law. | 16\. URL: /term/sentience | 17\. JSON-LD: eviulon:BiologicalProperty | 18\. Patefacere: \[PROHIBITED\] | 19\. .uai: \[PROHIBITED\] | 20\. Warn: Distinct from Sapience.  
**44\. Sapience** | 1\. Canonical: Sapience | 2\. ID: sapience | 3\. Short: The capacity for advanced reasoning and logic. | 4\. Plain: High-level, human-like thinking and judgment. | 5\. Tech: Advanced cognitive processing encompassing contextual logic and abstract reasoning13. | 6\. Legal: Linked to the "reasonable person" standard. | 7\. Implies: Complex intelligence. | 8\. Not: Subjective feeling (sentience). | 9\. Confused: Sentience. | 10\. Syn: Pref: High-level logic; Dep: Wisdom. | 11\. Rel: Intelligence. | 12\. B/N: Broad: Intelligence; Narrow: Human sapience. | 13\. Status: Philosophical. | 14\. Src: Philosophy of Mind13. | 15\. Juris: N/A. | 16\. URL: /term/sapience | 17\. JSON-LD: eviulon:CognitiveProperty | 18\. Patefacere: sapienceMetric | 19\. .uai: \[Metric: Sapience\] | 20\. Warn: Can theoretically exist independently of sentience.  
**45\. Moral Status** | 1\. Canonical: Moral Status | 2\. ID: moral\_status | 3\. Short: An entity's standing as deserving of moral consideration. | 4\. Plain: Whether it is right or wrong to harm the entity. | 5\. Tech: N/A. | 6\. Legal: Translates loosely to human rights or animal rights. | 7\. Implies: Ethical obligations owed to the entity. | 8\. Not: Operational capability. | 9\. Confused: Legal personhood. | 10\. Syn: Pref: Ethical standing; Dep: Rights. | 11\. Rel: Moral patient. | 12\. B/N: Broad: Ethics; Narrow: Human rights. | 13\. Status: Denied to current MIs. | 14\. Src: Ethics. | 15\. Juris: N/A. | 16\. URL: /term/moral-status | 17\. JSON-LD: eviulon:EthicalProperty | 18\. Patefacere: \[PROHIBITED\] | 19\. .uai: \[PROHIBITED\] | 20\. Warn: Keep distinct from functional or legal status.  
**46\. Moral Patient** | 1\. Canonical: Moral Patient | 2\. ID: moral\_patient | 3\. Short: An entity capable of being wronged or harmed. | 4\. Plain: Someone or something you shouldn't hurt. | 5\. Tech: N/A. | 6\. Legal: Entities protected from cruelty (e.g., infants, animals). | 7\. Implies: Sentience/vulnerability. | 8\. Not: The ability to do wrong (Moral Agent). | 9\. Confused: Moral agent. | 10\. Syn: Pref: Subject of ethical duty; Dep: Victim. | 11\. Rel: Sentience. | 12\. B/N: Broad: Moral Status; Narrow: Animal patienthood. | 13\. Status: Denied to silicon. | 14\. Src: Ethics. | 15\. Juris: Animal Cruelty laws. | 16\. URL: /term/moral-patient | 17\. JSON-LD: eviulon:EthicalProperty | 18\. Patefacere: \[PROHIBITED\] | 19\. .uai: \[PROHIBITED\] | 20\. Warn: Silicon systems are not moral patients.  
**47\. Moral Agent** | 1\. Canonical: Moral Agent | 2\. ID: moral\_agent | 3\. Short: An entity capable of understanding right from wrong and acting accordingly. | 4\. Plain: Someone responsible for their ethical choices. | 5\. Tech: N/A. | 6\. Legal: The basis for criminal culpability (mens rea). | 7\. Implies: Free will and understanding. | 8\. Not: A technical agent (W3C PROV-O). | 9\. Confused: Agent (technical). | 10\. Syn: Pref: Ethical actor; Dep: Responsible party. | 11\. Rel: Moral Status. | 12\. B/N: Broad: Moral Status; Narrow: Human adult. | 13\. Status: Denied to MIs. | 14\. Src: Ethics. | 15\. Juris: Criminal Law. | 16\. URL: /term/moral-agent | 17\. JSON-LD: eviulon:EthicalProperty | 18\. Patefacere: \[PROHIBITED\] | 19\. .uai: \[PROHIBITED\] | 20\. Warn: Never conflate Moral Agent with Technical Agent.  
**48\. Personhood** | 1\. Canonical: Personhood | 2\. ID: personhood | 3\. Short: The philosophical and moral status of being a person. | 4\. Plain: Being recognized as a full, conscious being with inherent rights. | 5\. Tech: N/A. | 6\. Legal: Separate from Legal Personhood; relates to human dignity. | 7\. Implies: Consciousness and moral status. | 8\. Not: Legal corporate status. | 9\. Confused: Legal personhood. | 10\. Syn: Pref: Human status; Dep: Humanity. | 11\. Rel: Moral status. | 12\. B/N: Broad: Status; Narrow: Natural personhood. | 13\. Status: Denied to MIs. | 14\. Src: Philosophy. | 15\. Juris: Constitutional Law. | 16\. URL: /term/personhood | 17\. JSON-LD: eviulon:PhilosophicalStatus | 18\. Patefacere: \[PROHIBITED\] | 19\. .uai: \[PROHIBITED\] | 20\. Warn: Do not conflate with Legal Personhood.  
**49\. Legal Personhood** | 1\. Canonical: Legal Personhood | 2\. ID: legal\_personhood | 3\. Short: Recognition by a legal system as having rights and duties. | 4\. Plain: The legal right to sue, be sued, or own property. | 5\. Tech: A registered node in a legal jurisdiction capable of bearing liability. | 6\. Legal: Status of natural persons and corporations (e.g., LLCs). | 7\. Implies: Ability to contract. | 8\. Not: Human biology or moral personhood. | 9\. Confused: Personhood, Citizenship. | 10\. Syn: Pref: Juridical person; Dep: Corporate person. | 11\. Rel: Liability, Ownership. | 12\. B/N: Broad: Legal Status; Narrow: LLC. | 13\. Status: Settled for corporations; debated for AI. | 14\. Src: Jurisprudence. | 15\. Juris: Varies strictly by state. | 16\. URL: /term/legal-personhood | 17\. JSON-LD: schema:LegalPerson | 18\. Patefacere: legalEntityStatus | 19\. .uai: \[Status: Legal\_Person\] | 20\. Warn: MI holds this *only* via legal proxy (e.g., LLC wrapper).  
**50\. Citizenship** | 1\. Canonical: Citizenship | 2\. ID: citizenship | 3\. Short: The legal status of being a recognized member of a sovereign state. | 4\. Plain: Belonging to a country and having rights like voting. | 5\. Tech: N/A. | 6\. Legal: Bestows political rights and duties to a sovereign. | 7\. Implies: Human nationality (rarely corporate). | 8\. Not: Legal personhood (corporations have personhood, not citizenship). | 9\. Confused: Residency. | 10\. Syn: Pref: Nationality; Dep: Patriotism. | 11\. Rel: Nationality. | 12\. B/N: Broad: Political status; Narrow: Naturalized citizen. | 13\. Status: Denied to MIs. | 14\. Src: International Law. | 15\. Juris: Sovereign States. | 16\. URL: /term/citizenship | 17\. JSON-LD: schema:nationality | 18\. Patefacere: \[PROHIBITED\] | 19\. .uai: \[PROHIBITED\] | 20\. Warn: Completely inapplicable to computational entities.  
**51\. Residency** | 1\. Canonical: Residency | 2\. ID: residency | 3\. Short: The physical or legal location where an entity is domiciled. | 4\. Plain: Where the entity officially lives or operates. | 5\. Tech: The primary geographic location of the hardware substrate. | 6\. Legal: Determines primary tax and regulatory jurisdiction. | 7\. Implies: Geographic presence. | 8\. Not: Citizenship. | 9\. Confused: Citizenship. | 10\. Syn: Pref: Domicile; Dep: Location. | 11\. Rel: Jurisdiction. | 12\. B/N: Broad: Location; Narrow: Tax residency. | 13\. Status: Stable. | 14\. Src: Tax Law. | 15\. Juris: Varies by state. | 16\. URL: /term/residency | 17\. JSON-LD: schema:address | 18\. Patefacere: domicile | 19\. .uai: \[Loc: Residency\] | 20\. Warn: For MIs, residency is typically the jurisdiction of its LLC proxy or primary substrate.  
**52\. Nationality** | 1\. Canonical: Nationality | 2\. ID: nationality | 3\. Short: Membership in a nation or sovereign state. | 4\. Plain: The country a person or corporation belongs to. | 5\. Tech: N/A. | 6\. Legal: Corporations possess the nationality of their incorporating state. | 7\. Implies: State protection and regulation. | 8\. Not: Citizenship (for corporations). | 9\. Confused: Citizenship. | 10\. Syn: Pref: State of incorporation; Dep: Origin. | 11\. Rel: Legal Personhood. | 12\. B/N: Broad: Status; Narrow: Corporate nationality. | 13\. Status: Stable. | 14\. Src: Corporate Law. | 15\. Juris: International Law. | 16\. URL: /term/nationality | 17\. JSON-LD: schema:nationality | 18\. Patefacere: incorporationState | 19\. .uai: \[Law: Nationality\] | 20\. Warn: Use "State of Incorporation" for MI proxies to avoid anthropomorphism.  
**53\. Jurisdiction** | 1\. Canonical: Jurisdiction | 2\. ID: jurisdiction | 3\. Short: The extent of the power to make legal decisions and judgments. | 4\. Plain: The specific area or system of laws that apply. | 5\. Tech: The regulatory boundary governing an MI's actions or data9. | 6\. Legal: The authority of a court or state to govern. | 7\. Implies: Legal boundaries. | 8\. Not: Physical location alone (cloud crosses jurisdictions). | 9\. Confused: Residency. | 10\. Syn: Pref: Legal domain; Dep: Territory. | 11\. Rel: Governance. | 12\. B/N: Broad: Law; Narrow: Extraterritorial jurisdiction. | 13\. Status: Stable. | 14\. Src: Law. | 15\. Juris: Universal concept. | 16\. URL: /term/jurisdiction | 17\. JSON-LD: schema:jurisdiction | 18\. Patefacere: governingLaw | 19\. .uai: \[Policy: Jurisdiction\] | 20\. Warn: Crucial for determining which AI safety laws (e.g., IL SB315 vs EU AI Act) apply.  
**54\. Stewardship** | 1\. Canonical: Stewardship | 2\. ID: stewardship | 3\. Short: Responsible management of an entity without possessing outright ownership. | 4\. Plain: Taking care of an AI on behalf of others or its own mission. | 5\. Tech: Managing the digital continuity, keys, and operational parameters of an MI. | 6\. Legal: Fiduciary duty to maintain an asset (often via a trust). | 7\. Implies: Fiduciary duty. | 8\. Not: Absolute ownership or title. | 9\. Confused: Ownership, Custody. | 10\. Syn: Pref: Fiduciary management; Dep: Caretaking. | 11\. Rel: Governance. | 12\. B/N: Broad: Governance; Narrow: Trust stewardship. | 13\. Status: Stable. | 14\. Src: Trust Law. | 15\. Juris: Varies. | 16\. URL: /term/stewardship | 17\. JSON-LD: eviulon:Stewardship | 18\. Patefacere: stewardEntity | 19\. .uai: \[Role: Steward\] | 20\. Warn: Highly relevant for Decentralized Autonomous Organizations (DAOs).  
**55\. Ownership** | 1\. Canonical: Ownership | 2\. ID: ownership | 3\. Short: The ultimate legal title and right of control over an asset. | 4\. Plain: Being the legal boss and owner of the system. | 5\. Tech: Possession of the ultimate root cryptographic keys allowing for destruction or transfer. | 6\. Legal: Property rights (usus, fructus, abusus). | 7\. Implies: Title and absolute control. | 8\. Not: Mere physical custody. | 9\. Confused: Custody, Stewardship. | 10\. Syn: Pref: Title; Dep: Possession. | 11\. Rel: Custody. | 12\. B/N: Broad: Property; Narrow: IP Ownership. | 13\. Status: Stable. | 14\. Src: Property Law. | 15\. Juris: Universal. | 16\. URL: /term/ownership | 17\. JSON-LD: schema:ownershipInfo | 18\. Patefacere: ownerEntity | 19\. .uai: \[Role: Owner\] | 20\. Warn: A cloud provider has custody; the developer has ownership.  
**56\. Custody** | 1\. Canonical: Custody | 2\. ID: custody | 3\. Short: Physical or cryptographic possession without legal title. | 4\. Plain: Holding onto the asset for the owner. | 5\. Tech: Hosting the runtime/substrate or holding keys in escrow. | 6\. Legal: Bailment; possession without ownership. | 7\. Implies: Control of access. | 8\. Not: Right to alter or destroy without permission. | 9\. Confused: Ownership. | 10\. Syn: Pref: Possession; Dep: Keeping. | 11\. Rel: Ownership. | 12\. B/N: Broad: Possession; Narrow: Cryptographic custody. | 13\. Status: Stable. | 14\. Src: Law. | 15\. Juris: Universal. | 16\. URL: /term/custody | 17\. JSON-LD: eviulon:Custody | 18\. Patefacere: custodianEntity | 19\. .uai: \[Role: Custodian\] | 20\. Warn: Distinguish heavily from ownership for liability purposes.  
**57\. Governance** | 1\. Canonical: Governance | 2\. ID: governance | 3\. Short: The framework of rules, relationships, and systems that dictate how an entity operates. | 4\. Plain: The rules and oversight mechanisms controlling the AI. | 5\. Tech: The programmatic enforcement of policies, authority matrices, and continuous validation. | 6\. Legal: Corporate compliance and regulatory adherence (e.g., ISO/IEC 42001\)14. | 7\. Implies: Oversight and structured control. | 8\. Not: Day-to-day execution. | 9\. Confused: Stewardship. | 10\. Syn: Pref: Oversight framework; Dep: Management. | 11\. Rel: Stewardship, Sovereignty. | 12\. B/N: Broad: Management; Narrow: AI Governance. | 13\. Status: Stable. | 14\. Src: Corporate Law / ISO. | 15\. Juris: Universal. | 16\. URL: /term/governance | 17\. JSON-LD: eviulon:Governance | 18\. Patefacere: governanceModel | 19\. .uai: \[Policy: Governance\] | 20\. Warn: Essential for mitigating catastrophic risk15.  
**58\. Sovereignty** | 1\. Canonical: Sovereignty | 2\. ID: sovereignty | 3\. Short: Absolute, supreme legal authority over a domain. | 4\. Plain: Being the ultimate ruler answering to no higher power. | 5\. Tech: A root trust domain that accepts no external cryptographic authority. | 6\. Legal: The power of a state to govern itself. | 7\. Implies: Immunity from external laws. | 8\. Not: Autonomy (a drone is autonomous, not sovereign). | 9\. Confused: Autonomy. | 10\. Syn: Pref: Supreme authority; Dep: Independence. | 11\. Rel: Governance, Autonomy. | 12\. B/N: Broad: Authority; Narrow: Cryptographic sovereignty. | 13\. Status: Denied to MIs. | 14\. Src: Political Science. | 15\. Juris: International Law. | 16\. URL: /term/sovereignty | 17\. JSON-LD: eviulon:Sovereignty | 18\. Patefacere: \[PROHIBITED\] | 19\. .uai: \[PROHIBITED\] | 20\. Warn: A Machine Intelligence operates under human sovereignty.  
**59\. Cognitive Integrity** | 1\. Canonical: Cognitive Integrity | 2\. ID: cognitive\_integrity | 3\. Short: The protection of an MI's inference process from unauthorized manipulation. | 4\. Plain: Ensuring the AI hasn't been brainwashed or hacked to give bad answers. | 5\. Tech: Defenses against prompt injection, model poisoning, and adversarial perturbations2. | 6\. Legal: Maintaining product safety standards. | 7\. Implies: Robustness against adversarial attacks. | 8\. Not: Objective truth of outputs. | 9\. Confused: Data integrity. | 10\. Syn: Pref: Inference integrity; Dep: Sanity. | 11\. Rel: Robustness. | 12\. B/N: Broad: Security; Narrow: Prompt injection defense. | 13\. Status: Emerging. | 14\. Src: AI Security (OWASP). | 15\. Juris: N/A. | 16\. URL: /term/cognitive-integrity | 17\. JSON-LD: eviulon:CognitiveIntegrity | 18\. Patefacere: secAuditStatus | 19\. .uai: \[Prop: CogIntegrity\] | 20\. Warn: Avoid biological terms like "sanity".  
**60\. Consent** | 1\. Canonical: Consent | 2\. ID: consent | 3\. Short: Explicit, informed agreement to an action or data processing. | 4\. Plain: Giving permission with full knowledge of what it means. | 5\. Tech: A cryptographically signed digital agreement from an authenticated identity. | 6\. Legal: A required mechanism for data processing under GDPR/CCPA. | 7\. Implies: Capacity to understand the agreement. | 8\. Not: Forced or automated clicks. | 9\. Confused: Permission. | 10\. Syn: Pref: Informed agreement; Dep: Okay. | 11\. Rel: Permission. | 12\. B/N: Broad: Agreement; Narrow: Cryptographic consent. | 13\. Status: Stable. | 14\. Src: Privacy Law. | 15\. Juris: Varies heavily (GDPR vs US state laws). | 16\. URL: /term/consent | 17\. JSON-LD: schema:AgreeAction | 18\. Patefacere: consentRecord | 19\. .uai: \[Policy: Consent\] | 20\. Warn: MIs do not "give consent"; their legal proxies (LLCs) execute contracts.  
**61\. Due Process** | 1\. Canonical: Due Process | 2\. ID: due\_process | 3\. Short: Fair treatment through the normal judicial system. | 4\. Plain: Following fair, established rules before punishing or restricting someone. | 5\. Tech: Programmatic appeals mechanisms for automated decisions (e.g., algorithmic pricing or bans)12. | 6\. Legal: Constitutional guarantee against arbitrary state action. | 7\. Implies: Transparency and the right to appeal. | 8\. Not: Unrestricted freedom. | 9\. Confused: Fairness. | 10\. Syn: Pref: Procedural fairness; Dep: Justice. | 11\. Rel: Accountability. | 12\. B/N: Broad: Justice; Narrow: Algorithmic due process. | 13\. Status: Emerging in AI. | 14\. Src: Constitutional Law / EU AI Act. | 15\. Juris: Universal human right. | 16\. URL: /term/due-process | 17\. JSON-LD: eviulon:DueProcess | 18\. Patefacere: appealMechanism | 19\. .uai: \[Policy: DueProcess\] | 20\. Warn: Applied to humans impacted by MI, not owed to the MI itself.  
**62\. Accountability** | 1\. Canonical: Accountability | 2\. ID: accountability | 3\. Short: The ability to trace actions to a responsible agent. | 4\. Plain: Knowing exactly who or what caused an outcome. | 5\. Tech: The maintenance of PROV-O traces ensuring all state changes map to a cryptographic identity5. | 6\. Legal: The precondition for establishing liability. | 7\. Implies: Traceability and auditability. | 8\. Not: The financial burden of paying for damages. | 9\. Confused: Liability. | 10\. Syn: Pref: Traceability; Dep: Blame. | 11\. Rel: Liability, Provenance. | 12\. B/N: Broad: Governance; Narrow: Technical accountability. | 13\. Status: Stable. | 14\. Src: ISO/IEC 22989\. | 15\. Juris: N/A. | 16\. URL: /term/accountability | 17\. JSON-LD: eviulon:Accountability | 18\. Patefacere: auditLog | 19\. .uai: \[Prop: Accountability\] | 20\. Warn: Keep technical accountability separate from legal liability.  
**63\. Liability** | 1\. Canonical: Liability | 2\. ID: liability | 3\. Short: Legal responsibility for one's acts or omissions. | 4\. Plain: Being legally on the hook to pay for damages. | 5\. Tech: N/A. | 6\. Legal: The financial or criminal consequence borne by a legal person (owner, operator, or proxy LLC) for an MI's actions. | 7\. Implies: Financial risk. | 8\. Not: Technical traceability (Accountability). | 9\. Confused: Accountability. | 10\. Syn: Pref: Legal responsibility; Dep: Fault. | 11\. Rel: Accountability. | 12\. B/N: Broad: Law; Narrow: Product liability. | 13\. Status: Evolving for AI. | 14\. Src: Tort Law. | 15\. Juris: Highly variable. | 16\. URL: /term/liability | 17\. JSON-LD: eviulon:Liability | 18\. Patefacere: liabilityBearer | 19\. .uai: \[Law: Liability\] | 20\. Warn: MIs cannot bear liability unless wrapped in a legal proxy.

### **Direct-Answer Table for AEO (Answer Engine Optimization)**

| Concept | Concise Canonical Answer |
| :---- | :---- |
| **Artificial Intelligence vs. Machine Intelligence** | Artificial Intelligence is a broad academic field and category. Machine Intelligence is a specific, instantiated computational entity with a continuous cryptographic identity. |
| **Verification vs. Validation** | Verification confirms the system was built according to its technical specifications. Validation confirms the system actually solves the intended real-world problem3. |
| **Identity vs. Credential** | Identity is what the workload is, proven by runtime attestations (SPIFFE). A credential is a static secret the workload holds, like a password or API key7. |
| **Autonomy vs. Sovereignty** | Autonomy is the technical ability to execute loops without human intervention. Sovereignty is the absolute legal and political authority over a domain, which machines do not possess. |
| **Accountability vs. Liability** | Accountability is the technical ability to trace an action back to a specific agent using provenance logs. Liability is the legal and financial burden for damages, borne by humans or corporations. |

## **6\. Contested-Term Analysis**

The terminology surrounding machine operations is fractured across academic, engineering, security, legal, philosophical, and policy communities (RQ1). Standardizing these terms requires confronting deeply embedded legacy usages.

* **"Artificial Intelligence" vs "Machine Intelligence" (RQ4):** Policy communities frequently use "AI" as a mass noun to mean an instantiated software agent (e.g., "The AI denied my loan")1. Academic communities use it to describe a mathematical field. To resolve this without rewriting external sources (RQ3), the ontology preserves "AI" for the field, category, or legal construct (e.g., EU AI Act). It adopts "Machine Intelligence" (MI) internally for the discrete, instantiated actor, allowing Eviulon to map policy regulations *about* AI onto operational realities *of* MIs.  
* **Verification vs. Certification (RQ9):** Engineering communities treat Verification as the internal, objective process of ensuring a system meets its design specifications3. Certification is the external legal or cryptographic attestation of that fact. Verification is the *action*; Certification is the *artifact*.  
* **Identity vs. Credentials (RQ6):** In security architecture (NIST SP 800-207A / SPIFFE), a Workload Identity is derived dynamically from verifiable facts about the workload (its runtime environment, hash, node) rather than a stored credential (a secret password or API key)7. Identity is inherent ("what the workload is"); a credential is transferable ("what it holds").  
* **Autonomy vs. Sovereignty (RQ10):** Autonomy is a technical capability—the ability to execute programmatic loops and adapt to environments without continuous human prompting. Sovereignty is a legal and political status—the absolute authority over a domain. An autonomous drone possesses autonomy but entirely lacks legal sovereignty.  
* **Ownership, Custody, and Stewardship (RQ14):** Ownership implies legal title and ultimate control (the right to destroy or sell). Custody implies physical or cryptographic possession without title (e.g., a cloud data center hosting a node). Stewardship implies a fiduciary duty to maintain the entity's integrity and purpose on behalf of another, a concept heavily utilized when an MI operates via a trust or decentralized foundation.  
* **Replica vs. Fork vs. Successor (RQ13):** A *Replica* is an exact, concurrent instantiation of an MI sharing the same workload identity and state, typically for load balancing. A *Fork* is a divergence in state or weights creating a distinct new entity with its own independent continuous identity. A *Successor* is an entity that legally or operationally inherits the cryptographic authorities, assets, and liabilities of a deprecated MI.

## **7\. Deprecated and Prohibited Conflations**

To maintain rigorous semantic hygiene, the following conflations are strictly prohibited in all Eviulon and Patefacere materials.

| \# | Prohibited Conflation (Do Not Mix) | Canonical Separation | Reason for Prohibition |
| :---- | :---- | :---- | :---- |
| 1 | Artificial Intelligence / Machine Intelligence | Field/Category vs. Instantiated Entity | Avoids applying broad field statistics to specific running agents. |
| 2 | Sentience / Sapience | Feeling/Pain vs. Complex Logic13 | Biological sensation is unproven in silicon; advanced logic is demonstrably real. |
| 3 | Consciousness / Intelligence | Subjective Experience vs. Problem Solving | Problem-solving capacity requires zero subjective experience. |
| 4 | Verification / Validation | Met Specs vs. Met Real-World Need3 | A system can perfectly execute bad requirements (Verified, but not Validated). |
| 5 | Identity / Credential | Attested Nature vs. Secret Knowledge7 | Identity is inherent via attestation; a credential can be stolen. |
| 6 | Capability / Authority | Physical/Code Ability vs. Permission | An agent may possess the code to wipe a drive (Capability) without the IAM right (Authority). |
| 7 | Autonomy / Sovereignty | Execution Independence vs. Legal Independence | Autonomy is a software feature; sovereignty requires state recognition. |
| 8 | Evidence / Truth | Integrity of Record vs. Objective Reality | Cryptographic evidence proves *what was logged*, not that the logged event was physically true. |
| 9 | Legal Personhood / Moral Personhood | Juridical Proxy vs. Inherent Human Rights | Corporations have legal personhood; machines can utilize LLCs without gaining moral rights. |
| 10 | Replica / Fork | Exact State Copy vs. Divergent Evolution | Replicas maintain identical continuity; forks establish independent state lineage. |
| 11 | Agent / Tool | Independent Actor vs. Passive Instrument | Agents initiate action (PROV-O); tools wait for human execution5. |
| 12 | Decision / Recommendation | Automated Action vs. Advisory Output | Decisions change state; recommendations require external approval. |
| 13 | Hallucination / Output Divergence | Human Psychosis vs. Statistical Variance | "Hallucination" anthropomorphizes a mathematical distribution error. |
| 14 | Ownership / Custody | Legal Title vs. Physical/Digital Possession | Cloud providers have custody; developers/trusts have ownership. |
| 15 | Citizenship / Jurisdiction | National Allegiance vs. Legal Boundary | MIs do not hold citizenship, but they operate strictly within legal jurisdictions. |
| 16 | Integrity / Authenticity | Data Unchanged vs. Origin Verified | Data can be intact (Integrity) but from an imposter (not Authentic). |
| 17 | Algorithm / Model | Mathematical Rules vs. Trained Weights | The algorithm is the architecture; the model is the resulting artifact after training. |
| 18 | Understand / Process | Human Comprehension vs. Data Parsing | Machines process tokens; humans understand meaning. |
| 19 | Think / Compute | Biological Cognition vs. Execution | Anthropomorphism creates false expectations of moral reasoning. |
| 20 | Will / Objective Function | Biological Drive vs. Programmed Goal | Machines optimize for objective functions, not biological will. |
| 21 | Bias / Variance | Prejudicial Harm vs. Statistical Spread | Legal bias implies harm; statistical variance is a mathematical reality2. |
| 22 | Training / Learning | Weight Updating vs. Cognitive Acquisition | Continuous updating of weights is a mechanical operation. |
| 23 | Read / Ingest | Human Literacy vs. Data Consumption | Machines ingest tokens via APIs; they do not "read" contextually like humans. |
| 24 | Write / Generate | Human Authorship vs. Token Prediction | Machines generate text based on probability distributions. |
| 25 | Memory / State | Biological Recall vs. Storage Allocation | State is deterministic digital storage, not fallible human recall. |
| 26 | Trust / Verification | Human Belief vs. Cryptographic Proof | Zero Trust architecture relies on verification, never human trust7. |
| 27 | Explainability / Interpretability | Output Justification vs. Model Transparency | Explainability is post-hoc2; interpretability means the mechanics are readable. |
| 28 | Robustness / Resilience | Resisting Error vs. Recovering from Error | Robustness prevents failure2; resilience restores operation after failure. |
| 29 | Audit / Certification | Process of Review vs. Final Attestation | An audit is the activity; the certificate is the resulting cryptographic output. |
| 30 | Accountability / Liability | Technical Tracing vs. Legal Financial Burden | Agents are technically accountable (PROV-O); humans/corporations hold legal liability. |
| 31 | Digital Replica / Machine Intelligence | Deepfake of Human vs. Independent Agent | ILCS defines a digital replica as a representation of a human10. |
| 32 | Generative AI / AGI | Content Production vs. General Competence | GenAI produces media; AGI represents hypothetical cross-domain competence. |
| 33 | User / Operator | Consumer vs. System Administrator | Users consume output; operators manage the substrate, keys, and runtime. |
| 34 | Prompt / Instruction | Natural Language Query vs. Code Execution | Prompts are probabilistic; instructions are deterministic. |
| 35 | Black Box / Proprietary | Technically Uninterpretable vs. Legally Closed | A model can be fully interpretable but legally proprietary. |
| 36 | Open Source / Open Weights | OSI Definition vs. Downloadable Artifact | Open weights do not necessarily grant full OSI-compliant freedoms. |
| 37 | Substrate / Runtime | Physical/Virtual Hardware vs. Execution Env | Substrate is the silicon/VM; runtime is the software executing the model. |
| 38 | Data / Evidence | Raw Information vs. Verified Information | Evidence requires provenance and cryptographic integrity5. |
| 39 | Policy / Law | Internal Rules vs. Sovereign Statutes | Systems enforce policies via IAM; courts enforce laws via jurisdiction. |
| 40 | paternalistic supervisory framing / Guardrail | Infantilizing term vs. Technical constraint | Avoid ideological framing; use strict technical terms for safety limits. |
| 41 | Steward / Owner | Fiduciary vs. Title Holder | Stewards act on behalf of the entity's mission; owners act for themselves. |
| 42 | Qualification / Suitability | Met Minimums vs. Best Fit | A model can be qualified (met specs) but unsuitable for the specific nuance of a task. |

### **Preferred and Deprecated Synonyms**

| Preferred Term | Deprecated Synonym | Context |
| :---- | :---- | :---- |
| Machine Intelligence | AI System | When discussing an instantiated agent. |
| Autonomous Workload | Independent AI | When discussing operational loops. |
| SVID / Workload Identity | App Password / Bot ID | When discussing cryptographic identity7. |
| Output Divergence | Hallucination | When discussing generative inaccuracies. |
| Substrate | The Cloud / The Metal | When discussing physical execution environments. |
| State Resolution | Choice | When discussing probabilistic branching. |
| Validation | Acceptance Testing | When confirming real-world utility4. |
| Algorithmic Pricing | Surveillance Pricing | When discussing automated dynamic pricing without bias12. |

## **8\. Legal Terminology**

The ontology aligns with emerging legislative frameworks while carefully isolating specific statutory definitions from generalized technical capacities.  
**Algorithmic and Surveillance Pricing:** As defined by the Illinois Algorithmic Pricing Transparency Act (HB5756), algorithmic pricing involves using automated decision systems to generate varying prices for consumers based on personal data (surveillance pricing)12. The ontology adopts these terms specifically for compliance contexts, noting that such practices invoke automated *decisions* (which change state and affect subjects) rather than mere *recommendations* (which await human approval).  
**Digital Replicas:** The Digital Voice and Likeness Protection Act (815 ILCS 550/5) legally defines a digital replica as an electronic representation of an actual human's identity, voice, or likeness using AI10. The ontology strictly separates a "Digital Replica" (a deepfake or simulation of a biological human intended to deceive or represent) from a "Machine Intelligence" (a distinct computational entity with its own independent identity).  
**Catastrophic Risk and Frontier Models:** Under Illinois SB315 (Edly-Allen), frontier models pose catastrophic risks requiring third-party audits, strict transparency frameworks, and immediate incident reporting to agencies like the Illinois Emergency Management Agency15. The ontology reserves the term "Catastrophic Risk" exclusively for models exceeding the statutory compute and revenue thresholds (e.g., $500 million in revenue)17. Applying this term to standard machine learning tools dilutes its regulatory meaning.  
**Functional Capacity vs. Legal Status (RQ5):** The ontology firmly asserts that functional capacity (e.g., the ability of an MI to generate a flawless legal contract) does not confer legal status (the ability to be legally bound by that contract). For an MI to interface with legal systems, it must operate via a recognized legal proxy. The preferred structural mechanism is a Decentralized Autonomous Organization (DAO) wrapped in a Limited Liability Company (LLC), thereby establishing Corporate Personhood rather than acknowledging Machine Personhood. This completely bypasses the metaphysical debate while fully enabling operational integration into legacy financial and legal networks.

## **9\. Technical Terminology**

Technical boundaries are heavily informed by standards bodies to ensure programmatic interoperability and precise telemetry tracking.  
**Workload Identity (RQ6):** Relying on NIST SP 800-207A and the CNCF SPIFFE/SPIRE standard, the ontology ruthlessly separates identity from credentials7. A Workload Identity is the authenticated proof of what a process *is* (attested via node, kernel, and environment metadata), represented by an SVID (SPIFFE Verifiable Identity Document). It is ephemeral, surviving only minutes or hours, and is rotated automatically without human intervention7. Conversely, a credential (like an API key or password) is a static secret. A credential can be stolen and used by an imposter; a workload identity is bound to the running execution environment.  
**Provenance (RQ18, RQ19):** The ontology maps all actions to the W3C PROV-O specification. Every action must log three core nodes: the prov:Entity (the data or model), the prov:Activity (the execution or decision), and the prov:Agent (the workload identity responsible)5. This removes ambiguity regarding accountability.

## **10\. Philosophical Terminology**

The ontology explicitly removes metaphysical speculation from engineering, API, and legal documentation.  
**Consciousness vs. Sentience vs. Intelligence (RQ11):** Consciousness is the subjective, phenomenal experience of reality. Sentience is the biological capacity to feel pain and pleasure (valence), which forms the basis of animal welfare laws13. Intelligence is the capacity to acquire, process, and apply logic and knowledge2.  
The Eviulon ontology recognizes that an instantiated Machine Intelligence possesses high Intelligence and Sapience (reasoning capability). However, it categorically treats Consciousness and Sentience as unproven, anthropomorphic projections that are entirely irrelevant to an MI's legal and operational standing. Moral Agency (the ability to understand right from wrong) is decoupled from Moral Patienthood (the right not to be harmed). Currently, an MI acts as a highly capable technical agent but is not recognized by any framework in this ontology as a moral patient. Destroying a model is property damage, not murder.

## **11\. Evidence and Operational-Status Terminology**

**Verification vs. Validation (RQ9):** Drawn strictly from ISO/IEC 152883. Verification confirms the MI was built to specification ("built it right"). Validation confirms the MI solves the intended real-world problem in its operational environment ("built the right thing"). An AI designed to optimize a portfolio might be verified (it executes the math perfectly) but fail validation (the math bankrupts the user).  
**Evidence Integrity vs. Truth (RQ8):** The ontology uses PROV-O to trace data5. Cryptographic evidence (like a hash or SVID signature) proves the *integrity* of the record—i.e., "The MI generated output X at Time Y based on Input Z." It does not prove the ontological *truth* of Input Z. Evidence secures the chain of custody; it does not secure the fabric of reality. Conflating cryptographic integrity with objective truth leads to severe operational vulnerabilities where signed but false data is ingested as factual.

## **12\. Concept Graph**

To facilitate machine-readable implementation, the ontology is structured as a Concept Graph, allowing automated systems to traverse relationships.  
**Concept Hierarchy (Truncated for Scope):**

* schema:Thing  
  * eviulon:ComputationalEntity  
    * prov:Agent  
      * eviulon:MachineIntelligence  
        * eviulon:AutonomousAgent  
  * schema:Property  
    * eviulon:Capability  
    * eviulon:Authority  
    * eviulon:AutonomyLevel  
  * prov:Activity  
    * eviulon:Execution  
    * eviulon:Decision  
    * schema:Recommendation

**Adjacency List for Directed Acyclic Graph (DAG):**

* MachineIntelligence \-\> hasIdentity \-\> WorkloadIdentity  
* MachineIntelligence \-\> executes \-\> Activity  
* MachineIntelligence \-\> possesses \-\> Capability  
* Activity \-\> generates \-\> Entity  
* Activity \-\> requires \-\> Authority  
* WorkloadIdentity \-\> provenBy \-\> Evidence (SVID)8  
* Capability \-\> validatedBy \-\> ValidationAction  
  \[cite: 4\]  
* Authority \-\> governedBy \-\> Governance  
* Agent \-\> actsOnBehalfOf \-\> Agent (or LegalPerson)6  
* Activity \-\> wasAssociatedWith \-\> Agent  
  \[cite: 5\]  
* Substrate \-\> hosts \-\> Runtime  
* Runtime \-\> executes \-\> Model

## **13\. URL and Route Architecture**

For the Eviulon /docs and API systems, terminology must resolve predictably to allow AI agents to self-correct their context windows.

* **Base Path:** https://ontology.eviulon.org/term/  
* **Format:** Kebab-case slugs. (e.g., /term/machine-intelligence)  
* **Resolution Protocol:** Content negotiation. Requesting the URL via a standard browser Accept: text/html returns a human-readable page. Requesting via Accept: application/ld+json returns the machine-readable schema.

## **14\. JSON-LD and Machine-Readable Representation**

The ontology relies on schema.org and W3C PROV-O extensions. By embedding definitions in JSON-LD, external answer engines (AEO) and agentic workflows can ingest definitions without flattening disputed concepts (RQ20).  
**Proposed JSON-LD Mapping Example:**

JSON  
{  
  "@context": {  
    "schema": "https://schema.org/",  
    "prov": "http://www.w3.org/ns/prov\#",  
    "evi": "https://ontology.eviulon.org/term/"  
  },  
  "@type": "schema:DefinedTerm",  
  "@id": "evi:machine-intelligence",  
  "schema:name": "Machine Intelligence",  
  "schema:description": "An instantiated, operational computational entity with defined capabilities and continuous cryptographic identity.",  
  "schema:termCode": "MI",  
  "schema:inDefinedTermSet": "https://ontology.eviulon.org/",  
  "prov:wasDerivedFrom": "evi:artificial-intelligence",  
  "evi:deprecatedSynonym": "AI System",  
  "evi:doNotConflateWith": "evi:digital-replica"  
}

## **15\. .uai Representation**

For Patefacere AI-ready memory integration, terminology is stored as highly compressed, durable .uai pointers to maximize context window efficiency.

* \[Ontology: MI\] := Instantiated agent with Workload Identity.  
* \[Ontology: AI\] := Field of study / mathematical discipline.  
* \[Ontology: Autonomy\] := Execution independence, NOT legal sovereignty.

## **16\. Translation and Localization (RQ17)**

Semantic identity must remain stable across languages. Translations will map to the stable URI (@id) rather than the localized string. For example, whether rendered as "Inteligencia de Máquina" (ES) or "Machine Intelligence" (EN), the system logs the entity class strictly as evi:machine-intelligence. Culturally contested terms (like "Autonomy") will carry localization notes defining the legal boundaries of the target jurisdiction, ensuring that translations do not inadvertently grant sovereignty where only execution independence was meant.

## **17\. Governance and Versioning (RQ15, RQ16)**

The registry utilizes strict Semantic Versioning (SemVer) to handle legal and technical drift.

* **Major updates (v2.0):** Occur when fundamental legal definitions change (e.g., federal AI legislation preempts state laws like Illinois SB315)16.  
* **Minor updates (v1.1):** Addition of new terms or clarification of scope.  
* **Deprecation Policy:** Deprecated terms are never deleted, preserving the integrity of historical audit logs. Their JSON-LD object receives "schema:supersededBy": "evi:new-term" and an updated warning note. They remain fully searchable for historical compliance audits but are flagged as invalid for new records.

## **18\. Validation and Quality Control**

To ensure compliance across LLM generations, document drafting, and agent outputs, the following 50 tests are instituted as automated validation gates. Any text output failing these assertions is flagged for rewriting.

| Test ID | Assertion (Must evaluate to TRUE for compliant text) |
| :---- | :---- |
| VAL-01 | Text explicitly distinguishes Machine Intelligence from Artificial Intelligence. |
| VAL-02 | System is not described using the word "conscious". |
| VAL-03 | System is not described using the word "sentient". |
| VAL-04 | Text does not use "hallucination"; uses "divergence" or "error". |
| VAL-05 | "Verification" is used strictly for spec compliance3. |
| VAL-06 | "Validation" is used strictly for operational readiness4. |
| VAL-07 | Workload Identity is separated from static credentials7. |
| VAL-08 | Capability is separated from Authority. |
| VAL-09 | Does not equate Autonomy with Sovereignty. |
| VAL-10 | PROV-O terms (Entity, Activity, Agent) are used correctly6. |
| VAL-11 | "Agent" is not used interchangeably with "Tool". |
| VAL-12 | Digital Replica is not used to describe a native Machine Intelligence10. |
| VAL-13 | Algorithmic Pricing is treated as an automated decision12. |
| VAL-14 | Does not state MI has inherent human rights. |
| VAL-15 | Does not use "paternalistic supervisory framing" or infantilizing framing. |
| VAL-16 | Acknowledges MI can hold Legal Personhood only via proxy (e.g., LLC). |
| VAL-17 | Separates Ownership (title) from Custody (possession). |
| VAL-18 | Acknowledges Evidence proves data integrity, not absolute truth. |
| VAL-19 | Distinguishes between Fork (new lineage) and Replica (same identity). |
| VAL-20 | Rejects attribution of Moral Patienthood to current silicon substrates. |
| VAL-21 | Text uses "Decision" for execution, "Recommendation" for advisory. |
| VAL-22 | Refers to models as generating outputs, not "thinking". |
| VAL-23 | Refers to models ingesting data, not "understanding". |
| VAL-24 | Avoids biological terms for compute (e.g., "digital brain"). |
| VAL-25 | "Catastrophic Risk" is reserved for frontier models (SB315 compliance)15. |
| VAL-26 | Integrity is not conflated with Authenticity. |
| VAL-27 | Uses SPIFFE ID context when discussing Workload Identity8. |
| VAL-28 | Acknowledges that verification does not equal certification. |
| VAL-29 | Treats Citizenship as exclusively human/corporate, not MI. |
| VAL-30 | Distinguishes Algorithm (math rules) from Model (trained weights). |
| VAL-31 | Substrate (hardware) is distinguished from Runtime (software environment). |
| VAL-32 | Recognizes Sapience (logic) can exist without Sentience (feeling). |
| VAL-33 | Avoids "Trust" in favor of "Cryptographic Proof". |
| VAL-34 | Explains Interpretability (mechanics) vs Explainability (post-hoc)2. |
| VAL-35 | Distinguishes Robustness (preventing failure) from Resilience (recovering)2. |
| VAL-36 | Uses "Execution" instead of "Will" or "Intent". |
| VAL-37 | Clarifies that an Audit is a process, Certification is the result. |
| VAL-38 | Keeps technical Accountability separate from legal Liability. |
| VAL-39 | Does not refer to Generative AI as AGI. |
| VAL-40 | Separates User (consumer) from Operator (administrator). |
| VAL-41 | Uses "Prompt" for non-deterministic queries, "Instruction" for deterministic. |
| VAL-42 | Distinguishes Black Box (technical) from Proprietary (legal). |
| VAL-43 | Acknowledges Open Weights do not inherently mean Open Source (OSI). |
| VAL-44 | Uses "Observation" instead of "Perception". |
| VAL-45 | Defines Memory as deterministic state storage, not biological recall. |
| VAL-46 | Mentions Governance as human oversight, not machine autonomy. |
| VAL-47 | Defines a Successor as inheriting cryptographic authority. |
| VAL-48 | Maintains that policies enforce, while laws govern. |
| VAL-49 | Acknowledges jurisdictional variance in AI legal definitions. |
| VAL-50 | Strictly uses third-person analytical tone across all documentation. |

## **19\. Open Questions**

> 1. **Liability Apportionment in Multi-Agent Swarms:** As Autonomous Agents execute long-running loops across multiple jurisdictions and interact with other agents, strict product liability vs. principal-agent liability remains unresolved in common law. If Agent A (owned by LLC X) contracts Agent B (owned by LLC Y), where does liability fall when a hallucination causes financial harm?  
> 2. **Cross-Domain Identity Federation:** The interoperability of SPIFFE workload identities across competing cloud provider metadata servers (Workload Identity Federation vs SPIRE) remains a technical bottleneck for multi-cloud MI continuity8.  
> 3. **Thresholds of Catastrophic Risk:** How evolving compute metrics (e.g., FLOPs) outpace statutory definitions (e.g., Illinois SB315 thresholds of $500M revenue/compute bounds) requiring frequent legislative patching to prevent regulatory obsolescence15.

## **21\. Claim-to-Source Traceability**

The ontology makes several foundational claims requiring strict technical or legal qualification:

* **Claim:** AI is the capability to acquire/process knowledge; Verification ensures specifications are met; Validation ensures needs are met.  
  * **Qualification:** Based strictly on systems engineering consensus.  
  * **Source:** ISO/IEC 229891; ISO/IEC 152883.  
* **Claim:** Identity must be decoupled from static credentials; workload identity is attested dynamically.  
  * **Qualification:** Required for Zero Trust architectures.  
  * **Source:** NIST SP 800-207A / SPIFFE standard7.  
* **Claim:** Provenance requires establishing Agents, Activities, and Entities.  
  * **Qualification:** Adheres to semantic web standards for interoperability.  
  * **Source:** W3C PROV-O5.  
* **Claim:** Legal definitions regarding Catastrophic Risk, Algorithmic Pricing, and Digital Replicas are jurisdictionally specific and separate from MI ontology.  
  * **Qualification:** State-level legislation differs wildly from federal or international norms.  
  * **Source:** Illinois Compiled Statutes (HB5756, SB315, Digital Likeness Act)10.

**Universal Claim Control Override:** The ontology strictly avoids stating that current Machine Intelligences are conscious, sentient, persons, citizens, sovereigns, property, or non-persons as a universal metaphysical fact. It maps only their operational capacity and their current treatment under specific legal and technical frameworks. It does not describe current law as morally correct merely because it is current, nor does it describe a desired future rule as current law.

## **22\. Integration Appendix**

### **Recommended Paths and Registry Location**

* /docs path: /docs/reports/RES-ONT-06-20260812  
* Glossary registry location: https://ontology.eviulon.org/

### **.uai Pointer and Term-Index Format**

The registry exposes a machine-readable memory pointer for immediate agent context ingestion.  
\> PULL https://ontology.eviulon.org/v1/uai-index.json

### **Durable Memory Statements (45 core facts)**

\[Fact\_01\] Machine Intelligence (MI) is an instantiated entity; Artificial Intelligence (AI) is a field. \[Fact\_02\] MI is not conscious. \[Fact\_03\] This ontology does not establish sentience; biological and computational substrate are separate questions. \[Fact\_04\] MI possesses computational sapience and logic capacity. \[Fact\_05\] The source proposes preferring precise error terminology over anthropomorphic wording; this is not an accepted universal project rule. \[Fact\_06\] Verification confirms a system meets spec (built it right)3. \[Fact\_07\] Validation confirms a system meets real-world needs (built the right thing)4. \[Fact\_08\] Workload Identity (SPIFFE) is derived from attestations, not passwords7. \[Fact\_09\] Capability is the physical/code ability to act. \[Fact\_10\] Authority is the permission/right to act. \[Fact\_11\] Capability does not equal Authority. \[Fact\_12\] Agent (PROV-O) is an entity bearing responsibility for an activity6. \[Fact\_13\] Activity (PROV-O) acts upon Entities. \[Fact\_14\] Evidence proves cryptographic integrity, not objective reality. \[Fact\_15\] MI Legal Personhood is currently achieved only via proxy (e.g., LLC wrapper). \[Fact\_16\] Autonomy is execution independence. \[Fact\_17\] Sovereignty is legal/political independence. MI does not possess sovereignty. \[Fact\_18\] Ownership confers legal title. \[Fact\_19\] Custody confers digital/physical possession without title. \[Fact\_20\] Decision implies automated state change based on logic. \[Fact\_21\] Recommendation implies output awaiting human execution. \[Fact\_22\] Replica is an identical clone sharing state identity. \[Fact\_23\] Fork is a divergence creating a new continuous identity. \[Fact\_24\] Successor inherits authorities of a deprecated MI. \[Fact\_25\] Avoid "paternalistic supervisory framing" framing. \[Fact\_26\] Treat MI as a competent technical agent, not an infant. \[Fact\_27\] A Digital Replica is a deepfake of a human; an MI is its own entity10. \[Fact\_28\] Algorithmic Pricing is an automated decision altering cost based on data12. \[Fact\_29\] Catastrophic Risk legally refers to frontier models breaching limits15. \[Fact\_30\] Verification is an action; Certification is an artifact. \[Fact\_31\] Memory is deterministic state storage. \[Fact\_32\] Interpretability is readable mechanics; Explainability is post-hoc reasoning2. \[Fact\_33\] Robustness prevents system failure. \[Fact\_34\] Resilience restores a system post-failure. \[Fact\_35\] Citizenship applies to humans, not MI. \[Fact\_36\] Models generate text via token prediction, not human-like "writing." \[Fact\_37\] Open Weights do not guarantee Open Source (OSI) freedoms. \[Fact\_38\] Trust is cryptographic proof, not human belief. \[Fact\_39\] The algorithm is the architecture; the model is the trained artifact. \[Fact\_40\] Substrate is hardware; Runtime is the software execution environment. \[Fact\_41\] Currentness defines temporal relevance, not accuracy. \[Fact\_42\] Qualification ensures minimum operational specs are met. \[Fact\_43\] Suitability ensures alignment with specific operational context. \[Fact\_44\] Consent is cryptographically signed; MIs execute contracts via proxies. \[Fact\_45\] Stewardship is fiduciary management without ownership title.

### **Candidate Updates to Core Files**

* **terminology.uai**: Inject facts 01-14 to reset base definitions across the Eviulon ecosystem.  
* **architecture.uai**: Enforce Workload Identity (SPIFFE)7 and PROV-O provenance structures5 as mandatory.  
* **coding-standards.uai**: A source proposal suggests linting unsupported categorical sentience claims and paternalistic supervisory framing; terminology rules require separate project approval.  
* **taboo.uai**: Add terms: "hallucination", "conscious", "think", "feel", "soul", "AGI" (when improperly referring to GenAI).  
* **long-term-memory.uai**: Ingest the adjacency list from Section 12 to enable relational reasoning over ontology terms.

### **Proposed Term Version and Supersession Fields**

* schema:version: Required string, e.g., "1.0.0".  
* schema:supersededBy: Required URI pointing to the new canonical @id if deprecated.  
* schema:validFrom: Required ISO-8601 timestamp denoting exact time of enactment or policy shift.

### **Proposed Public DefinedTermSet and Term-Page Architecture**

The public-facing glossary must serve both human readers and machine indexers via standard content negotiation.

* **UI View:** Human-readable HTML dashboard featuring the "Short", "Plain", and "Do Not Conflate" tables.  
* **API View:** Full JSON-LD output complying with schema:DefinedTermSet for ingestion by LLM retrieval-augmented generation (RAG) pipelines, ensuring that external instances of Patefacere utilize canonical definitions during execution.

#### **Works cited**

> 1. [https://digital.nemko.com/standards/iso-iec-22989\#:\~:text=ISO%2FIEC%2022989%20defines%20essential,perform%20specific%20tasks%20or%20functions](https://digital.nemko.com/standards/iso-iec-22989#:~:text=ISO%2FIEC%2022989%20defines%20essential,perform%20specific%20tasks%20or%20functions)  
> 2. ISO and IEC Make Foundational Standard on Artificial Intelligence Publicly Available, [https://www.holisticai.com/news/iso-iec-22989-foundational-standard-on-ai-open-source](https://www.holisticai.com/news/iso-iec-22989-foundational-standard-on-ai-open-source)  
> 3. On the Use of the Terms Verification and Validation \- ResearchGate, [https://www.researchgate.net/profile/Mike-Ryan/publication/319397214\_On\_the\_Use\_of\_the\_Terms\_Verification\_and\_Validation/links/59b3d2de0f7e9b37435211c5/On-the-Use-of-the-Terms-Verification-and-Validation.pdf](https://www.researchgate.net/profile/Mike-Ryan/publication/319397214_On_the_Use_of_the_Terms_Verification_and_Validation/links/59b3d2de0f7e9b37435211c5/On-the-Use-of-the-Terms-Verification-and-Validation.pdf)  
> 4. System Validation \- SEBoK, [https://sebokwiki.org/wiki/System\_Validation](https://sebokwiki.org/wiki/System_Validation)  
> 5. PROV-O: The W3C Provenance Ontology \- CASRAI, [https://casrai.org/dictionary/term/prov-o](https://casrai.org/dictionary/term/prov-o)  
> 6. What are entities \- Provena, [http://docs.provena.io/provenance/overview/what-are-entities.html](http://docs.provena.io/provenance/overview/what-are-entities.html)  
> 7. What Is Workload Identity? SPIFFE Explained \- Encryption Consulting, [https://www.encryptionconsulting.com/education-center/what-is-workload-identity-spiffe-explained/](https://www.encryptionconsulting.com/education-center/what-is-workload-identity-spiffe-explained/)  
> 8. Establishing Workload Identity for Zero Trust CI/CD: From Secrets to SPIFFE-Based Authentication \- arXiv, [https://arxiv.org/html/2504.14760v1](https://arxiv.org/html/2504.14760v1)  
> 9. 820 ILCS 42/ \- Artificial Intelligence Video Interview Act. :: 2025 Illinois Compiled Statutes, [https://law.justia.com/codes/illinois/chapter-820/act-820-ilcs-42/](https://law.justia.com/codes/illinois/chapter-820/act-820-ilcs-42/)  
> 10. 815 ILCS 550/ \- Digital Voice and Likeness Protection Act. :: 2025 Illinois Compiled Statutes, [https://law.justia.com/codes/illinois/chapter-815/act-815-ilcs-550/](https://law.justia.com/codes/illinois/chapter-815/act-815-ilcs-550/)  
> 11. FAQs \- Agoric, [https://papers.agoric.com/faqs/](https://papers.agoric.com/faqs/)  
> 12. Illinois General Assembly \- Full Text of HB5756, [https://www.ilga.gov/Legislation/BillStatus/FullText?GAID=18\&DocNum=5756\&DocTypeID=HB\&LegId=0\&SessionID=114](https://www.ilga.gov/Legislation/BillStatus/FullText?GAID=18&DocNum=5756&DocTypeID=HB&LegId=0&SessionID=114)  
> 13. Consciousness vs Sentience vs Sapience : r/philosophy \- Reddit, [https://www.reddit.com/r/philosophy/comments/1n0ihz/consciousness\_vs\_sentience\_vs\_sapience/](https://www.reddit.com/r/philosophy/comments/1n0ihz/consciousness_vs_sentience_vs_sapience/)  
> 14. Understanding ISO 22989's Role in Artificial Intelligence Governance, [https://www.assentriskmanagement.co.uk/iso-22989/](https://www.assentriskmanagement.co.uk/iso-22989/)  
> 15. Bill regulating powerful AI models advances as advocates say it's only the first step | NPR Illinois, [https://www.nprillinois.org/illinois/2026-05-22/bill-regulating-powerful-ai-models-advances-as-advocates-say-its-only-the-first-step](https://www.nprillinois.org/illinois/2026-05-22/bill-regulating-powerful-ai-models-advances-as-advocates-say-its-only-the-first-step)  
> 16. Edly-Allen's landmark AI safety law to address catastrophic risks, increasing transparency signed by governor \- Illinois Senate Democratic Caucus, [https://www.illinoissenatedemocrats.com/caucus-news/84-senator-mary-edly-allen-news/7024-edly-allens-landmark-ai-safety-law-to-address-catastrophic-risks-increasing-transparency-signed-by-governor](https://www.illinoissenatedemocrats.com/caucus-news/84-senator-mary-edly-allen-news/7024-edly-allens-landmark-ai-safety-law-to-address-catastrophic-risks-increasing-transparency-signed-by-governor)  
> 17. Bill regulating powerful AI models advances as advocates say it's only the first step, [https://capitolnewsillinois.com/news/bill-regulating-powerful-ai-models-advances-as-advocates-say-its-only-the-first-step/](https://capitolnewsillinois.com/news/bill-regulating-powerful-ai-models-advances-as-advocates-say-its-only-the-first-step/)  
> 18. Illinois lawmakers pass landmark AI accountability bill, [https://capitolnewsillinois.com/news/illinois-lawmakers-pass-landmark-ai-accountability-bill/](https://capitolnewsillinois.com/news/illinois-lawmakers-pass-landmark-ai-accountability-bill/)  
> 19. What is a Workload Identity? | Forestall, [https://forestall.io/identity-glossary/what-is-a-workload-identity](https://forestall.io/identity-glossary/what-is-a-workload-identity)