ABL / Public architecture · dated evidence
Documentation
Nodes, by role
This is a public map of compute and service responsibilities. A role is not a physical-machine count: several roles can share a host. The map omits private names, addresses, ports and operational destinations.
Review scope: retained project receipts and planning evidence, reviewed November 5. No private-service probe was performed for this website update. The public site check measures the website only.
Primary services
Migration, recovery, admission and task receipts.
Desktop controls
Guarded transports and retained compatibility helpers.
Memory and archive
Canonical records, vector index and capture lifecycle.
Specialist resources
Availability is not inferred from an old inventory.
Primary services
Late-October migration evidence places the backend, durable task records, local model services, retrieval and search on a primary Linux service host. November recovery and native-task receipts add dated operational proof. The older “desktop runs everything” description is no longer an accurate account of this arrangement.
Documented components include Python/Uvicorn services, SQLite records, Chroma retrieval, SearXNG, Ollama and llama.cpp-based routing under a Linux service lifecycle. This public page does not query those private services.
- Evidence state
- Documented migration plus November 5 recovery, admission and one-task receipts.
- Acceptance boundary
- Service startup, admission, answer quality and useful task completion are separate states.
Desktop client and owner controls
The desktop retains the native client, guarded local transport, admission and owner-availability controls. Some PM2-managed compatibility helpers and WSL dependencies remained after the service migration; native migration did not remove every compatibility dependency.
A prepared Hub panel is separate from proof that the currently loaded client and serving root are the reviewed build. That ownership and mounted-interface acceptance remains an integration gate.
- Evidence state
- Documented retained controls; reviewed Hub preparation.
- Acceptance boundary
- Identify the active client and integration owner, then demonstrate the mounted workflow without changing security boundaries.
Local-model worker path
A November 5 receipt records one admitted local 27B attempt through the existing engine and durable native ledger. Identity was checked around the task. The generation ended at its token limit; the incomplete answer was rejected and preserved.
This establishes that bounded execution path at its recorded time. It does not establish present availability, broad coding quality, an autonomous scheduler or that the complete AETHER model/runtime was exercised.
- Evidence state
- One real task, completed execution and rejected content.
- Next proof
- A scoped task with sufficient context, a reviewable complete result and independently accepted outcome.
Memory and archive
SQLite application/canonical records, markdown memory and a separate Chroma vector index serve different purposes. A write acknowledgement does not alone prove exact retrieval, canonical/vector equivalence or restart persistence.
The earlier native feeder was deliberately paused after cycle 53 at its October 29 checkpoint. The later cold feedback consumer reads saved task/review evidence; it is a different workflow, not proof of a resumed continuous ingest service.
- Evidence state
- Documented storage boundaries and a paused feeder checkpoint; bounded saved-feedback retrieval.
- Next proof
- Exact source identity, idempotent writes, retrieval parity and restart/interrupt behavior in a reviewed complete path.
Specialist compute and witnesses
Earlier fleet documentation assigns small-model/embedding work, lightweight CPU tasks and hash-only observation to specialist resources. Those September roles are historical design/measurement evidence, not a freshly verified online fleet.
A later access attempt that failed locally before remote execution does not establish that a physical specialist node is down. Current availability should be measured only through an authorized role-specific check.
- Evidence state
- Historical role documentation; current availability not remeasured here.
- Next proof
- A bounded admission and result check for the role actually being used, with no inferred whole-fleet health.
Public website edge
The public site runs static HTML, CSS and JavaScript through Cloudflare Pages and its Worker. Its request-time site check reads the edge handler and four bundled public assets. It does not read private model, memory or node telemetry.
The House is an agent-organization/source-inventory view. The Floor is an architecture illustration. The homepage’s DOM-node measurement counts browser document elements; none of these is a live physical-machine monitor.
Run the public site check → Read site-check JSON → Agent organization → Architecture illustration →