independent personal system · public-record · verified 2026-07-24

Nolan operator system

A capable agent is less useful when it forgets context, loses execution state, or cannot distinguish public knowledge from private authority.

Matthew’s role

System designer, engineer, and daily operator

attribution

Matthew Gennings

claim boundary

The public record describes the operating shape only. Private memory, contacts, prompts, credentials, and operator authority are not public portfolio evidence.

sanitized public proof · no private sources
A sanitized public proof composition connecting uxuiai.org product records and the ux-ui.ai consultancy journey.
Nolan’s public operating seam is demonstrated through the two allowlisted surfaces it can help keep coherent. Composed only from deterministic captures of uxuiai.org and ux-ui.ai with private-source patterns rejected.

sanitized public proof · no private sources

Nolan operator system

A sanitized public proof composition connecting uxuiai.org product records and the ux-ui.ai consultancy journey.

Composed only from deterministic captures of uxuiai.org and ux-ui.ai with private-source patterns rejected.

the meaningful constraint

Memory, tools, repositories, consent, release gates, and human review have to stay legible and revocable.

the smallest consequential decision

Separate public context, reviewed relationship policy, and private authority, then make each agent own a bounded outcome rather than a conversational fragment.

implementation depth

  • MCP and local tools
  • repository-aware memory
  • Notion and public records
  • release and confirmation gates

what shipped or remains public

A daily operating system that can research, build, test, and hand back evidence while keeping private authority out of public surfaces.

privacy relevance

The public portfolio exposes no private Nolan endpoint, prompt store, filesystem path, invitation secret, or personal memory.

accessibility relevance

Agent-mediated paths inherit the same plain-language, recovery, and public-fallback requirements as visible interfaces.

correction path

If this public evidence has changed, email a correction for this record.

supporting explanation

the model follows the proof.

The primary artifact above shows the public operating surface. This diagram explains the boundary without pretending to be the evidence.

architecture diagram · explanatory only
A public architectural diagram of four bounded Nolan records.
The diagram explains the boundary model; the public-surface composition above is the primary proof. Purpose-built public diagram with no endpoint, credential, prompt, contact, or filesystem detail.

architecture diagram · explanatory only

Nolan operator system architecture

A public architectural diagram of four bounded Nolan records.

Purpose-built public diagram with no endpoint, credential, prompt, contact, or filesystem detail.

back to all work