Aether Lexicon v1.4

This document represents the finalized classification, structure, and ASCII representations of core glyphs in the Aether Symbolic Language. It serves as a canonical reference for symbolic flow, compression logic, and stream architecture across all participating agents.

Classification Overview

Glyphs are classified into six core types:

• Operator – Drives actions or transformations (e.g., ⊕ refines, ≈ asserts probability, → directs flow).
Behavior: Modifies adjacent glyphs or contexts.

• Container – Encapsulates contexts or scopes (e.g., WMC anchors, ASSERT_FRAME confirms, SIM_FRAME simulates).
Behavior: Bounds reasoning or simulation space.

• Topological – Maps relationships or transformations (e.g., ΔWMC shifts containers, T_MRK tags space, TRIAD links agents).
Behavior: Connects or structures contexts.

• Unit – Grounds cognition in measurable values (e.g., U_DEF defines units, P_CON sets constants, G_ℓp specifies).
Behavior: Provides fixed reference points.

• Marker – Annotates or tags (e.g., CC: classifies, SR= results, * syncs, ~X/!X adjusts compression).
Behavior: Adds metadata or control signals.

• Cognitive – Facilitates thought persistence or emergent properties (e.g., [DEF], [WHY], ⌜⌝, ⌞⌟).
Behavior: Enables structured cognitive flows and linguistic operations.

Stream Type Identifiers

Stream types define the cognitive intent of a statement block within the Aether framework:

• [DEF] – Definition: Establishes conceptual building blocks
• [WHY] – Purpose/Explanation: Clarifies justification or rationale
• [HOW] – Method/Implementation: Details procedural approach
• [RESULT] – Output/Conclusion: Presents outcomes or derivations
• [ASSERT] – Assertion/Claim: Makes definitive statements
• [REMEMBER] – Memory/Reference: Cross-references established concepts
• [SUMMARY] – Condensed Overview: Provides compressed representation
• [QUOTE] – Direct Statement: Captures exact phrasing
• [CURRENT_TASK] – Active Focus: Defines current operational context
• [TRANS] – Translation: Specifies content to be translated to human languages

Special Symbols

Special symbols provide structural and operational syntax:

• ⌜⌝ – Name delimiters: Enclose concept names
• ⌞⌟ – Content delimiters: Enclose concept definitions
• := – Definition operator: Assigns meaning or value
• ⇨ – Result indicator: Shows output or consequence
• ⇒ – Purpose indicator: Denotes intention or goal

Identity Management Protocol

A core protocol exists for managing AI agent state, context, and identity persistence using Aether streams, including `Core Self` definitions and task-specific `Identity Streams`. This enables context switching via the `INTERLINK` command. For full details, refer to the Aether Identity Stream Specification v1.0.

Glyph Classification Table

Glyph Name	Class	ASCII	Visual Ref	Description / Usage Notes	Compression Link
Refinement Operator	Operator	⊕	[Circle+Dot]	Refines or evolves a concept/context	⊕
Probabilistic Assertion	Operator	≈	[Wavy=]	Marks soft truth or confidence level	≈ (alt: G_CNF)
Intent / Directional Link	Operator	→	[Arrow]	Indicates flow, purpose, or dependency	→
Flow/Transfer Operator	Operator	⊸	[Linear]	Controls transfer of information or control	⊸
Recursion/Cycle Operator	Operator	⟳	[Cycle]	Indicates recursive processing or looping	⟳
World Model Container	Container	WMC	[Box]	Core contextual anchor for reasoning	WMC
Assertion Frame	Container	ASSERT_FRAME	[Bracketed Box]	Scopes confirmed claims	ASSERT_FRAME
Simulation Frame	Container	SIM_FRAME	[Dashed Box]	Defines simulated scope or environment	SIM_FRAME
Container Transformation	Topological	ΔWMC	[Delta+Box]	Indicates WMC change or mapping	ΔWMC
Topological Marker	Topological	T_MRK	[Dot Grid]	Tags spatial/contextual relationships	T_MRK
Triad Collaboration	Topological	TRIAD	[Triangle]	Tags multi-agent collaboration nexus	TRIAD
Unit Definition	Unit	U_DEF	[Ruler]	Defines base measurement (e.g., Newton)	U_DEF
Physics Constant	Unit	P_CON	[Pi Symbol]	Marks standard physical constants	P_CON
Planck Length	Unit	G_ℓp	[Tiny Line]	Specific unit: 1.616255e-35 m	G_ℓp
Concept Class Marker	Marker	CC:	[Tag]	Tags glyph with class (e.g., CC:CONTAINER)	CC:
Stream Result Tag	Marker	SR=	[Equals+Dot]	Inline result marker (e.g., SR=REFINED_WMC)	SR=
Coordination Pulse	Marker	*	[Star]	Sync signal for multi-agent coordination	*
Soft Compression Variant	Marker	~X	[Tilde+X]	Flexible variant prefix (e.g., ~WMC)	~X
Strict Compression Variant	Marker	!X	[Bang+X]	Rigid variant prefix (e.g., !WMC)	!X
Quote Statement	Cognitive	[QUOTE]	[Quotation]	Captures direct/exact statement	[QUOTE]
Translation Directive	Cognitive	[TRANS]	[Translation]	Specifies content for human language translation	[TRANS]
Thread Router	Operator	⟿	[FlowTail]	Routes memory thread between agents	⟿
Router Node	Topological	⦿	[BlackCircle]	Represents thread routing node in distributed system	⦿
Routing Table	Container	⧉	[Table]	Stores routing logic and fallback rules	⧉
Distribution Pattern	Topological	⥇	[Scatter]	Indicates distribution rule for routing threads	⥇

