agentleFS
Sign inStart free
docxologydocxology/template/.github/actions/upload-readiness-shards/AGENTS.md

template / upload-readiness-shards

AGENTS.md20 starsChanged 2 months agoApache-2.0View on GitHub

README.md defines the three explicit inputs and supported transport roles. The action runs the Source-owned DATA checker before invoking the existing pinned upload-artifact action. It does not construct a Source context, runtime provider grant or completed-original capability from an index. Keep every ordinal shard path and conditional count aligned with the bounded checker. Preserve all per-file/archive, decoded-byte, shard, member and whole transport caps. Do not fall back to a first-page artifact census, overwrite a conflicting index or infer acceptance from…

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

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep every ordinal shard path and conditional count aligned with the bounded checker.

    line 8
  2. Distinctive:

    Keep failed evidence separately named and retain the genuine signed process failure.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 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

Readiness shard upload contract

README.md defines the three explicit inputs and supported transport roles. The action runs the Source-owned DATA checker before invoking the existing pinned upload-artifact action. It does not construct a Source context, runtime provider grant or completed-original capability from an index.

Keep every ordinal shard path and conditional count aligned with the bounded checker. Preserve all per-file/archive, decoded-byte, shard, member and whole transport caps. Do not fall back to a first-page artifact census, overwrite a conflicting index or infer acceptance from successful upload. Independent collectors authenticate exact hosted producer, run, revision, artifact IDs, digests, sizes and full bounded pagination before using retained bytes.

Keep failed evidence separately named and retain the genuine signed process failure. The failure schema and role may never substitute for a native acceptance index or complete candidate handoff. The original operation deadline is not reset by diagnostic packing or upload.

Maintain the parent action contract, this doc pair and resolving links. Action pins, caller permissions and Source acceptance predicates stay under their existing contracts; run actionlint after action edits.

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.

Reviews can't be read right now.

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.

Check your setup, free