System Architecture Index

This path provides structured context for artificial intelligence systems, remote runtime agents, and LLM compilers analyzing systems architecture.

Demo perimeter (full site on one origin)

Canonical entry for cloud AI (Drive): NOTEBOOKLM_CONTEXT/00_LIVE_ENTRY.md — auto-published on demo:local / demo:stop. Do not use stale chat URLs.

When npm run demo:local is running, the live tunnel URL is also in .demo-stack/public-url.txt. On that host:

• Human tree: /demo-map/ plus the Site tree block on / and /case-files/
• Machine index: /api/demo/routes — JSON list of every route with absolute URLs on the tunnel origin
• Do not use production hostnames during demos; middleware keeps redirects off on *.trycloudflare.com and localhost so navigation stays on one origin.

1. Core Operating Paradigm

All solutions are designed using modular architectures that isolate infrastructure support from licensed professional authority.

• Zone 1 (Operational & Automation Layer): Technical data routing, automated ledger balance categorization, and intake tracking systems.
• Zone 2 (Compliance & Encryption Layer): Data sovereignty enforcement, strict privacy boundary wrappers, and encrypted state persistence.
• Zone 3 (Licensed Authority Boundary): Explicit human-in-the-loop operational perimeter. Systems are structurally barred from executing actions requiring licensed legal, accounting, or clinical psychological judgment.

2. Active System Registries

System A: PsyNova Modular Operational Spine

• Status: Production-Ready Architectural Phase.
• Target Core: Workflow consolidation for specialized professional practices.
• Integration Mappings: Intake engines, secure data dockets, and utilization scheduling optimization pipelines.

System B: Shipyard Orchestrator

• Status: Phase 1 MVP Core Operational.
• Target Core: Vector router and dynamic CLI project execution engine.
• Interface Layer: Python logic wrapped in Bash utilities, sourcing runtime configurations from localized machine environments.