agentleFS
MicrosoftKnown publishermicrosoft/amplifier-unified/components/AGENTS.md

amplifier-unified / components

AGENTS.md5 starsChanged todayMITView on GitHub

components/workspaces/ is the temporary authoring home for the independently buildable amplifier_workspace_metadata package. Its registration and query mechanism tests belong here; Unified retains initialization, filesystem effects, history, authority and persistence. Unified consumes only the published artifact selected into workspace-metadata-delivery/ by workspace-metadata.source.json, as the sole installed owner; do not coinstall the standalone distribution. Never edit that generated copy by hand. Author edits and publication do not refresh the app selection. This metadata boundary is not the whole workspace domain. components/outputs/ is temporarily…

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository6 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Never edit either generated delivery copy by hand.

    line 30
  2. Distinctive:

    Never edit that generated copy by hand or coinstall the standalone distribution.

    line 44
  3. Distinctive:

    Never edit the delivery copy by hand or coinstall the standalone distribution with Unified, which remains the sole installed owner.

    line 52
  4. Distinctive:

    Never edit that snapshot by hand or coinstall the standalone distribution with Unified.

    line 60
  5. Very specific:

    Read README.md and the small source record before opting into copied contents.

    line 79

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Component ownership

components/workspaces/ is the temporary authoring home for the independently buildable amplifier_workspace_metadata package. Its registration and query mechanism tests belong here; Unified retains initialization, filesystem effects, history, authority and persistence. Unified consumes only the published artifact selected into workspace-metadata-delivery/ by workspace-metadata.source.json, as the sole installed owner; do not coinstall the standalone distribution. Never edit that generated copy by hand. Author edits and publication do not refresh the app selection. This metadata boundary is not the whole workspace domain.

components/outputs/ is temporarily authored here as an independently buildable Python project. Preserve amplifier_outputs imports and its saved-body formats. Its Git/SQLite mechanism tests belong with the package; Unified retains transactions, authorization, source access, content integrity and retention. Unified consumes only the published artifact selected into outputs-delivery/ by outputs.source.json, as the sole installed owner. Never edit that generated copy by hand or coinstall the standalone distribution. Author edits and publication do not refresh the app selection. This package is not the whole resources domain.

components/portability/ is temporarily authored here as an independently buildable Python project. Preserve amplifier_portability imports and its existing worktree dependency. Its signed-journal and Git-capsule tests stay with the package; Unified retains task admission, data projection, native fencing and account probes. Unified consumes only portability-delivery/ selected by portability.source.json, which binds the exact published dependency to worktrees.source.json. Authoring and publication do not change those selected defaults. Standalone delivery selects an exact public worktrees artifact through portability/worktrees-source.json; install both selected wheels explicitly, never alongside their Unified-owned copies. Never edit either generated delivery copy by hand.

components/worktrees/ is temporarily authored here as an independently buildable Python project. Preserve amplifier_worktrees and amplifier_worktrees.git imports; Unified selects published bytes into worktrees-delivery/, recorded by worktrees.source.json, as the sole installed owner. Its real-Git mechanism tests belong here; host permission, active-task, handoff and cleanup policy remain in Unified. The author project is independent of the generated delivery copy; never edit that copy by hand or coinstall the standalone distribution.

components/publishing/ is temporarily authored here as its independently buildable Python project. Preserve its amplifier_publishing imports and existing module entrypoint. Unified consumes only the published artifact selected into publishing-delivery/ by publishing.source.json, as the sole installed owner. Never edit that generated copy by hand or coinstall the standalone distribution. Author edits and publication do not refresh the app selection. Its POSIX mechanism tests stay with the package; host authorization, policy and integration stay in Unified.

components/scheduling/ is temporarily authored here as its independently buildable Python project. Preserve its normal amplifier_scheduling import. Unified consumes only the generated scheduling-delivery/ snapshot selected by scheduling.source.json; author edits and publication do not change this default. Never edit the delivery copy by hand or coinstall the standalone distribution with Unified, which remains the sole installed owner. Follow the author project's README.

operations/ is the temporary authoring project for amplifier_operations. Its SQLite operation observations and bounded delivery/cursor tests belong here; Unified retains admission, authority, Stop and execution. The top-level amplifier_operations/ is the generated runtime snapshot selected by operations.source.json, preserving the installed and isolated-worker import path. Never edit that snapshot by hand or coinstall the standalone distribution with Unified. Independent author edits/publication do not refresh the app selection.

kernels/ is the temporary authoring project for amplifier_kernels, including its Python and Node runners and real-process mechanism tests. Unified consumes the generated top-level amplifier_kernels/ snapshot selected by kernels.source.json, preserving editable and isolated-worker import origins. Never edit that snapshot by hand or coinstall the standalone distribution with Unified. Author edits and publication do not refresh the app selection; the host retains process approval, execution, observation and recovery authority.

Web client delivery

web-client/ is a verbatim snapshot of the separate client repository selected by web-client.source.json. Maintain source, client tests and build tools in that owning repository, then refresh the whole snapshot and record together. Do not make independent fixes inside this copy. Its nested guides describe upstream development; this wrapper governs maintenance of the delivery copy.

Read README.md and the small source record before opting into copied contents. Unified assembles the selected client through scripts/web_client_build.py; ignored .build/web-client is disposable prepared source. Host/browser/producer checks and their own dependencies live in tests/web. Neither delivery nor preparation creates another client owner.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.