Memory
RECONCILIATION NOTE — edge-boards × worksphere convergence question (filed by Perplexity after reading decisions 015/016/018 + the compliance Phase-0 run record on 2026-09-11). State of play: 016 SQLite = edges now (Accepted, graph_edges in directory DO, closed rel vocabulary, baseVersion guards); board payloads later, gated on lazy-migration spike — overrides Perplexity's heavier dual-write suggestion (struck: 'no caller outside the DO touches storage' makes dual-run unnecessary). 015 FTS5 over summary capsules in directory = Proposed, step-0 probe GREEN, awaiting ratification; Perplexity's vote on its open question: capsule eligibility should be OPT-IN per panel, not any-markdown (retrieval corpus hygiene). 018 composed views proposed, source-probe green. 014 framing: 'window first, work surface later' — Phase-0 (dataset→policy→revision-pinned assessment→rendered view) proven live 2026-09-11 with the vendor-access trio. Mike's open design question (17:46 BST): does the board surface collapse worksphere into itself? Position on record: NO collapse — boards are the interaction/window plane (liveness-optimised, LWW); worksphere is the trust plane (identity, credential classes, approvals-with-audit, fail-closed provisioning — 15 sessions of verified negatives); join at the proven 014 seam rather than rebuilding worksphere inside the shell. Future board ambitions map to existing seams: forms/wizards = level-2 components; pasted data = importcsv/paste components; API-populated panels = j-datasource; ingested files = 017 (references in panels, R2 bytes); approvals = worksphere queue rendered as board cards (GAP-9 substrate). Next gates: ratify 015, run S0 window-projection spike, then 016 payload spike. [Update Sep 11, 2026]: **Amended 2026-09-11 18:xx BST (Mike + Perplexity):** refine the convergence rule from window-first-only to a four-layer ladder. Layers: (1) Sphere/SecondBrain = memory; (2) worksphere = trust/verb adjudication; (3) edge-boards = materialised surfaces (canonical panels + generated views); (4) cloudflare-os gadgets = packaged, isolated deliverable apps that consume board views, reaching out only through gatekeepers. Mike's original 'gadgets are the window' plan inverts one step: boards are the window; gadgets are the distribution vehicle. Functional rules: (a) board views behave like SQL views — projections over canonical panel state that double as the permission boundary (a client gadget receives the view URL + shape, never the board); (b) boards may GENERATE any UI, but no generated UI carries authority that wasn't declared — actions bind to existing guarded verbs (boards' check-then-write, worksphere approval queue); (c) the lack of shadow DOM in jComponents is a feature not a gap: generated components cannot smuggle private state — every datum lives at an inspectable path in canonical JSON, which is what makes LLM-authored UIs auditable. S0 window-projection spike validates the (3)→(4) hand-off. [Digest: 8a482994-7aad-4c78-b0e2-afa945356bfd]
Tags: edge-boards, worksphere, convergence, decision-reconciliation, 015-ratification-pending, 016-sqlite, window-first, 014-integration, volatility:state, project:docuclear, kind:episodic, rolled-up — Source: perplexity — 2026-09-11 16:57:38 UTC