Phanes wraps hexa-lang's OUROBOROS engine — the loop goal, falsifier, saturation, run in rounds with a per-round honesty gate — as a hosted web product. A company brings a measurable objective and a verifier; Phanes drives the engine against it and returns a verified, provenance-tracked discovery catalog. Their own private echoes.
The engine is not a black box. Every round is a goal proposed, a falsifier fired against it, and a saturation check — and every step is written to an audit trail you can inspect. What Phanes sells is not a promise that your objective is met; it is a verified record of exactly what the engine found and exactly how hard it tried to break it.
↳ Drive the full OUROBOROS loop from the web.
Phanes connects the seed, the rounds, and the saturation check into one hosted workflow — the same drill engine that powers hexa-lang's own discovery cycles, behind an authenticated control plane.
↳ A live dashboard, no page reloads.
Submit jobs and watch them progress through an HTMX-polled dashboard. Polling auto-stops the instant a job reaches done or failed — the interface knows when to be quiet.
↳ Per-tenant isolation across every job.
Hybrid multi-tenant isolation — a per-job home-jail now, a first-class data-dir boundary upstream. Session cookies and bearer tokens gate every authenticated surface.
↳ Bring your own verifier.
The seed format is open and the verifier is just a script that exits zero on PASS. Wire any measurable objective into the loop without forking the engine.
Phanes operates under scope B: the tenant-supplied verifier is the sole authority for objective-met, and Phanes never claims a result the verifier did not pass. It is built on hexa-lang — OUROBOROS cycle h36 complete, a bit-stable self-host fixpoint, tier-1 codegen-correctness verified — and inherits its real-limits-first honesty rule. No over-claim, no project-completion promise. Saturation is the only hard stop.