Reasoning rail
Run strategy questions through the same internal rail.
Some jobs are written prompts, tradeoff notes, or planning questions. This page keeps them on the same run and artifact rail as the code-facing work.
Run Control
Queue input and run a job
Active Thesis
Philosophy
Use this page for internal questions, decision docs, or structured reasoning when you want the output stored like any other job.
- treat written reasoning as a first-class job type
- keep job ids, traces, and artifacts consistent with the code-facing pages
- leave room for rubric-based evaluation or follow-up tooling later
- Expected output
- Written response artifact with trace metadata and any attached notes.
- Input rail
- presign -> upload -> enqueue -> poll
- Input shape
- single file, multi-file bundle, and optional inline notes
- Backend direction
- Rust gateway, job workers, artifact processors, later terminal adapters
Job State
Job state and artifacts
Stage files, paste notes if needed, then run a job through the gateway.
Artifacts
- No artifacts yet.