@theemystikcove/nexis-os-core

Alpha 0.1.0-alpha.0 — command-core surface only. This published package ships only the provider-neutral command-core: a transport-agnostic command pipeline and a two-axis permission gate. It performs no I/O and bundles no provider SDK. Both entry points resolve to command-core:

const cc   = require("@theemystikcove/nexis-os-core");              // "."
const same = require("@theemystikcove/nexis-os-core/command-core"); // "./command-core"

The broader NEXIS AI.OS overview below is internal context and is not included in this package.

NEXIS AI.OS — NEXIS_AI_CORE

Thee Mystik Cove runs on NEXIS AI.OS.

NEXIS AI.OS is the central intelligence operating system of Thee Mystik Cove, designed to unify governance, knowledge, agents, workflows, and applications into one structured digital environment.

This directory is the OS Core — the hub from which all branches, apps, and agents inherit their intelligence.

What This Is

NEXIS AI.OS is not a chatbot. It is not a toolset. It is the operating system that governs how all AI agents, applications, and workflows behave across the entire Mystik ecosystem.

Every app inherits from this core. Every agent references it. Every output is anchored to it.

OS Layer Model

| Layer | Folder | Purpose | |-------|--------|---------| | OS Core Identity | 00_CORE_IDENTITY/ | Defines what NEXIS is, how it governs, and how everything is structured | | OS Canon Library | 01_CANON_LIBRARY/ | Approved reference material by domain — the knowledge the OS draws from | | OS Agent Registry | 02_AGENT_REGISTRY/ | All registered intelligence agents and their contracts | | OS Templates | 03_TEMPLATES/ | Reusable templates for canon docs, agents, apps, and outputs | | OS Connectors | 04_CONNECTORS/ | Integration logic for Notion, Supabase, Google Docs, and app routing | | OS UI System | 05_UI_SYSTEM/ | Design standards and UX principles for all NEXIS-powered interfaces | | OS Identity Layer | identity/ | Universal MYSK-ID member identity — profiles, overlays, schemas, companion context, scripts |

The Foundational Architecture

The single most important document in this system:

📄 NEXIS_OS_FOUNDATIONAL_ARCHITECTURE_V1.md

This is the consolidated record of all 6 OS components. Read this first.

Core Identity Files

| File | OS Layer | |------|---------| | NEXIS_OS_CORE_DEFINITION_V1.md | OS Identity Layer | | NEXIS_OS_GOVERNANCE_HIERARCHY_V1.md | OS Governance Layer | | NEXIS_OS_NAMING_PROTOCOL_V1.md | OS Indexing Layer | | NEXIS_OS_CANON_REFERENCE_PROTOCOL_V1.md | OS Memory Linking Layer | | NEXIS_OS_AGENT_ARCHITECTURE_V1.md | OS Execution Layer | | NEXIS_OS_INTEGRATION_FRAMEWORK_V1.md | OS Infrastructure Layer | | NEXIS_OS_AIOS_DEFINITION_V1.md | OS Operating System Layer |

Quick Start — For Agents

When an AI agent is activated within NEXIS, it must:

1. Reference NEXIS_OS_GOVERNANCE_HIERARCHY_V1.md — confirm tier authority
2. Reference NEXIS_OS_AGENT_ARCHITECTURE_V1.md — confirm role and constraints
3. Pull relevant canon from 01_CANON_LIBRARY/ — confirm knowledge sources
4. Attach Canon References block to all outputs — confirm alignment
5. Classify all outputs — Type / Sensitivity / Visibility

Quick Start — For Apps

When a new application is onboarded to NEXIS:

1. Review NEXIS_OS_INTEGRATION_FRAMEWORK_V1.md — define the 4-layer connection
2. Register any new agents in 02_AGENT_REGISTRY/
3. Use templates from 03_TEMPLATES/ — do not invent new formats
4. Store all outputs to Notion / Supabase per 04_CONNECTORS/notion-sync-logic.md
5. Follow naming convention in NEXIS_OS_NAMING_PROTOCOL_V1.md
6. Create a .nexis/ directory in the app — see identity/README.md for the required files

Hub-and-Spoke Principle

         🧿 NEXIS AI.OS CORE
        /    |    |    |    \
   Academy Harbor Studios Market Ops

NEXIS Core is the hub. Every branch is a spoke. Every app connects back to the hub. Nothing lives as an orphaned system.

NEXIS AI.OS — Built with intention. Governed with sovereignty.