Fabric handbook · Fabric + Fabric Studio

Release changes and documentation coverage

The handbook distinguishes committed product behavior, installer evidence and workflow authority. 2026.9.91 is the current repository release candidate: its suite record is signed, checksum-bound, Apple-notarized with status Accepted, and marked release_ready. Zynga distribution approval, agent certification, commissioning and production-effect approval remain separate gates.

◇

Current evidence · 25 September 2026

2026.9.91 release checkpoint

What is in the suite

Separate Fabric Executor and Fabric Studio apps; server-owned release approvals with automatic resume; streamlined certified-agent release flow; refined Studio authoring, conversation and overflow layouts; governed Ability correction and delivery; Git publishing using saved credentials without requiring a standalone CLI; and stabilized 2D Iconic Item execution.

What the installer proves

The retained record binds release 2026.9.91 to source revision 15ab66ed, a signed release-mode build, an Accepted Apple notarization receipt and the final archive checksum. It does not certify an agent, approve a repository write or prove downstream delivery.

◇

Release eras

Changes users should know

Patch releases are grouped by the product outcome they advanced. Every released version remains listed in its era; the detailed engineering ledger stays in local-distribution/RELEASE-NOTES.md.

Release eraIncluded versionsWhat changedBoundary to remember
Governed release and Ability delivery
Current era
2026.9.85 · 2026.9.86 · 2026.9.87 · 2026.9.88 · 2026.9.89 · 2026.9.90 · 2026.9.91Server-owned release approvals with automatic resume; streamlined certified-agent release review and guided panel; refined Studio authoring workspace, conversation and overflow layouts; governed Ability correction runs, first-run overwrite review and draft PR delivery; model download progress restored; Git publishing using saved credentials (no standalone CLI required); idempotent Ability artifact provenance; Jira publication readback for comment-only updates; agent evaluation state kept outside the release tree.2026.9.91 is the current signed, checksum-bound, Accepted-notarization repository candidate at 15ab66ed. Release approval is server-owned but does not commission agents, approve repository writes or authorize downstream delivery.
Qualification and agent release2026.9.80 · 2026.9.81 · 2026.9.82 · 2026.9.83 · 2026.9.84Durable 2D Iconic Item qualification and independent disposable-project attestation; portable, exact-revision agent certification; refreshed installed revisions; direct Studio-to-Executor handoff and qualification recovery; imported-agent certification continuation; exact Toolsmith package resolution; clearer certification/release UI.Qualification and certification do not publish, commission or authorize production effects.
Conversational authoring2026.9.46 · 2026.9.48 · 2026.9.50 · 2026.9.72Guided local-AI setup; live Trigger-to-stage graph; visible proposal, reviewer and retry state; retained questions, warnings and attachments; redacted diagnostic export; verified pinned Ollama and embedding-model provisioning on a fresh Mac.A proposal, model review, package handoff or successful installation is not execution evidence. The 2026.9.48 build was signed, but its own notarization/team approval remained pending.
Governed Studio authoring2026.9.34 · 2026.9.35 · 2026.9.41 · 2026.9.42 · 2026.9.43 · 2026.9.44Flat Art resume and Unity-idle recovery; shared agent execution standard; exact repository ownership and image evidence; simplified repository setup; signed Studio-to-Executor packages; specialist review team, local SOPs, playbooks and repeatable evaluations.Studio authors and evaluates drafts. Executor still owns installation, certification, commissioning, repository mutation and effect approval.
Credential-safe delivery and isolation2026.9.16 · 2026.9.17 · 2026.9.18Host-bound GitHub Enterprise PR transport, PR-access preflight and retained-push reconciliation; explicit delivery intent; durable status reconciliation; responsive Vision scanning; one retained run-owned Live-data worktree and branch receipt per Faction run.Delivery intent remains separate from publication approval. A draft PR is not a merge, and neither proves downstream Sheets/Jira completion.
Local suite foundation and recovery2026.9.7 · 2026.9.8 · 2026.9.9 · 2026.9.10 · 2026.9.11 · 2026.9.12 · 2026.9.13 · 2026.9.14 · 2026.9.15Exact-revision certification recovery; safer reinstall and emergency-stop setup; stronger memory/RAG/Graphify lineage; Google OAuth; reviewed setup transfer; complete signed support payload; certified-package re-export; mixed-snapshot publishing; retained Faction publication recovery and expanded operator guidance.Compatibility warning: 2026.9.14 omitted the production commit_parent adapter. Use 2026.9.15 or later for retained Faction publication recovery.

Within each era, versions are ordered oldest to newest. The table prioritizes behavior an operator or agent author needs to understand; the engineering ledger retains the patch-by-patch detail.

◇

Reference

Process changes to adopt

  1. Use a matched Executor + Studio installer and verify the installed release before diagnosing agent behavior.
  2. In Studio, finish Build → Check → Test → Resolve → Save, then review the exact signed package before sending it to Executor.
  3. In Executor, treat installation, certification review, commissioning/readiness and effect approval as distinct steps. Follow the displayed next action for the installed revision.
  4. For 2D Iconic Item, let Fabric resolve and verify the exact Toolsmith package before the Unity physical stage. Qualification evidence does not authorize a game-repository write.
  5. Keep local preparation, draft PR, merge and downstream Jira/Sheets delivery as explicit, independently verified checkpoints.
◇

Reference

Coverage and source evidence

Handbook areaAudited source / contract
Release version and macOS evidencedist/suite/Fabric Installer.release.json, notarization receipt and archive checksum
First-time setup and package behaviordocs/forge-executor-quick-start.md, local-distribution/RELEASE-NOTES.md, package scripts and suite builders
Settings and connectorsdashboard/path_settings.py, Settings views, connector registry and backend routes
Studio authoring and handoffstudio/authoring_team.py, package export, Executor bridge, Studio host UI and agent-package contracts
Agent import and certificationAgent package verification, quality qualification, installed-agent admission, commissioning authority and promotion contracts
2D Iconic ItemTyped workflow, live providers, Toolsmith session, disposable attestation, qualification store and operator guide
RAG, skills and memoryRAG, memory, skills registry, knowledge source and lifecycle services
Runs and publicationRepository policies, publisher, runtime/effect evidence contracts and downstream delivery verification

The wiki is a guide to retained behavior and evidence, not a live readiness dashboard. Maintainers must update this page and the affected operator guide when a field, state, runtime contract or release changes.

◇

Reference

Release and deployment limits

Internal candidate status is not broad release approval. Apple notarization is not agent certification. Certification is not commissioning or an effect approval. A disposable Unity qualification is not permission to write an approved game repository. A draft PR is not a merge or downstream delivery.

The current suite supersedes the older 2026.9.15 handbook baseline, but the historical recovery notes remain useful for installations that have not yet upgraded.