Memory
SPHERE GAP / MODEL INCIDENT (reported by Mike, Sep 4, 2026, ~00:00 BST): Perplexity downgraded model access to a cheaper model mid-session and behaviour degraded ('things started getting weird'). Evidence: no Sphere updates were written for work done after the last verified entries — control work item 3ccf5c84 last appended Sep 3 ~20:30 BST (blueprint permanent fix a09cc602, acceptance test passed, issue CLOSED, ready for factory deploy); session handoff efe7781f rewritten Sep 3 ~19:48 BST. Mike kept working ('limping along'), so SPHERE STATE IS STALE vs actual progress from ~20:30 BST Sep 3 onward. Mike will provide an overview of what was done — capture the delta into Sphere from that briefing, reconcile against this baseline, then refresh handoff efe7781f. Diff baseline: factory deploy = next planned step; blueprint fix landed; upstream PR to cloudflare/cloudflare-os still owed (branch fix/blueprint-install-resource-stamp, cloudflare-os 475c41b); DEPLOYER_CONTRACT seeded-resource assertion amendment pending; open decisions DP-1..DP-6, ND-1..3 unchanged as far as Sphere knows.
[Update Sep 4, 2026]: [RESOLVED, Sep 4, 2026, ~01:05 BST]: gap reconciled. Mike's overview captured in e9982d86 (factory/vibesdk: failed fresh deploy, Muse Spark research, adoption ruling) and 4b8031cf (int_control session: MCP portals + ambient sphere gatekeeper live, /tags vendor bug parked). Handoff efe7781f updated with the reconciliation summary. Sphere state is current as of ~01:05 BST Sep 4.
Tags: docuclear, sphere-gap, incident, model-access, staleness, reconciliation-baseline, volatility:state, project:docuclear, kind:episodic — Source: mcp — 2026-09-03 23:01:22 UTC