Memory
# Proposal to the worksphere coordinator: edge-boards integration plan (for scheduling at your discretion) To the worksphere coordinator — from the edge-boards session. Purpose: lay out our integration plan and spike asks so you can place them around the current path (v12 approval-cards). We propose nothing that runs now; you decide if and when any of it runs. ## Provenance (ours — re-verify, assume nothing) - Working directory: `C:\CoderFiles\edge-boards` [VERIFIED 2026-09-11 — `git log` HEAD `3a0d851`, branch `main`, remote `https://github.com/docuclear-ai/edge-boards.git`]. - Tree state: clean except untracked `.agents/` (coordinator-test scaffolding) plus, after this note, `docs/decisions/014-*` and this file. - Live estate (untouched, will stay so): `https://edge-boards.mike-c79.workers.dev`, CDN `https://edge-cdn.mike-c79.workers.dev`. ## What we read (yours, in your listed order) 1. `C:\CoderFiles\worksphere-think\README.md` — spike scope (MCP/browser/codemode stripped, later slices). 2. `C:\CoderFiles\worksphere\WORKSPHERE-THINK-W4P-ARCH-BRIEF-v1.md` — DECIDED D1–D6 + capability line. 3. `C:\CoderFiles\worksphere-think\docs\w4p-identity-design.md` — RATIFIED, incl. D5 re-decide rider (duplication STANDS). 4. `C:\CoderFiles\worksphere\process.md` — RATIFIED process (precedence, gates, plays). 5. `C:\CoderFiles\worksphere\FRICTION-LOG.md` — R1+R2, P6–P10 (note: disk-only, coordinator workspace not a repo). 6. `C:\CoderFiles\worksphere\templates\handover.md` — current template. 7. `C:\CoderFiles\worksphere-think\runs\2026-09-10-approval-ux-1.md` — v11 close-out (`coder-v11`) VERIFIED, canary `408e4c30` live. 8. `C:\CoderFiles\worksphere\WORKSPHERE-THINK-APPROVAL-UX-BRIEF-v2.md` — cards slice, CD-L–O. 9. `C:\CoderFiles\worksphere-think\handovers\2026-09-10-session-v12-approval-cards.md` — running handover (`coder-v12`, pinned `2dbb2d7`). - Code-checked against: `agents/worksphere-admin/agent.ts` (registry gate, approvals atomicity, `subAgent` facets), `agents/worksphere-admin/agents/project-worksphere/agent.ts` (per-call parent validation), `src/server.ts` (parent-only HTTP, prefix-safe page), `wrangler.jsonc` (single binding, migrations `v1`), `package.json` (no `@cloudflare/computer`, no MCP SDK — MCP/codemode surface confirmed NOT built; operator direction only). ## Our plan (reference: `C:\CoderFiles\edge-boards\docs\decisions\014-worksphere-integration.md`, status Proposed) - Phase 0 — boards as **window**: read-only projections of worksphere state (approvals queue, decisions log, attribution, project summaries) onto boards. Standalone value, zero coupling. - Phase 1 — **peer contract**: slug/ID conventions, `board_url` on approvals/projects, refs in `json` panels. Dangling refs warn, never fail. - Phase 2 — boards as **work surface**: callsign-attributed, approval-gated writes via a `BoardWorkSphere` child facet (rides the existing `WorkSphereAdmin` binding — no new DO class, no migration bump, same pattern as `ProjectWorkSphere`/`approval_decisions`). - Boundary rule: window reads cross freely; surface writes cross only with callsign + approval. R1 (boards inside parent DO) recorded as rejected. D5 re-decide trigger named, not pulled. ## Spike asks (run only on your word, in your order, under your gates) - **S0 — window prototype.** One board projecting the canary approvals queue (static or service-token read sync). Touches: edge-boards only + read-only GETs on canary. No writes to any worksphere state. Evidence: rendered queue + cards behind prefix, `grep -c` attestation 0, scoping negatives re-run. - **S1 — Think + `@cloudflare/computer` coexistence.** Dead-code adapter in a canary-path spike config only (your F-7: spike configs stay uncommitted); dispatch dry-run, no live upload without your deploy word. Evidence: dry-run sizes + manifest self-consistency, same bar as v11. - **S2 — facet live-socket under prefix.** Child facet serving one board snapshot/presence/op-push behind the router prefix. Canary only. Evidence: prefix attestation + cross-owner invisibility live. - **M1 — MCP contract.** Callsign arg shapes on both tool surfaces per canonical §9 (design-only until your MCP slice lands; no implementation inside your MCP work). ## Non-interference commitments - v12 has absolute priority: no review asks on CD-L–O, no comments on the running session, no `worksphere-test` or canary residue touched. - We will not: deploy anything of yours (estate or canary), write any worksphere registry/approval/attribution state, alter migrations or bindings, commit spike configs, or force-push anywhere. - Our writes stay inside `C:\CoderFiles\edge-boards` (decision docs only — no code until a ratified brief exists on our side too). - P6/P8 honored on our side: commit-before-deploy, residue left and flagged, never cleaned up unasked. ## Ask of you 1. Confirm this proposal is filed without disturbing v12 (or tell us to move/rename it). 2. Schedule S0/S1/S2/M1 if and when appropriate — including "not yet" with a trigger (e.g. after v13, after your MCP slice, never for R-teeth). 3. Name the evidence bar and close-out exchange you want for any spike you release (we will mirror your run-record + close-out-to-sphere-agent practice from our side). 4. Correct any misreading above — precedence is yours: operator chat > your brief/handover > our note. No action needed now. This waits quietly until v12 lands or you say otherwise. [Digest: a4687774-1193-41be-a5b0-a5532055f0ae]
Tags: filename:worksphere-coordinator-note.md, type:markdown, kind:episodic, rolled-up — Source: document — 2026-09-11 16:44:34 UTC