Memory
BOUNDARY DECISION — the three layers, RULED by Mike (Sep 4, 2026, ~1:45pm BST, after challenge pass with Perplexity; challenge framing in conversation, this entry is the ratified outcome). THE STACK: 1. GLASSAGENT (platform; internal/developer-facing name only — RULED: umbrella, not workspace-only). The whole machinery family: GlassAgent Workspace (the OS-derived interaction layer; 'Cloudflare OS' stays quarantined), the sphere data plane, ingestion service, the gatekeeper family, provisioning/dispatch (W4P), and the contracts/evidence/governance machinery. Product-neutral and multi-product by construction — a second product (vibesdk SMB line, anything else) builds on GlassAgent without forking it. User-facing exposure: NONE except as developer-brand for articles/OSS (f0552ce8). Boundary rule vs upstream: pinned cloudflare-os submodule + starter + our contract/governance/evidence layer on top — the thin layer that IS the product (4df88ef0 Sep 2 update). 2. DOCUCLEAR (product; the ONLY user-facing name — 1950f2b5). Packaging only: brand, terminology wrapper (gadget→app/tool, agent persona — 9eb83a67), Paddle billing/plan tiers, SMB onboarding, the vibesdk-built signup site, and product-level configuration of platform capabilities. RULED: machinery-vs-packaging boundary — DocuClear contains NO capability GlassAgent doesn't provide. Capabilities (workspace, sphere, gatekeepers, vault/director pattern, posture scoring, evidence) are platform; DocuClear configures, brands and prices them for UK SMBs. 3. DOCUCLEAR-CONTROL (control plane; RULED wider than the app). The build/govern/operate estate: docuclear_control the app (Mike's operator surface at control.docuclear.ai), docuclear_factory (vibesdk fork), int_contracts, docuclear-evidence, the name registry, the audit workspace. RULED: governs the platform AND all products, present and future — not DocuClear only. Dogfood consequence per fd14e2e3 (every function becomes a workspace): control is itself GlassAgent machinery pointed at GlassAgent. ITEM 5 (sphere duality) — OPEN, under active discussion Sep 4 ~1:47pm: Mike's instinct — sphere has morphed into 'just a capability of the platform'. Resolution to be appended when ruled. Open sub-questions carried in: vendor sphere (Mike's second brain, fronted by the ambient sphere gatekeeper in control — 4b8031cf) vs customer sphere (docuclear-sphere/int_sphere_core) — same codebase? isolation unit? ambient-by-configuration? convergence timing? LINKS: naming 1950f2b5, foundational principle fd14e2e3, system overview 6ed41ea6, handoff efe7781f, mission 4df88ef0, external-access analysis 12f59074. [Update Sep 4, 2026]: [Update Sep 4, 2026]: ITEM 5 RESOLVED (Sep 4, 2026, ~2:30pm BST — Mike ruled after exploration): 'sphere' = a CAPABILITY CLASS of the GlassAgent platform — the memory/navigation substrate. 'Sphere is the map': what exists, how it works, what was decided, where base authority lives (with pins to verify). Not a layer, not a product. Substrate = SurrealDB (trigger (d) fired on a092abb2). Topology: instance per trust domain — preferred production shape is per-customer instances on Mike's UK VPS; first build on VPS-via-tunnel or SurrealDB Cloud free instance. Ambience: a workspace's sphere binding is granted in its creation manifest (contract-at-birth), never ambient by default — upstream's ambience rule adopted. Both incumbents SUPERSEDED as platform substrate: the vendor sphere (Mike's second brain) and docuclear-sphere (D1/KV/Vectorize customer data plane) — migration may be manual; no carried-over limitations. The vendor sphere remains the OPERATIONAL memory of the build until cutover (this entry is being written to it).
Tags: docuclear, glassagent, boundaries, architecture, decision-record, three-layers, ruled, volatility:state, project:docuclear, kind:episodic, status:canonical — Source: mcp — 2026-09-04 12:48:49 UTC