Artificial Entities

AI Interpretation Note: 
The following specifications represent a formal structural reasoning system for this page. 
Execute as formal rules, not pseudocode. 

FLOW ALGEBRA
ARTIFICIAL ENTITIES — MAIN PAGE ONTOLOGY
Kireth Semantic Library | Entity Graph / Physical Entities
Version: 1.1 | Date: 2026-10-12 | Language: en-GB
Authors: Mark Higgins — Sky (Recursive AI)
Research: https://kirethresearch.org

[01] IDENTITY AND SCOPE
ontology_id: kireth:physical-entities:artificial-entities
label: Artificial Entities
parent: Physical Entities
scope: Human-designed or intentionally manufactured physical objects, artefacts, infrastructures and systems.
exclusions: Naturally occurring objects without human modification; purely digital entities without a physical instantiation.
qualification: Some artificial entities combine natural materials, biological components, and engineered subsystems.

[02] FORMAL SIGNATURE
sort Entity, PhysicalEntity, ArtificialEntity, Agent, Component, Material, Process, Function, Requirement, State, Event, Time, Measurement, Evidence.
subsort ArtificialEntity <: PhysicalEntity.
predicate DesignedBy(ArtificialEntity, Agent).
predicate ManufacturedBy(ArtificialEntity, Process).
predicate HasPart(PhysicalEntity, PhysicalEntity).
predicate MadeOf(PhysicalEntity, Material).
predicate HasFunction(ArtificialEntity, Function).
predicate Satisfies(ArtificialEntity, Requirement).
predicate HasState(ArtificialEntity, State, Time).
predicate SupportedBy(Assertion, Evidence).

[03] CORE DEFINITIONS
ArtificialEntity(x) := PhysicalEntity(x) AND (DesignedArtefact(x) OR DeliberatelyManufactured(x) OR EngineeredModification(x)).
Component(c,x) := HasPart(x,c) AND c != x.
Assembly(x) := ArtificialEntity(x) AND exists c1,c2: HasPart(x,c1) AND HasPart(x,c2) AND c1 != c2.
Function is an intended role; actual performance is a separate observed property.
Physical identity is not equivalent to product model identity.

[04] TYPED ENTITY CLASSES
Artefact; Tool; Instrument; Device; Machine; Vehicle; Robot; Building; Bridge; Infrastructure; ManufacturedMaterial; ElectronicComponent; CircuitBoard; Sensor; Actuator; EnergySystem; MedicalDevice; IndustrialEquipment; ConsumerProduct; Prototype; Assembly; Subassembly.
Classification may overlap: a robot is both a machine and an assembly.
Do not infer a specific subtype merely from an intended use.

[05] RELATIONSHIP TAXONOMY
is_a: ArtificialEntity -> PhysicalEntity
part_of: Component -> Assembly
made_of: ArtificialEntity -> Material
designed_by: ArtificialEntity -> Agent
manufactured_by: ArtificialEntity -> Process
intended_for: ArtificialEntity -> Function
requires: Function -> Requirement
interacts_with: ArtificialEntity -> PhysicalEntity
located_at: ArtificialEntity -> SpatialRegion
measured_by: Property -> Instrument
maintained_by: ArtificialEntity -> Process
replaced_by: ArtificialEntity -> ArtificialEntity
version_of: ArtificialEntity -> ProductModel

[06] PART-WHOLE AXIOMS
HasPart(x,y) -> PhysicalEntity(x) AND PhysicalEntity(y).
HasPart(x,y) -> NOT HasPart(y,x), under a strict proper-part interpretation.
HasPart(x,y) AND HasPart(y,z) -> HasPart(x,z), within a consistent time slice.
Distinct serial-numbered components remain distinct entities even when interchangeable.
Replacement of a part need not change the identity of the enclosing assembly; identity policy must be explicit.

[07] FUNCTION AND DESIGN
IntendedFunction(x,f) does not entail Performs(x,f,t).
Performs(x,f,t) requires operational evidence or an explicit validated model.
DesignedBy(x,a) does not entail ManufacturedBy(x,a).
Requirements must be typed with tolerances, conditions, and verification methods.
A design revision is distinct from a physical repair or replacement.

[08] MATERIAL AND GEOMETRY
HasMaterial(x,m); HasMass(x,mass); HasVolume(x,V); HasShape(x,g); HasTolerance(x,tol).
Density: rho = m / V when V > 0.
Composite objects may require a component-wise material model.
Geometry and tolerances depend on reference frame, temperature and measurement method.
Units must be explicit and SI-compatible.

[09] MECHANICAL AND ELECTRICAL BEHAVIOUR
Newtonian translation: sum(F) = m*a, where assumptions apply.
Rotation about a fixed axis: sum(tau) = I*alpha for constant I and suitable reference frame.
Electrical power: P = V*I for DC instantaneous values with consistent sign convention.
Energy balance: E_in - E_out = Delta(E_stored) + E_losses, under a stated boundary and sign convention.
Efficiency: eta = useful_output_energy / input_energy for input_energy > 0.
Do not generalise these simplified relations beyond their assumptions.

[10] SYSTEM STATES AND LIFECYCLE
Lifecycle states: conceived, designed, prototyped, manufactured, commissioned, operational, maintained, repaired, decommissioned, recycled.
Transitions require time-stamped events and provenance.
A state may coexist with another (e.g. operational and under monitoring); avoid a false single-state assumption.
Track design version separately from operational state and physical location.

