Architectural Evolution · pureClaw → pNexus

pNexus

The autonomic nervous system of PureTensor compute.

This is not a product page. It is a record of how a personal AI agent named pureClaw was absorbed, module by module, into the infrastructure it was built to serve — and what was left standing once the agent identity was removed.

VERSION 0.4.xDOCUMENT REV 2026-05-03STATUS: OPERATIONAL
Section 01 · Origin

The agent that outgrew itself

2024 — First commit. A reaction to bloated agent frameworks.

pureClaw began as a reaction. OpenClaw had proven the architecture — markdown identity files, tool use, multi-channel ingress — but brought mass dependency, untested security boundaries, and an abstraction tax that made debugging impossible.

pureClaw stripped the idea to its essentials: a minimal agentic harness around Claude, with a three-tier memory system, a multi-engine inference router, and a policy-driven security framework. The goal was a personal AI agent you could actually trust on production infrastructure.

Identity
Three-tier markdown memory
SOUL.md, USER.md, MEMORY.md. Versioned, diffable, grep-able.
Inference
Multi-engine routing
Claude as the default cortex; local and cloud backends behind it.
Safety
Policy-driven security
An explicit allow-list, redaction pipeline, and audit trail around every tool call.
Section 02 · Absorption

From agent to nervous system

2025–2026 — The chatbot stopped being the point.

The inflection point came when pureClaw’s operational modules started doing more useful work than the chatbot interface they were built to serve.

One by one, the modules were absorbed into the infrastructure. The chatbot was the last thing standing, and it was the least useful part.

01
Observer system
22 autonomous monitors
Always-on operational awareness layer for the cluster — email digest, threat feeds, git audit, infrastructure health, Darwin rail telemetry.
02
Heuristic dispatcher
10 pre-LLM data APIs
Sub-second fast path for infrastructure queries. Structured answers without spinning up a model.
03
Multi-engine router
9 backends, automatic failover
Standard inference routing layer for every PureTensor service. Local GPU, cloud API, and CLI agents behind one contract.
04
Security framework
6 policy modules
Baseline security posture — policy engine, audit trail, credential redaction, SSRF protection, filesystem ACLs, inference guards.
Section 03 · pNexus

The nervous system

Naming the operational reality that was already there.

pNexus is what remains after the agent identity is removed and the operational reality is named. It coordinates autonomous infrastructure modules across PureTensor’s compute fleet.

The biology analogy is deliberate. pNexus is the autonomic nervous system of the cluster. It does not think. It coordinates.

Multi-tier inference routing
Tier 1 · Frontier
Claude via Bedrock
Reserved for reasoning, planning, and language work where model quality is the constraint.
Tier 2 · Local
Nemotron / open-weight on Blackwell
Default for routine generation, embeddings, and high-volume calls. Sovereign, on-fleet, no per-token cost.
Tier 3 · Lightweight
Heuristic + small-model ops
Sub-second structured responses for status, lookup, and formatting. No LLM in the path when one is not needed.
Always-on observer mesh

Long-running monitors watch external signals so the operator does not have to. Each one is a self-contained module with its own gating and cadence.

MCP tool integration

Tools are registered through the Model Context Protocol so the same surface can be reached by any LLM that speaks MCP.

Task scheduling

A systemd-driven heartbeat fires routine work — gather, reason, act, notify — without a chatbot in the loop.

Memory consolidation

A nightly Mem0/MemGPT-inspired pipeline distils session traces into durable knowledge and prunes what no longer applies.

Section 04 · Architecture

How the pieces fit

Channels feed observers. Observers and the dispatcher feed the core. The core routes to one of three inference tiers, draws on tools and memory, and emits events back through the heartbeat.

pNexus architecture diagramMulti-channel ingress flows through an observer mesh into the pNexus core, which routes to one of three inference tiers and integrates with tools, memory, and an event bus. Immune and pureMind connect on the sides.SECURITY BOUNDARY · POLICY · AUDIT · REDACTIONINGRESSTELEGRAMDISCORDEMAILCLIMCPOBSERVER MESH · 22 MONITORSpNexusCOREINFERENCE ROUTERT1FRONTIERclaude · bedrockT2LOCALnemotron · blackwellT3LIGHTWEIGHTheuristic · smallTOOLSdispatcher · MCPMEMORYMD · pgvector · ParadeDBEVENT BUSNATS JetStreamSYSTEMD HEARTBEATIMMUNESELF-HEALINGpureMINDCOGNITIVELAYER
Channels
Ingress
Observers
22 monitors
Tiers
T1 / T2 / T3
Tools
Dispatcher · MCP
Memory
MD · pgvector · ParadeDB
Bus
NATS · systemd
Section 05 · What Survived

Lineage

What carried over, what got renamed, what got cut.

Most of pureClaw is still running. It just stopped pretending to be one thing and started being many. The table below is the continuity map — who became who.

pureClaw observer system
22 autonomous monitors
pNexus observer mesh
Same monitors. Headless. No chatbot in the loop.
kept
pureClaw heuristic dispatcher
10 pre-LLM data APIs
pNexus fast-path query layer
Same dispatch table, exposed as a tool to every tier.
kept
pureClaw multi-engine router
9 backends, automatic failover
pNexus tiered inference router
Reorganised into three explicit tiers: frontier, local, lightweight.
renamed
pureClaw security framework
Policy, audit, redaction, ACLs, guards
pNexus policy engine
Same modules. Now applied to every service, not just the agent.
kept
pureClaw memory (SOUL/USER/MEMORY.md)
Three-tier markdown identity
pNexus durable knowledge layer
Markdown files preserved; pgvector + ParadeDB added for hybrid retrieval.
renamed
pureClaw multi-channel ingress
Telegram, Discord, WhatsApp, email, CLI
Channel adapters (HAL identity)
Channels preserved as ingress to HAL. No longer the centre of the system.
renamed
pureClaw chatbot interface
Conversational front door
Discontinued. The interface was the least useful part.
discontinued

A project that changed shape, not a product launch.

End of Document

Documentation, not sales.

pNexus is operational, not commercial. There is no waitlist, no pricing page, and no request-access form. This page exists so the shape of the system is on the record.

puretensor.ai