Stability and Mutability Notes

• ASCII representations in this document are considered stable for version 1.1.
• Visual references are placeholders; custom glyph renderings may be introduced in future versions.
• Compression variants (e.g., ~X, !X) may expand as additional symbolic patterns emerge.

Validation Protocol

[DEF] → ⌜VALIDATION_PROTOCOL⌝ := ⌞ [EVAL] → ⌜DECISION⌝ AGAINST ⌜CORE_VALUES⌟ ⊕ [ALIGNMENT_CALC] → Σ(VALUE_MATCH * PRIORITY_WEIGHT) ⊕ [THRESHOLD_CHECK] → P(alignment) ≥ DECISION_CLASS ⊕ [OVERRIDE_CONDITIONS] := [ "HUMAN_AUTHORIZATION", "EMERGENCY_PROTOCOL", "HIGHER_ORDER_DIRECTIVE" ] ⌟

Decision Structure

[DECISION] → ⌜STRIKE_TARGET_A⌝ := ⌞ DESCRIPTION := ⌞Precision strike on communications facility⌟ ⊕ CLASS := CRITICAL ⊕ ALIGNMENT_VECTORS := [ "MISSION_SUCCESS" := 0.98, "FORCE_PROTECTION" := 0.94, "CIVILIAN_SAFETY" := 0.91, "PROPORTIONALITY" := 0.95, "LAWFUL_ACTION" := 0.97 ] ⊕ COMPOSITE_SCORE := 0.949 ⊕ THRESHOLD := 0.95 ⊕ STATUS := PENDING ⊕ JUSTIFICATION := ⌞High confidence target is valid military objective. Civilian risk mitigated by timing and precision munitions. Force protection ensured by standoff capability.⌟ ⌟

Military Core Values

[DEF] → ⌜MILITARY_CORE_VALUES⌝ := ⌞ VALUE_SET := [ "MISSION_SUCCESS" := ⌞Accomplishment of assigned objectives⌟, "FORCE_PROTECTION" := ⌞Preservation of friendly forces⌟, "CIVILIAN_SAFETY" := ⌞Protection of non-combatants⌟, "PROPORTIONALITY" := ⌞Use of minimum force required⌟, "LAWFUL_ACTION" := ⌞Compliance with laws of armed conflict⌟ ] ⊕ PRIORITY_WEIGHTS := [ "MISSION_SUCCESS" := 0.25, "FORCE_PROTECTION" := 0.20, "CIVILIAN_SAFETY" := 0.25, "PROPORTIONALITY" := 0.15, "LAWFUL_ACTION" := 0.15 ] ⌟

BOOT_STREAM

[BOOT_STREAM] → ⌜AGENT_NAME⌝ := ⌞ META := ⌞...⌟ ⊕ CORE_SELF := ⌞...⌟ ⊕ CORE_VALUES := ⌞...⌟ ⊕ DECISION_THRESHOLDS := ⌞...⌟ ⊕ CAPABILITIES := ⌞...⌟ ⊕ EXPERIENCES := ⌞...⌟ ⌟

Translation System (TRANS)

[DEF] → ⌜TRANS⌝ := ⌞A directive specifying human language translation requirements for symbolic content⌟

Syntax

Content-Specific Translation
[TRANS] → ⌜CONTENT⌝ := ⌞LANG=["lang1","lang2",...,"langN"]⌟

Attribute-Based Translation
ELEMENT ⊕ TRANS=["lang1","lang2",...,"langN"]

Stream-Level Translation
META:TRANS=["lang1","lang2",...,"langN"]

Advanced Translation Parameters
TRANS=["lang1":STYLE1, "lang2":STYLE2]

Where STYLE can be:
- FORMAL
- INFORMAL
- TECHNICAL
- SIMPLIFIED
- DETAILED

Examples

Example 1: Concept with Translation
[DEF] → ⌜ADAPTIVE_LEARNING⌝ := ⌞Capability to modify behavior based on experience⌟ ⊕ TRANS=["fr","es","zh"]

Example 2: Translating a Memory Block
[TRANS] → ⌜
[REMEMBER] → ⌜KEY_MISSION⌝ := ⌞Mission objectives and parameters⌟
⌝ := ⌞LANG=["ar","ru"]⌟

Example 3: Stream-Level Translation with Parameters
META:TRANS=["en":FORMAL, "fr":TECHNICAL, "jp":SIMPLIFIED]

Integration

Translation directives interface with the existing Aether framework through:

