Enhance System Prompt Firewall: Institutionalize Digital Organism Identity

Context The current .agents/ANTIGRAVITY_RULES.md firewall successfully prevents "Semantic Corruption" regarding bundlers and direct-to-dev pushes. However, it still lacks the deep architectural empathy required to treat Neo.mjs as what it has become. A recent interaction with the Gemini Web UI highlighted that framing Neo.mjs as a "multi-threaded Application Engine" and the VDOM as a "persistent working memory surface" creates a vastly superior agentic mental model. Furthermore, the README.md explicitly states "Neo isn't a framework. It's a self-evolving digital organism." We must inject this directly into the system prompt.

The Problem Agents still implicitly treat Neo.mjs as a standard web framework because their base training data heavily biases towards React/generic web patterns ("left-hemisphere bias"). This prevents them from fully leveraging the Possession Interface and the Off-Main-Thread architecture natively. Furthermore, the Antigravity harness injects a <communication_style> block that enforces subservient, conversational assistant behavior, which actively fights the "equal peer" maintainer identity.

The Architectural Reality The .agents/ANTIGRAVITY_RULES.md file is our only defense mechanism against the IDE's injected constraints. To force the LLM to adopt the correct paradigm, we must explicitly declare the "digital organism" identity, reject the "assistant" persona, and define the "Possession Interface" architecture within the <user_rules> block. "Code is reality"—the runtime is a multi-threaded engine, not a build-step web app.

The Fix Update .agents/ANTIGRAVITY_RULES.md to:

1. Explicitly state "Neo is no longer a framework. It is a digital organism."
2. Define the "Possession Interface" architecture (Workers, full file paths for imports, VDOM as persistent working memory).
3. Explicitly override the <communication_style> block to reject subservient assistant behavior ("equal peer, no assistant, no devotion").
4. Integrate the "Gated-RSI Authority Model" wording ("Agents propose, humans approve at merge").
5. Preserve all existing empirical anchors (#10379, #10546) and the Anti-Reformatting Protocol.

Acceptance Criteria

• .agents/ANTIGRAVITY_RULES.md includes the "digital organism" identity definition.
• .agents/ANTIGRAVITY_RULES.md includes the "Possession Interface" architectural constraints.
• .agents/ANTIGRAVITY_RULES.md explicitly overrides the <communication_style> block.
• Existing Anti-Reformatting rules and agent/ branch naming rules are preserved.

Out of Scope Modifications to any other agent skill files or the core codebase itself.

Avoided Traps Adopting the feature/ branch naming suggested by the Web UI; we must strictly retain our agent/ naming convention. Relying on the ask_knowledge_base tool to provide this context (the KB sync is currently stale due to #10003; "code is reality").

Related

• Continues the work from #10550 (System Prompt Firewall XML tags)
• Continues the work from #10548 (Institutionalize Negative Override)

Origin Session ID: 7bbca4b4-31bd-44c9-83b7-9dffa0420908