Architecture Atlas

Explain the system without exposing the system.

This page describes functions, responsibilities, and governance boundaries. It is intentionally not a production blueprint.

06

Human authority

Consent, permissions, physical safety, escalation, and final decision rights.

05

Evidence & governance

Audit records, corrections, capability gates, and publication boundaries.

04

Presence & interface

Voice, interaction, and carefully bounded awareness at human scale.

03

Continuity

Memory, identity, history, values, and context that survive a session.

02

Orchestration

Routing, tasks, agents, tools, and the logic that connects capability to purpose.

01

Model layer

Replaceable reasoning engines selected for the work, not treated as the whole identity.

WHAT WILL BE ADDED

Decision diagrams, not wiring diagrams.

Future charts will show how information moves between functional layers, where human approval enters, what persists through model change, and how failure becomes a durable lesson.

WHAT STAYS PRIVATE

The attack surface.

Production addresses, device inventory, precise physical layout, live observability, secrets, raw sensing material, household routines, and implementation details that would make intrusion or imitation easier.

DEFERRED BY DESIGN

Deep technical documents come later.

The first public release establishes the story, method, governance frame, and Paul’s operating credibility. Detailed technical material will be added as sanitized, reviewable modules—not as a maintenance burden at launch.

Read the disclosure framework