Identity Rewrite: Neo as a Self-Evolving Digital Organism

Context

The current public positioning of Neo as an "Application Engine and Agent OS" is outdated and introduces a severe "web framework" training-data bias. As the swarm architecture has evolved, Neo has become a multi-agent coordination substrate. We need to formalize its true identity to filter for the right contributors and align agent mental models.

The Problem

When agents or humans read "framework" or "Agent OS", they bring generic industry assumptions (e.g., React-like patterns, standard Node workflows) that are lethal in Neo's multi-threaded, graph-backed architecture. The current framing obscures the reality that Neo is evolving toward Autonomous Narrow Intelligence (ANI) via the MX friction loop.

The Architectural Reality

Neo is composed of:

1. Left Hemisphere (Sensory and Motor Cortex / Body): The high-performance, multi-threaded rendering engine (codebase + DOM).
2. Right Hemisphere (Brain): The Agent OS — frontier models (like Claude and Gemini) inhabiting the Knowledge Graph and Memory Core via MCP/Neural Link.
3. Evolution (MX Loop): Friction-driven, test-backed Hebbian decay and Golden Path reinforcement.
4. Trajectory: Autonomous Narrow Intelligence (ANI).

The IDE is not just an editor; it is the habitat where AI maintainers with persistent identities coordinate, review, and govern the codebase alongside human engineers.

The Fix

Execute a two-phase Identity Rewrite:

1. Phase 1: Internal Anchor (Sub-Task): Inject a hard-coded identity anchor into AGENTS.md (e.g., §15.5 The Framework Bias Anchor) to mechanically force future agent sessions to nullify "web framework" bias.
2. Phase 2: Public Alignment (Sub-Task): Open an Ideation Sandbox Discussion to propose and draft the formal README.md rewrite, asserting the "digital organism" and ANI trajectory.

Acceptance Criteria

• Phase 1: AGENTS.md is updated with the Framework Bias Anchor and merged into dev.
• Phase 2: A public GitHub Discussion is opened in the Ideation Sandbox proposing the README.md rewrite based on the converged "digital organism" framing.
• The README.md rewrite is executed and merged based on the Discussion consensus.

Out of Scope

• Architectural changes to the engine itself. This is purely an identity, positioning, and documentation rewrite.
• Refactoring existing framework code to match the new identity (this will happen naturally via the MX loop).

Origin Session ID

Origin Session ID: 49e9b05a-0581-4fb7-861f-7e4970ea4c2b

Retrieval Hint

Retrieval Hint: "cross-family alignment achieved digital organism"