← Back to Home

Run a Trial

source=external probe

Bounded, read-only evaluation: structured findings on your repo and problem statement—then continue in the repo room, hatch, and probe again. Not a promotion or admission flow.

V1 loop: probe → report + egg → repo room → hatch → next probe. Optimized for desktop/laptop browsers first.

Public examples available here

Flask

General repo structure and docs-tests-src alignment.

Use: https://github.com/pallets/flask

Memory Palace

Retrieval benchmark claim-evidence check.

Use: https://github.com/milla-jovovich/mempalace

Want your own repo reviewed? Request a Free First Probe first. FoldEngine reviews each repo/question before running anything so the output stays bounded, useful, and honest. Submitting the form does not guarantee a probe. Do not submit private repos, secrets, credentials, or sensitive project material.

Request Free First Probe Email fallback

Problem Statement

Describe the operational problem you're trying to stabilize (150–1200 characters).

Questions you can test the probe against — click any to use as your problem statement

0 / 1200 characters

GitHub Repository URL

Public repo only. We'll analyze the structure (read-only).

I understand this is analysis-only. Your code is safe. We read structure only — no modifications, no execution, no hidden calls.

Seed loop (optional). After the trial egg is fixed, run one more bounded pass (README surface, repo root index, hint alignment via GitHub API). Still read-only.

Cancel

Trial reports are read-only. Your repo is not modified. The probe is bounded analysis; if you enable the optional seed loop, read-only GitHub API calls may be used as described above—nothing is executed in your codebase.

Run a Trial

Public examples available here

Analyzing your source

Trial request not completed