DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to inspect saved proof artifacts from the offline math run with Effective Auto Research EAR

Run the offline math fixture to see proof checks, rejection and saved manuscript files.

  • Research
  • Intermediate
  • 30 minutes
  • From the README
  • Any agent

Who it is forA mathematician or developer who wants to see how the AutonomousMath engine records its work before using a live backend.

The problemLive math runs need a configured backend, so it is hard to learn the artifact layout and review flow first.

The outcomeA workspace with a labeled offline demo run showing rejection, revision and saved math artifacts, with accepted set to false.

What you need first

  • Python 3.10 or newer
  • git, to clone the repository
  • For live research only: an authenticated Codex or Claude setup and the module dependencies described in docs/getting-started.md

Steps

  1. Clone the repo and run cd EAR from the project root.
  2. Run python3 -m ear math run --offline --workspace workspaces/math-demo --episodes 1
  3. Run python3 -m ear math status --workspace workspaces/math-demo
  4. Open the saved artifacts in workspaces/math-demo and confirm the run is labeled offline_demo with accepted=false.
  5. Read autonomousmath/docs/ENGINE_DESIGN.md to map each saved artifact to its role in the review gate.

Prompt for your agent

In the repo liyingze07-svg/EffectiveAutoResearch-EAR-, run `python3 -m ear math run --offline --workspace workspaces/math-demo --episodes 1` and then `python3 -m ear math status --workspace workspaces/math-demo`. Report the status output and the saved artifact list. Verify that the run is labeled offline_demo and accepted=false before saying anything about its contents.

Caveat. The offline fixture is a demonstration only, so its output is not a completed research result and does not show what a live backend would produce.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page