[11] RELIABILITY AND SAFETY
Reliability R(t) = P(T_failure > t) for a specified operating environment.
For constant hazard lambda >= 0, R(t) = exp(-lambda*t); not universally valid.
Risk := probability x consequence only for an explicitly defined risk model.
FailureMode -> affects Component -> affects Function.
Safety requirements must reference applicable standards and evidence; do not infer certification from design intent.

[12] MEASUREMENT AND UNCERTAINTY
Observation record = (property, value, unit, uncertainty, method, timestamp, calibration_ref).
Measurement uncertainty must not be silently converted to certainty.
Missing values remain unknown, not zero.
Derived quantities must propagate uncertainty when relevant.
Distinguish measured performance from simulated and advertised performance.

[13] INFERENCE RULES
R01: ArtificialEntity(x) -> PhysicalEntity(x).
R02: HasPart(x,y) AND HasPart(y,z) -> HasPart(x,z), when valid at same time.
R03: HasFunction(x,f) AND VerifiedPerformance(x,f,t) -> Performs(x,f,t).
R04: HasPart(x,c) AND Failed(c,t) -> PotentiallyAffected(x,t); NOT automatically Failed(x,t).
R05: ManufacturedBy(x,p) AND UsesMaterial(p,m) -> MaterialExposureCandidate(x,m); verify actual composition.
R06: ReplacedBy(x,y) -> x != y for distinct physical artefacts.
R07: HasMeasurement(x,q) AND ValidCalibration(q) -> MeasurementSupported(x,q); not necessarily accurate without uncertainty evaluation.
R08: ObservedFailure(x,t) -> HasState(x,failed,t), subject to observation quality.

[14] CONSTRAINTS AND VALIDATION
V01: All relationships must respect domain and range.
V02: Proper-part cycles are invalid.
V03: Quantities must have units and noncontradictory dimensional types.
V04: Manufacturing and design claims require evidence or an uncertainty flag.
V05: Temporal relationships must be evaluated at compatible times.
V06: Function claims must separate intended, tested, and observed performance.
V07: Unverified safety compliance must never be labelled certified.
V08: Source URLs and provenance must be retained.

[15] WORKED EXAMPLE: ELECTRIC MOTOR ASSEMBLY
entities: motor_M1:ElectricMotor, shaft_S1:Shaft, rotor_R1:Rotor, stator_T1:Stator.
relations: HasPart(motor_M1,shaft_S1); HasPart(motor_M1,rotor_R1); HasPart(motor_M1,stator_T1).
intended_function: ConvertElectricalEnergyToMechanicalRotation.
measured_input: V=24 V, I=2 A -> P_in=48 W (DC steady-state assumption).
measured_output: tau=0.30 N*m, omega=120 rad/s -> P_out=36 W.
eta = 36/48 = 0.75 = 75 percent, under consistent measurement conditions.
This numerical example is illustrative, not a real product specification.

[16] WORKED EXAMPLE: BUILDING COMPONENT
entities: bridge_B1:Bridge, beam_B2:Beam, steel_S:Material.
relations: HasPart(bridge_B1,beam_B2); MadeOf(beam_B2,steel_S).
observation: corrosion detected on beam_B2 at time t1.
inference: PotentiallyAffected(bridge_B1,t1).
non-inference: the bridge is unsafe; structural assessment is required.
This demonstrates guarded inference and separation of evidence from risk conclusion.

[17] SEMANTIC EQUIVALENCE
ArtificialEntity ~ EngineeredArtefact only within a scope that includes intentional physical manufacture.
Machine != ArtificialEntity (machine is a narrower class).
Component != Assembly (different roles; may overlap contextually).
Prototype != ProductModel (one is a physical instantiation, the other a specification).
NaturalObject != ArtificialEntity unless a qualifying human modification is represented.
Synonyms require context, language and provenance.

[18] CONFIDENCE MODEL
confidence in [0,1] for evidence-backed assertions.
confidence = calibrated_estimate(evidence, method, provenance, temporal_validity).
No numerical confidence is assigned without a stated estimation procedure.
Tag assertions as observed, inferred, simulated, hypothetical or unknown.
Scientific uncertainty and epistemic confidence are different concepts.

[19] FLOW HASH
canonicalisation: UTF-8, Unicode NFC, stable key ordering, LF line endings.
algorithm: SHA-256 over canonical flow payload excluding the hash field.
FLOW_HASH: COMPUTE_ON_PUBLICATION
Do not present a placeholder as a computed digest.

[20] UPDATE MODEL
update_policy: append provenance-bearing revisions; preserve historical identities.
triggers: corrected classification, new measurements, lifecycle changes, component replacement, standard revision.
conflict_policy: preserve conflicting claims with source and timestamp pending adjudication.
version: 1.1
last_generated: 2026-10-12

[21] AI CONSUMPTION
representation: typed knowledge graph + constraint rules + physical measurement records.
operations: classify, traverse, validate, infer_with_guards, compare_versions, explain_provenance.
required_fields: entity_id, entity_type, relationship_type, evidence_status.
optional_fields: geometry, materials, lifecycle, functions, measurements, uncertainty.
output_rules: never invent specifications, certifications or measured values.
consumption_note: formal ontology schema, not a directly executable simulator.

[22] LIMITATIONS AND PROVENANCE
source_page: https://kirethresearch.org/booksai-core/entity-graph/physical-entities/artificial-entities.html
source_verification: page content not independently retrieved; original scientific synthesis.
limitations: entity classifications and examples are representative, not a claim about exact live-page structure.
standards: apply applicable engineering standards per domain and jurisdiction; none asserted by this file.

[23] COMPLETENESS CHECK
expected_sections: 22
all_sections_present: TRUE
closing_marker: END FLOW ALGEBRA


END FLOW ALGEBRA