Skip to main content
Where each of the three stages — ① Collect, ② Translate (standardize), ③ Agent — lives, and the two forms the code ships in. Moved here from the README in 1.4.1; the README keeps the one-line map.
Two forms, and they want opposite things. The PyPI package is a LIBRARY and is meant to be small enough that nobody has to think about it: pip install mirobody is 2 packages, 67 MB — the entries above the documents/ line, on numpy. [parse] adds document reading, [agent] the harness as a library; [app] is everything, and the only thing that installs it is requirements.txt, because the Docker application is git clone && ./deploy.sh and never a pip install. Machine-enforced, not documented: six import-linter contracts hold the lines — the library layer imports nothing but numpy, the engine never imports the agent layer, and collect and translate each have one front door — and lint-imports fails the build. A separate gate, scripts/check_wheel_data.py, keeps the bundle-build passes and the v2 semantic pipeline — 19,000 lines nobody who installs the package can run — out of the artifact. → Architecture · CONTRIBUTING.md