---
id: "concept-shared-surface"
type: "concept"
source_timestamps: ["00:01:32", "00:03:45", "00:05:45"]
tags: ["architecture", "data-sync"]
related: ["concept-open-brain", "claim-no-sync-layer", "quote-no-sync-layer", "entity-supabase"]
definition: "A single database table that acts as the absolute source of truth, accessed directly by both human visual interfaces and AI agents."
sources: ["s21-ai-tool-memory"]
sourceVaultSlug: "s21-ai-tool-memory"
originDay: 21
---
# Shared Surface

## Definition
A single database table that acts as the absolute source of truth, accessed directly by both human visual interfaces and AI agents.

## The Principle
A **Shared Surface** is the foundational architectural principle of [[concept-open-brain-d21]]: both the human and the autonomous agent **read from and write to the exact same database table**. There is no API, no export layer, no sync middleware between them.

- When the agent logs a note during a chat, it writes directly to the table.
- When the human opens the visual dashboard ([[concept-human-door]]), they are reading from that **identical** table.
- Both sides are always immediately consistent.

## Why Sync Layers Fail
Traditional software relies on APIs and sync middleware to keep different systems updated. These layers are the source of lag, breakage, and silent data loss. By eliminating them entirely, the Shared Surface achieves architectural simplicity — see [[claim-no-sync-layer]] and [[quote-no-sync-layer]].

## Implementation
The Shared Surface is implemented as a structured table in [[entity-supabase-d21]]. The agent reaches it through [[concept-agent-door]] ([[entity-mcp-d21]]); the human reaches it through [[concept-human-door]] (a [[entity-vercel-d21]]-hosted web app).

See also [[action-create-shared-table]] for the concrete setup steps.


## Related across days
- [[concept-context-graph]]
- [[framework-open-brain-architecture]]
- [[concept-mcp]]
- [[concept-hybrid-memory-architecture]]