agentleFS
Sign inStart free
docxologydocxology/codomyrmex/data/AGENTS.md

codomyrmex / data

AGENTS.md10 starsChanged 38 days agoMITView on GitHub

Repository-level data area for committed evidence that code and docs reference by path. It currently hosts only the archived SAIR Mathematics Distillation run records and results. - sair/ — SAIR data: runs/ (three archived 2026-03-16 run JSONs) and results/ (initial_test.json). - README.md — human signpost. - Written and read by the SAIR tooling in scripts/sair/ (run_sair.py, evaluate.py, analyze_results.py); see sair/AGENTS.md for which paths are defaults and which must be passed explicitly. - No code under src/codomyrmex/ reads from this directory.…

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    No code under src/codomyrmex/ reads from this directory.

    line 21
  2. Very specific:

    Run JSONs are generated evidence — do not hand-edit.

    line 26

≈ “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

AGENTS.md — codomyrmex/data

Purpose

Repository-level data area for committed evidence that code and docs reference by path. It currently hosts only the archived SAIR Mathematics Distillation run records and results.

Key Files

  • sair/ — SAIR data: runs/ (three archived 2026-03-16 run JSONs) and results/ (initial_test.json).
  • README.md — human signpost.

Dependencies

  • Written and read by the SAIR tooling in scripts/sair/ (run_sair.py, evaluate.py, analyze_results.py); see sair/AGENTS.md for which paths are defaults and which must be passed explicitly.
  • No code under src/codomyrmex/ reads from this directory.
  • Parent: ../README.md · Root contract: ../AGENTS.md

Development Guidelines

  • Run JSONs are generated evidence — do not hand-edit; regenerate through the SAIR pipeline (scripts/sair/).
  • Large/bulk data belongs in data/ only when referenced by deterministic code; transient artifacts belong in output/ (git-ignored at every depth).
  • The SAIR problem sets (normal.jsonl, hard.jsonl) are not committed; scripts/sair/download_data.py fetches them from Hugging Face only when live mode is enabled (--live or RUN_LIVE_SAIR=1).
  • Give any new subdirectory its own README.md and AGENTS.md, matching the existing sair/ tree.

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.

Check your setup, free