Auracle/Docs/Web UI

Web UI

The visual front-end at http://localhost:1969/. Four Forge-related surfaces are documented below.

Overview

Houston is a server-rendered FastAPI + Jinja2 application with HTMX for in-place updates. No SPA, no client-side router. Pages are full HTML responses; interactivity is layered on top via small HTMX fragments. This keeps the bundle tiny and the surface scriptable.

Forge (API-only in v1.0)

v1.0 status In v1.0 the Forge surface is API-only. The dedicated web UI (Discover / Catalog browser / Research flow / Candidates pages described in earlier drafts of this page) is on the v1.1 roadmap. For v1.0, drive Forge entirely through the REST API or via the auracle forge CLI subcommands.

The active Forge surface today:

Action	API	CLI equivalent
List configured providers	`GET /forge/providers`	`auracle forge providers`
Browse the catalog	`GET /forge/catalog` (filter via `?verdict=&provider=&asset_class=`)	`auracle forge catalog`
Inspect one dataset	`GET /forge/catalog/{id}`	`auracle forge dataset <id>`
Get the ambient context the AI assistant uses	`GET /forge/ambient`	`auracle forge ambient`

The full schema for each endpoint is in the OpenAPI docs at https://<your-host>/api/docs. The Forge concept doc walks through the agents, scoring rubric, and cost model.

Pin / exclude / promote actions, and the agent-driven Discovery / Probe / Planner / Synthesis pipeline described in earlier drafts of this page, are part of v1.1 and not yet shipped. v1.0 ships with the catalog, ambient context, and per-dataset inspection only.