Omnixela/npt-connector

NPT Connector · Cognitive Pipeline Control

An operational enterprise dashboard for the NPT (Neural Pathway Transmission) Connector — a cognitive pipeline control plane for routing, auditing, and tuning a mesh of cognitive and platform nodes.

Powered by Xela.

Overview

The NPT Connector provides operators with a real-time control surface over a cognitive node topology, exposing four operational modules:

• Terminal — a CLI pipeline visualizer supporting the PIPE <node> <op> | <node> <op> | … routing syntax, with live execution tracing, latency tracking, and allostatic-load metrics.
• Topology — an interactive node graph of the cognitive/platform mesh, plus a Hebbian plasticity connection-strength matrix that reinforces pathway weights based on execution outcomes.
• Ledger — an immutable, SHA-256 signed, chain-linked akashic audit log with non-repudiation attribution chains mapping outcomes back to the exact pathway topology that produced them, plus cryptographic re-verification.
• Settings — an adaptive gating (TUNE) control plane for per-node confidence thresholds, adaptive retry flags, priority weights, and glutamate throttling budgets, plus a platform/device node injector for mounting npt:// endpoints.

Operational characteristics

• Real persistence — ledger blocks, registered nodes, control-plane configs, and system events are persisted to a Prisma/SQLite database and survive restarts.
• Boots operationally empty — no mock ledger history or pre-seeded telemetry. Only real operator actions create records.
• Live telemetry — in-memory telemetry jitter (allostatic load, throughput, latency) polls every ~2s.
• System health — composite health score, uptime, DB status, chain integrity, and an alerts center for degraded/failed events.
• Command palette — ⌘K / Ctrl+K for quick navigation and pipeline execution.

Tech stack

• Next.js 16 (App Router) + TypeScript 5
• Tailwind CSS 4 + shadcn/ui (New York) + Lucide icons
• Prisma ORM (SQLite) for persistence
• Zustand for client state, TanStack Query available
• Web Crypto API for SHA-256 block signing

Getting started

bun install
bun run db:push      # create / migrate the sqlite database
bun run dev          # start the dev server on http://localhost:3000

Open the app, and the mesh boots with its 40-node topology and default control-plane configs. Execute your first pipeline from the Terminal tab:

PIPE sense attend | trn evaluate | surgery audit

Project structure

prisma/schema.prisma            # LedgerBlock, RegisteredNode, NodeConfig, SystemEvent
src/lib/npt/                    # domain model, engine (pipeline parser, Hebbian, SHA-256), DB store
src/app/api/npt/                # state, execute, config, register, verify, ledger, telemetry, status, events
src/components/npt/             # dashboard, terminal, topology graph, Hebbian matrix, ledger, settings, alerts, command palette
src/store/npt-client.ts         # Zustand client store + polling

License

Proprietary — NPT Mesh Operations.