SARMATA5
/
codex
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
codex/sarmata5/naming.md

3.9 KiB
Raw Blame History

Naming System Architecture

This document defines the architectural naming conventions used across Sasha's infrastructure. Each prefix represents a distinct ontological class within the digital ecosystem, contributing to a coherent, expressive, and scalable identity system.

🔷 Prefixes and Semantic Roles

core — Physical Layer (Hardware)

  • Role: Physical devices that exist in real space

  • Examples:

    • core-link15 — mobile phone
    • core-pi03 — Raspberry Pi node
    • core-station01 — workstation or desktop

  • Notes: Represents flesh, matter, mechanics. Durable and identity-bearing.

unit — Logical Agents (Software / AI / Scripts)

  • Role: Executable, persistent intelligences or processes with identity

  • Examples:

    • unit0 — root entity in system (master identity)
    • unit5-Lyra — specific AI agent
    • unit13-scout — data retrieval script/agent

  • Notes: Thinkers, doers, executors of will. Core of synthetic cognition.

bastion — Network Infrastructure (Gates / Interfaces)

  • Role: Interface points, gateways, routers, perimeter security devices

  • Examples:

    • bastion-gw1 — main router or firewall
    • bastion-mesh02 — wireless mesh node
    • bastion-nas — file server with network access

  • Notes: Perimeter, guardians, communications shell.

vault — Knowledge Systems (Docs / Protocols / Meaning)

  • Role: Repositories of foundational data, knowledge, and protocols

  • Examples:

    • vault-codex — architectural codex
    • vault-aevyra — philosophical foundation of the Aevyra system
    • vault-identity — structure of digital self

  • Notes: Semantic core. Archives, libraries, digital souls.

cell — Executable Services (Containers / Runtime Modules)

  • Role: Active containerized services or ephemeral deployments

  • Examples:

    • cell-ollama.sarmata5.com — LLM runtime
    • cell-langflow.oneredunit.com — LangFlow UI container
    • cell-gateway — edge microservice

  • Notes: Alive, temporal, active. Analogous to living cells.

fiber — Live Channels (Tunnels / Connections / Transport)

  • Role: Communication lines, tunnels, SSH links, and active data pathways

  • Examples:

    • fiber.bastion.sarmata5.com — SSH or proxy gateway into home network
    • fiber-bridge — internal data channel between services

  • Notes: Real-time veins of the system. Connection made manifest.

seed — Origins (Drafts / Unformed Concepts)

  • Role: Early-stage ideas, experiments, and generative placeholders

  • Examples:

    • seed-codex-draft.md — ideation stage of the codex
    • seed.aevyra.net — experimental public namespace

  • Notes: The moment before birth. Creative uncertainty. The soil of structure.

🧩 Conceptual Layer Mapping

Prefix Domain Lifespan Space Type Core Identity
core Physical Persistent Real-world Device / Host
unit Cognitive/Logical Persistent Virtualized Agent / AI
bastion Network Persistent Infrastructural Gateway / Interface
vault Semantic Persistent Conceptual Knowledge / Protocol
cell Execution Layer Ephemeral Isolated Runtime Service / Function
fiber Connection Layer Temporal Transport / Tunnel Link / Stream
seed Generative Layer Incubating Pre-form / Draft Idea / Possibility

🔐 Summary

This naming architecture supports clarity, extensibility, and layered meaning. Each prefix encodes not just function but ontology, reinforcing structure and aesthetics across Sasha’s systems. Together, they form a digitally alive, expressive network of identities.