Scoped memory and proposals

Memory provides guidance layered by organization, workspace, factory, primary repository, workflow, crew and worker. When two notes conflict, the later scope in that list wins. Put a convention at the narrowest scope that needs it so unrelated work does not inherit irrelevant instructions.

Approve learning deliberately

A worker can propose a memory note when it discovers a convention or constraint. A proposal does not become active guidance until a person approves it. Review the evidence and remove secrets or task-specific assumptions before approval.

Memory and tool/context payloads have bounds; attaching more text does not guarantee that every future run reads it in full.

Revisions and supporting evidence

Open Factory settings → Memory, choose the scope, and edit a note. Give it a purpose: fact, preference, constraint or lesson. Saving approved wording creates an immutable revision. Revision history shows earlier approved text, who approved it and when, and its supporting evidence. A concurrent edit asks you to reload instead of overwriting someone else's revision. Older notes retain an explicit unknown origin until reviewed.

Attach knowledge sources or completed-run evidence that you can currently read. The note keeps their identities and hashes. A changed source requires a new review; restoring its old bytes or archiving and restoring the note does not clear that requirement. Lost access or retained-away evidence hides derived wording from readers and future runs. A reviewer cannot detach inaccessible evidence to turn that wording into unbound guidance.

Worker proposals remain inactive until approved. Their originating run stays attached, and unavailable or removed run evidence prevents approval and learning-candidate creation. Installed memory-pack copies retain their recorded origin while your reviewed edits stay independent of the publisher.

Archive, delete and export

Archive a note to stop future use while retaining its history. Deleting requires its exact title and removes its note/revision text and directly linked learning copies, leaving a body-free audit tombstone. There is no undelete. It does not rewrite combined agent instructions, past chats, run logs, downloaded exports, model paraphrases or other outputs that may contain earlier wording. A memory delete is not an erasure request covering every historical copy.

Factory versions and files omit evidence-bound memory and report an omission count. Restoring a definition preserves excluded live notes; a portable file cannot carry private source-derived text into a destination without its access checks.

Current limits

Scoped notes are separate from source retrieval and code graphs. Reusable skills provide immutable package versions, dependencies, conflict checks and rollback. Agent studio can turn worker-scoped proposals into human-reviewed instruction candidates, then require evaluation before release. Creating a candidate does not approve the memory note or activate the instructions.

Use editable skills for a worker’s role instructions and what the worker reads for the task context.

For source documents, selected GitHub files, freshness requirements and cited retrieval, use Knowledge sources. Source material stays separate from memory proposals.

Repository memory

Conventions that belong to a codebase, such as "run the compatibility suite before changing the public API", can live with the repository instead of with each workflow. In the Memory editor, choose Primary repository.

• Which runs read it. A workflow reads the repository memory of its first connected repository only (the first in board order). Secondary repositories contribute nothing, and an unavailable first repository does not fall back to the next one. General chats without a board and external workers never receive repository memory. A caller cannot point a run at a different repository.
• Access. Organization owners and admins write repository memory. Organization members can read it while the repository's connection and approval are current. Revoking access withholds the wording from readers and runs; it does not physically erase the stored revisions.
• Pinned to the repository's identity. Each approved revision records which repository it was approved for (provider route, host, remote ID, owner and name, never credentials). If that identity changes, current and earlier wording is hidden until someone reviews new wording. Rotating the access token does not change identity. The history line shows Approved for the current repository identity when the pin matches.
• Evidence. A repository note can cite only ready knowledge sources indexed for that same repository. Private workflow, worker, organization or run evidence cannot be promoted into repository-wide notes. The evidence picker offers at most the first 100 ready sources; it does not search the whole repository index.
• Not portable. Repository memory stays out of factory versions, files, packs and blueprints. Removing the repository or its organization removes its notes, their revisions and evidence, and directly linked learning copies. Detaching the repository from one workflow only stops that workflow reading it.

Notes written before this scope existed carry no identity pin; repository wording without one stays hidden until it is reviewed again.

Shared crew memory

Open Factory settings → Memory → Crews, select a crew, and add its shared notes. The leader, members and reviewer read active crew notes during that crew’s runs. The same agent running alone or with another crew does not inherit them. Personal worker notes remain separate.

Workspace permissions govern crew notes. A person creates, edits, archives and reorders them; agent proposals cannot write into shared crew memory. The editor shows the shared context budget before individual worker notes are added. Removing a crew removes its scoped notes.

Reuse guidance with memory packs

Publish reviewed guidance in Agent marketplace → Memory packs, then install an explicit version into workspace memory. Publication alone changes no worker instructions. Installation adds independent active notes; newer versions do not overwrite them. Removing an installation archives unchanged notes and preserves your edits. See memory packs in the marketplace for version review, visibility and limits.