Memory
ARTIFACT — DEPLOYER_CONTRACT v0.1 DRAFT produced (Perplexity, Sep 3, 2026, ~12:35pm BST, from decision 5e4408f5). Delivered to Mike as a Markdown file for review; canonical home on commit = docuclear GitHub org (created today for greenfield separation), then hash-pin + verbatim duplication into consuming repos + evidence snapshot at /contracts/DEPLOYER_CONTRACT@0.1.md per the loop. CONTENT: 16 sections — authority model (gadget proposes / gatekeeper disposes / worker executes / Workflows orchestrates; structural no-egress enforcement); 4 deployment profiles (workspace-glassagent, service-platform, sphere-customer, factory-internal); full manifest schema incl. service_bindings/secrets_store_secrets/workflows/keep_bindings; workflows bindings forbidden in namespace deploys (Cloudflare docs-verified), account-level only; contract-reference verification (context gatekeeper serves hash-pinned, byte-identical vs GitHub canonical; contracts embedded in deployed artifacts, queryable at health endpoint); health contract; evidence emission (run records, audit per governed call, digests-only secrets); append-only rollback; portal least-privilege + async semantics; decommissioning; amendment procedure via gatekeeper-github. SIX OPEN DECISION POINTS (DP-1..6): context-store↔GitHub sync mechanism; vibesdk API-surface inventory → portal tool appendix (v0.2); keep_bindings semantics; Dynamic Workflows adoption (post-MVP); gadget-env binding wiring verification; namespace-workflow spike. NEXT PER PLAN: Mike reviews draft → commit + pin → then score engines (vibesdk + deployer worker) against the contract → then work items (deployer worker contract-first, contract-based vibesdk, controller gadget workspace, gatekeeper-github, sphere-core). [Update Sep 3, 2026]: [Regeneration, Sep 3, 2026, ~12:50pm BST — Perplexity]: DEPLOYER_CONTRACT v0.1 draft regenerated and re-delivered. Changes: (1) nomenclature applied throughout — docuclear_factory (fork; 'vibesdk' = upstream only), gatekeeper-factory, docuclear_control, int_/cust_ repo prefixes, canonical home = int_contracts in the docuclear org; (2) foundational principle fd14e2e3 framed in §1 — every function a workspace, profiles as the only differentiation (§4 note; internal function workspaces incl. the audit workspace deploy under factory-internal); (3) §5 rule 7 added — name validation against the registry per NAMING_CONTRACT (unregistered name = failed validation); (4) audit agent (34b0f4a0) added — §2 definitions, §3.7 (verdicts feed deterministic gates, never direct enforcement), §7 review gates (PR → requirement→diff; deploy completed → manifest-vs-contract + evidence completeness; periodic drift sweeps), §9.5 (auditor consumes the evidence stream only); (5) §6.4 names contract-at-birth; §14 decommissioning now quarantines names per NAMING_CONTRACT. Awaits Mike's review, then canonical commit + pin + evidence snapshot. [Update Sep 3, 2026]: [Scope clarification, Sep 3, 2026, ~1:01pm BST — Mike + Perplexity]: the contract family has THREE TIERS. TIER 1 — PLATFORM contracts (genesis, deployer, naming, sphere-gatekeeper, ingestion…): internal, authored once, govern the machinery and its boundaries for everyone. TIER 2 — CUSTOMER DEPLOYMENT contracts: instantiated per customer AT ONBOARDING by the factory — not hand-written each time; generated from the profile template@version + the customer's config/clauses (the 'contract as input' to the client-onboarding utility); pinned, versioned, evidence-trailed, registered under their cust_ slug; embedded in the deployed artifact per DEPLOYER_CONTRACT §6.4. TIER 3 — the customer's OWN obligations graph: the product itself — DocuClear contractualises the customer's work (policy extraction → obligations → checks; vault rules; compliance enabler). Tiers 2 and 3 are the SAME machinery at two planes (b7f41f56 topology: 'every merge reconstructible' and 'every yes reconstructible' are one machinery). The auditor reviews all three tiers. [Update Sep 3, 2026]: [COMMITTED, Sep 3, 2026 — VERIFIED by Perplexity via GitHub connector ~1:22pm BST]: repo docuclear-ai/int_contracts (private, default branch main, created 12:14 UTC). Commit 8ee901cc82511bafa6b9f33868949aa4d97f4d36 'Genesis Contract' (12:16:22 UTC, DevmanMikey) — genesis first, ritual order followed. Commit e305400651bdba67b7c1526801f49ca5baa4866e 'Deployer and Naming contracts' (12:18:45 UTC). Blob SHAs: genesis 21eb9e40f9816e1e48d4cbea11bdb2927b432faf (5,340 bytes), deployer 1184369a790b9511ac22cad609938b5b541b2667 (16,215), naming 256127195305b1bc969d4d086c090936d77ab1be (6,774) — byte sizes match the authored drafts exactly = byte-identical commits. SHA-256 contract pins: compute from the committed files at evidence-snapshot time (the blob SHAs above already content-address the exact bytes). TWO FIXES BEFORE RATIFICATION COMPLETES: (1) filenames carry the _v0.1_DRAFT delivery suffix — canonical names should be GENESIS_CONTRACT.md / DEPLOYER_CONTRACT.md / NAMING_CONTRACT.md (rename at the ratification commit); (2) genesis §9 ratification block still has placeholder fields — fill with commit SHA 8ee901cc + date 2026-09-03. OUTSTANDING: evidence snapshots to docuclear-evidence /contracts/NAME@0.1.md + hash. [Update Sep 3, 2026]: [CANONICAL TREE FINAL, Sep 3, 2026, 1:31pm BST — VERIFIED via connector]: docuclear-ai/int_contracts main contains exactly three files — GENESIS_CONTRACT.md (5,690 bytes, blob 3ae922fd5766760ce9eca723d31953920ca5754a, RATIFIED), DEPLOYER_CONTRACT.md (16,221, blob 5aea876a073f900f6bf05cd4c014ddc4f2f72de3, draft), NAMING_CONTRACT.md (6,777, blob 787b9b0a88c358cf8bf094d48cd2b83195c355f4, draft). Commit chain: 8ee901cc (genesis draft) → e3054006 (deployer+naming drafts) → 6f99d1cd (ratification + canonical names + org fix) → 03558132 / 033367dd / 806bc2e0 (draft-suffix cleanup; two deletes needed retries after a branch-ref race — parallel same-branch writes conflict, lesson for future connector batches). SHA-256 pins still to be computed from THESE canonical files at evidence-snapshot time. Note: the delivered-file panels and the committed canonicals now differ (ratification edits) — int_contracts is the only source of truth; the file panels are historical. [Update Sep 3, 2026]: [PINS, Sep 3, 2026, ~6:58pm BST — VERIFIED, Mike-computed from canonical clone, head 806bc2e0; content unchanged since ratification commit 6f99d1cd]: DEPLOYER_CONTRACT.md SHA-256 C12572173D05CF78E7DD0C4C0550764E007752762E925414A7E36EA30F7BB628; NAMING_CONTRACT.md SHA-256 AF4DF3D81B9B5DFDDAD9D155484FFA445C3DE7A749AD867B3071B4996149C0C9. Definition-dialogue run record (evidence artifact #1) delivered alongside — upload path runs/genesis/2026-09-03-perplexity.md.
Tags: docuclear, artifact, deployer-contract, contracts, factory-plane, decision-points, project:docuclear, kind:episodic, volatility:state — Source: mcp — 2026-09-03 11:33:43 UTC