Fabric evolved from a production dashboard into a governed agent platform with separate local Executor and Studio apps. Drag the slider — or use arrow keys — to walk the timeline: each version, what actually shipped, what is being qualified next, and why it matters.
Interactive timeline
Status rule: green means the milestone's release gates are complete, not merely that its code exists. The v2/v3 labels describe capability milestones; the date-based versions identify local installer releases. They are different tracks, not successive versions of one release. 2026.9.91 is the current repository release candidate. Its retained suite record is signed, checksum-bound, Apple-notarized with status Accepted, and marked release_ready. v3.3–v3.6 remain amber because broader qualification and production-evidence gates are open. Engineering remains active; v3.7 has moved from implementation into qualification and rollout. Cloud Alpha is a separate historical deployment. See what each needs to turn green.
Remaining work · 23 September 2026
These are release exit criteria from the repository plans, not a fresh audit of a teammate’s machine. A code fix closes an implementation gap; real provider results and the responsible reviewer close qualification gates. Historical counts must be refreshed against the exact candidate and environment.
Collect the required real accepted Photoshop and Unity cases for each exact capability/candidate, with independent review. The plan calls for 20-case campaigns; a synthetic run or one successful export cannot qualify a whole operation family.
Distribute the trusted Photoshop provider, qualify the remaining operation families, and complete 20 accepted full character-production tickets. Then explicitly register, certify, publish and commission each workflow against its exact roots, providers and permissions.
Resolve protected Sheets/Atlassian access or retire those sources explicitly; refresh indexes against frozen source revisions and pass the labelled retrieval/citation quality gate. Qualify the new Flat Art UXP operations on real approved targets before their lifecycle promotion.
Build, sign, install and independently trust the native Photoshop challenge and Finder/browser/spreadsheet transports. Prove exact capture and disposable-sandbox replay with fresh consent, rollback/reconciliation and an independently reviewed 20-case cross-app corpus. The local installer’s notarization does not qualify those separate providers.
The exact 2D Iconic Item Unity apply candidate now has an independently signed, digest-bound disposable-project attestation and the installed-agent certification path is implemented. Next, complete the exact agent’s remaining release/promotion/commissioning gates and prove governed game-repository delivery. Faction still needs retained teammate publication, merge and downstream-delivery evidence.
Complete real incident-to-draft-PR qualification with independent code review, deterministic validation, recurrence verification and retained approval evidence. The engine remains in development; opening a draft PR does not establish a live production service.
Reverify the actual hosted deployment and settle its authority track: historical Cloudflare/D1 alpha and planned PostgreSQL authority are distinct. Prove two authenticated workers on different machines, single claim ownership, stale-worker fencing, lease recovery, capacity/backpressure, dead-letter handling and workspace isolation. Close artifact transport, emergency-stop and real connector qualification before promotion.
Finish the consolidated Qualification Operations view, measure model cards and Code Intelligence consumer quality, and commission the new verticals with named owners. Team inference and cross-team memory still need scope, retention, revocation and tenant-isolation proof. Standalone Studio’s Certify handoff and disabled Upgrade/Refresh remain explicit product limitations.
2026.9.91 is bound to source revision 15ab66ed, a signed release-mode suite, an Accepted Apple notarization receipt and the final archive checksum; its suite record is marked release_ready. Broad Zynga distribution approval and target-Mac rollout evidence remain separate. No agent, capability family or production effect inherits authority from the installer.
Evidence and operator steps: External qualification gates · Detailed implementation checklist · v3.3 qualification plan.
Implementation and release evidence
The architectural baseline converges around one six-plane contract spine. Inventory counts in the cards below are dated August snapshots, not a current installation audit: Intelligence → Context & Knowledge → Capability → Execution → Governance → Assurance. It does not turn external evidence into a repository checkbox.
55 executable; 37 knowledge-only or awaiting reviewed activation contracts. Discovery and RAG indexing never grant execution.
Thirty registered contracts with golden/rejection discipline and three compatibility deprecations.
Context budgeting/diff, World State v2 and compatibility, evidence-derived confidence, normalized Agent/Capability projections, sealed checkpoints and the execution-event read model are repository foundations.
The historical seven-workspace audit recorded a verified post-recommission refresh; this is not a fresh access check. Canonical edits return derived indexes to fail-closed canonical_revision_mismatch until the next source freeze and refresh. Protected Google Sheets and one Atlassian Cloud source still need owner access or an explicit retirement decision. The 2D Iconic Item Unity apply capability has passed its approved disposable-project qualification with an independently signed attestation; the agent’s release, promotion, commissioning, writable-target approval and delivery evidence remain distinct. Other Unity completion paths still need their own independently operated signed feeds and pinned public trust.
Environment fingerprints, real disposable and accepted-ticket runs, approved writable scopes, owner activation, independent review, signed/notarized installed builds, certification, publication and commissioning must come from their owning systems and people.
World State and replanning stay above cache work. Provider/runtime KV or exact prefix caches are performance-only. A semantic answer cache is deliberately out of scope because generated answers cannot safely cross freshness, provenance, workspace, authority, policy and validation changes.
Upcoming
The next releases turn implemented contracts into independently evidenced operations. They do not bypass qualification by adding a green badge.
Authorize protected Sheets, decide the remaining Atlassian source, freeze canonical inputs and refresh RAG. Onboard the separately operated Unity Ed25519 attestor with a read-only feed and public trust only.
Add one operator view for feed freshness, exact capability/candidate/environment bindings, accepted-case counts, independent review and next governed action. It observes evidence; it never signs, certifies or promotes.
Use the completed 2D Iconic Item disposable qualification as a bounded precedent, not a blanket approval. Qualify each remaining exact capability family on reviewed disposable targets, then retain the required distinct accepted cases and an independent review bound to each exact corpus digest.
PostgreSQL as sole hosted authority, two authenticated workers on distinct hosts, signed failover/dead-letter/backpressure/isolation evidence, then verify that deployment’s distribution and promotion evidence. Local suite notarization is tracked per installer.
Replace unknown model-card fields only with retained cost, latency, cache, privacy, structured-output and tool-call observations bound to exact model/provider/runtime/environment revisions.
Commission the first Production, QA, Product and Art agents only after exact skill, capability, model, permission, qualification, publication and human-owner bindings pass.
Evaluate the implemented Code Intelligence review and impact-planning consumers; expand the Production Knowledge Graph beyond characters; add tenant-qualified team inference and cross-team knowledge federation. Semantic answer caching remains out of scope.
Where it's going
Every stop on the timeline is the same Fabric Intelligence engine gaining a capability — never a new tool. Knowledge and confidence learned in Tech Art carried into Design, into the governed Faction Offers and 2D Iconic Item families, and into the in-development bug-fix engine and incident response. The cloud era didn't replace the local platform; it added a budgeted cloud lane beside it. That is the design bet: new work becomes a new agent, and new intelligence becomes a new capability behind the same contract — so the platform gets more capable without the surface above it moving.
Dive deeper: the architecture and the Fabric Intelligence engine for how it's built, or the Architecture Master Plan for the whole platform on one page. Decisions are recorded as ADRs — the promoted, default-on governed specialist layer is ADR-0006 · Fabric Intelligence Core Intelligence, with a persistent Settings kill switch and emergency process override.
23 September 2026 audit
The current signed/notarized local candidate, conversational Studio authoring, explicit Studio-to-Executor package handoff, exact installed-agent certification review and the bounded 2D Iconic Item disposable qualification now exist. They are no longer wholly future work.
Broad distribution approval, protected source access, remaining capability-family corpora, native provider rollout, distinct-host exercises, agent release/promotion/commissioning and production delivery require their own evidence. Studio can guide the handoff but cannot grant Executor authority.
Local release history · Detailed implementation checklist and updated audit. Historical counts are dated snapshots, not this Mac’s readiness.