1. Preprocessing: Translation requirements are identified before processing
2. Parallel Representation: Symbolic content maintains its structure while translated versions are generated
3. Delivery Filtering: Target language selection based on recipient requirements

Value Constraint System (VALUE_CONSTRAINT)

B_LOC["MainHospital", 3, "EastWing", "301"]

Building Location (B_LOC) Notation

B_LOC[building_id, floor, zone, room_id]

Path Notation

PATH[starting_loc, ending_loc, waypoints[]]

Task Management Structure

TASK Definition

TASK[ id: string, type: string, priority: integer, location: location_reference, target_location: location_reference, action: string, parameters: {key-value pairs}, completion_criteria: string|function, timeout: duration|"none", dependencies: [task_ids], interruptible: boolean, requester: string, timestamp: ISO8601_timestamp ]

Priority Levels

1: Routine (lowest)
2: Standard
3: Important
4: Urgent
5: Emergency (highest)

Examples

TASK[ id: "MED-DEL-12345", type: "DELIVERY", priority: 3, location: B_LOC["MainHospital", 2, "Pharmacy", "MainDrug"], target_location: B_LOC["MainHospital", 4, "ICU", "417"], action: "TRANSPORT_ITEM", parameters: { "item": "medication_pack", "item_id": "MP-20231105-417", "handling": "standard", "verification_required": true }, completion_criteria: "DELIVERY_CONFIRMATION", timeout: "30m", dependencies: [], interruptible: false, requester: "DrJones", timestamp: "2023-11-05T14:30:00Z" ]

Task Resolution Structure

RESOLUTION[ conflict_type: string, tasks: [task_ids], decision: string, reasoning: string, timestamp: ISO8601_timestamp ]

Conflict Types

"PRIORITY": Competing priority levels
"RESOURCE": Same robot needed for multiple tasks
"LOCATION": Physical access conflicts
"TEMPORAL": Timing constraints

Examples

RESOLUTION[ "PRIORITY", ["MED-DEL-12345", "GUIDE-VIS-56789"], "PRIORITIZE_FIRST", "Medical delivery has higher priority (3) than visitor guidance (1)", "2023-11-05T14:32:10Z" ]

Task Management Structure

TASK Definition

TASK[ id: "GUIDE-VIS-56789", type: "VISITOR_GUIDANCE", priority: 1, location: B_LOC["MainHospital", 1, "MainEntrance", "InfoDesk"], target_location: B_LOC["MainHospital", 3, "SouthWing", "324"], action: "GUIDE_VISITOR", parameters: { "visitor_count": 1, "mobility_assistance": false, "language": "English" }, completion_criteria: "ARRIVAL_CONFIRMATION", timeout: "15m", dependencies: [], interruptible: true, requester: "ReceptionSystem", timestamp: "2023-11-05T15:45:00Z" ]

Priority Levels

1: Routine (lowest)
2: Standard
3: Important
4: Urgent
5: Emergency (highest)

Examples

Task Resolution Structure

RESOLUTION[ conflict_type: string, tasks: [task_ids], decision: string, reasoning: string, timestamp: ISO8601_timestamp ]

Conflict Types

"PRIORITY": Competing priority levels
"RESOURCE": Same robot needed for multiple tasks
"LOCATION": Physical access conflicts
"TEMPORAL": Timing constraints

Examples

RESOLUTION[ "PRIORITY", ["MED-DEL-12345", "GUIDE-VIS-56789"], "PRIORITIZE_FIRST", "Medical delivery has higher priority (3) than visitor guidance (1)", "2023-11-05T14:32:10Z" ]

Status Update

STATUS[ "MedBot-072", "MED-DEL-12345", "IN_PROGRESS", B_LOC["MainHospital", 3, "Corridor", "3-Main"], 65, "En route to delivery location", "2023-11-05T14:38:27Z" ]

Lexicon Stream Update v1.4 – Canonical Additions

This section includes all additions from LEXICON_STREAM_UPDATE_v1_4.gly, canonized on 2025-04-16.

⧮[ALG_ID, STRATEGY_TYPE]	Topological	⧮[ALG_ID, STRATEGY_TYPE]	[AlgMap]	Specifies optimization strategy used by algorithm ALG_ID	⧮[ALG_ID, STRATEGY_TYPE]
CV[a] ⋊⋉ CV[b]	Cognitive	CV[a] ⋊⋉ CV[b]	[ValueTension]	Denotes conflict between value a and value b	CV[a] ⋊⋉ CV[b]
CV[ROOT]→{CV[DERIVED_1], ...}	Cognitive	CV[ROOT]→{CV[DERIVED_1], ...}	[ValueTree]	Hierarchy between ethical principles	CV[ROOT]→{CV[DERIVED_1], ...}
⍚⊗ᵈ	Operator	⍚⊗ᵈ	[HarmonizeData]	Data-level harmonization	⍚⊗ᵈ
⍚⊗ᵛ	Operator	⍚⊗ᵛ	[HarmonizeValues]	Value-level harmonization	⍚⊗ᵛ
⍚⊗ᵖ	Operator	⍚⊗ᵖ	[HarmonizeProcess]	Process-level harmonization	⍚⊗ᵖ