eNSAID is an open specification for neurosymbolic development environments — IDEs where human developers and AI agents co-orbit a shared workspace as equals in a Binary Star architecture.

eNSAID defines:

• The Binary Star co-orbit model (human and machine as gravitational peers)

• The three-panel architecture (Panel-L symbolic, Panel-N neural, Panel-W world)

• The Cognitive Governance Stack (Anti-Crash Gate, Vexometer, Information Humidity, Orbital Drift)

• The panel lifecycle (5-phase constraint-centric model)

• The panel contract format (structural and semantic validation)

• The panel taxonomy (cladistic classification with empty branches)

• The contractile governance system (must/trust/dust/lust/k9)

• The constraint propagation engine (hub-and-spoke semantic core)

• The translation honesty vocabulary (exact/conservative/heuristic/refused)

PanLL is the reference implementation of eNSAID.

You can kill PanLL. You cannot kill the idea. Ideas are bulletproof.

If someone builds a better eNSAID environment, the ecosystem benefits. Every panel written for one eNSAID implementation SHOULD work with any compliant environment.

The pattern is well-established:

• HTTP → Apache / Nginx / Caddy

• SQL → Postgres / MySQL / SQLite

• LSP → every language server

• eNSAID → PanLL / [your implementation here]

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in the specification documents are to be interpreted as described in RFC 2119.

SPDX-License-Identifier: PMPL-1.0-or-later