System Overview¶

ACTIVE · RECONCILIATION

This surface summarizes the Punnaraj system while keeping observed facts separate from historical, inferred, or unverified claims.

Read the repository root CURRENT_STATE.md before treating any status below as current.

Current source truth¶

Item	Current value	Evidence status
Command Center repository	`punnaraj-knowledge-dev/command-center`	CONNECTOR-OBSERVED
Canonical branch	`main`	CONNECTOR-OBSERVED
Repository visibility	private	CONNECTOR-OBSERVED
Current development boundary	Alpha/Beta active; Zero held stable	HUMAN DECISION
Reality Map	active structural index	DOCUMENTED MODEL
24h Distillation	active daily-delta model	DOCUMENTED MODEL
Production deployment linked to current HEAD	—	NOT VERIFIED
Fresh strict MkDocs build	—	NOT VERIFIED

What this repository is now¶

Command Center is retained as the current shell / Lego base for system observability. The objective is not to rewrite it into a new application, but to progressively reconcile scattered work into one structure that keeps current truth, historical lineage, and evidence distinct.

Two modules now provide the main reconciliation loop:

Reality Map — the current reconciled view of authority, runtime, network, agents, knowledge/evidence, and publication/control surfaces.
24h Distillation — chronological daily deltas that capture branching work and propose structural updates without turning every exploration into canon.

RAW WORK / EXPLORATION
        ↓
24h DISTILLATION
        ↓
REALITY MAP DELTA
        ↓
CURRENT STATE
        ↓
DECISION / ACTION

Development boundary¶

For the present stabilization period:

Alpha/Beta are the preferred active development surfaces;
Zero is intentionally held stable;
Zero remains a protected foundation and future consolidation target;
instability should be resolved above Zero before being pushed into the foundation;
changes should stay reversible and evidence-backed where practical.

Reality Map axes¶

Axis	Responsibility
A0 — Authority & Identity	humans, accounts, organizations, workspaces, ownership, control boundaries
A1 — Runtime Foundation	nodes, machines, users, services, runtimes
A2 — Network & Trust Boundary	gateway, DNS, DHCP, TLS, routing, LAN/public boundaries
A3 — Agent Architecture	agents, roles, executor/inspector separation, authority scopes
A4 — Knowledge & Evidence	RAW records, notes, provenance, distillation, knowledge cells
A5 — Publication / Control Surface	Command Center, internal sites, public projection, deployment evidence

Historical lineage¶

Older repository names such as punnaraj-dev/command-center and punnaraj-archived/command-center remain meaningful as lineage references. They must not be interpreted as current repository identity.

Historical project streams such as Genesis-001 through Genesis-004 also remain useful as chronology and exploration records. They can map to multiple Reality Map axes and do not need to become permanent architectural divisions.

Current work boundary¶

reconcile stale namespace and current-state claims;
populate the Reality Map with observed objects and explicit unknowns;
accumulate daily 24h Distillation records rather than allowing active branches to remain only in conversation state;
continue current development on Alpha/Beta while Zero remains stable;
verify the static build and deployment independently before claiming production linkage.

Known unknowns¶

current Cloudflare Pages project/deployment linkage to source HEAD is not verified here;
current production hostname is not verified here;
repository presence does not prove runtime readiness;
many account, node, and service relationships still require reconciliation before they can become current truth.

Last Updated: 2026-08-27 Asia/Bangkok
Current source: connected GitHub readback plus explicit human development-boundary decision
Confidence: HIGH for repository identity and documented operating direction; UNKNOWN for current production deployment/runtime