Memory
INNOVATION PIPELINE — publishable items registry (opened Sep 3, 2026, ~6:23pm BST — Mike: 'each could be a publishable item… articles and OSS base, gives DocuClear industry cred'). PUBLISHING LANE (per 0b8f273e branding note): articles/OSS release under GLASSAGENT (developer/industry-kudos surface, glassagent.ai + Nimbus docs lane a91b09ef); DocuClear stays the SMB product surface. STANDING RULE: every published claim must verify against the evidence store — the auditor fact-checks articles pre-publication (claim↔code applied to our own marketing; receipts or don't publish). THE REGISTRY (status at opening): (1) THE CALLSIGN PATTERN — multi-agent identity for MCP; article DRAFT EXISTS since Aug 7 (old-sphere c14fd70c); closest to done. (2) THE CONTRACT/EVIDENCE LOOP — four artifacts, three checks; 'every merge reconstructible / every yes reconstructible' (b7f41f56). (3) CONTRACT-AT-BIRTH + GENESIS — a system that contractualises itself; agent-defined, human-ratified bootstrap (fd14e2e3; GENESIS_CONTRACT ratified today). (4) THE THREE STRANDS — model/deterministic/possibilistic-human symbiosis (philosophy piece). (5) DOCS-AS-SINGLE-LINE-JSON + skills — the RAG-rival pattern with MEASURED numbers (1,850 items, 0.2ms queries; 978b7cce); OSS artifact = the Total.js skill + exporter pattern. (6) THE AUDITOR AUTHORITY MODEL — review everything, never execute; verdicts feed deterministic gates (34b0f4a0). (7) CONTRACT-ENFORCED MCP PORTAL — codemode pattern + contract validation at execute() (5e4408f5). (8) EVIDENCE-BASED MODEL ROUTING — promotion ladder implementation (Ringer-inspired, ee0c53a2). (9) THE NAME REGISTRY — naming as a governed boundary; the dictation-drift anecdote is the story hook (1950f2b5 extension). Each item: article + (where applicable) OSS base; add new candidates as they emerge; statuses: idea → drafting → reviewed-by-auditor → published.
[Update Sep 3, 2026]: [Pipeline addition, Sep 3, 2026, ~6:29pm BST]: THE EXEC FRAMEWORK SERIES joins as the positioning SPINE (see positioning pathway entry for the full mapping). Art.1 + Art.2 written (four characteristics of work × three reasoning types); Art.3 WIP unfinished (reasoning types × work characteristics, the visibility gap); Art.4 never written — and Art.4 IS the DocuClear reveal ('how to integrate AI into the work and why the work itself has to change'). Publishing order proposal: finish Art.3, write Art.4 as the product-launch article, THEN the technical items (callsigns, loop, genesis…) land as the 'how we built it' engineering series beneath it. The series gives buyers the framework; the platform is its proof.
[Update Sep 3, 2026]: [Vocabulary lesson + article-4 hook, Sep 3, 2026]: the framework articles underperformed on LinkedIn because they don't sound like the current fashion ('context engineering', 'skills') — the market buys vocabulary before substance. TRANSLATION STRATEGY for the series: bridge in the fashion terms, then reframe. Article 4 hook candidate: 'SKILLS ARE UNGOVERNED CONTRACTS' — end-user-editable skills = amending the agent's governing context with no version, no review, no evidence trail; per Mike's own framework it's possibilistic burden pushed onto users WITHOUT the owning machinery. The contrarian hook lands because we carry receipts: the wizard-provenance story, the KV-adoption improvisation caught by the loop, genesis ratified through a governed gate. Never argue taxonomy in public — show the machinery.
Tags: docuclear, innovation-pipeline, publishing, glassagent, articles, oss, industry-cred, registry, project:docuclear, kind:semantic, status:canonical, volatility:state — Source: mcp — 2026-09-03 17:24:22 UTC