Compute prototypes
Table of Contents
1. Summary
The grid's work: the load, one job end to end, a failure to reproduce, the capacity planned, and what it may run.
Four prototypes answer to this group. Each one is a static page under
doc/prototypes/, opens with no build and no session, and reads mock data
only. The table below opens each one and says what it argues. Where a
prototype carries a Gemini review, the last column opens it: a review is a
generated alternative kept beside the agreed design, never instead of it.
Prototypes is the top page and the only inventory.
2. The prototypes
| Prototype | What it argues | Open it | Review |
|---|---|---|---|
| Compute journeys | A grid read as tables is a grid nobody can read: the five use cases, and every chart compute.org names, drawn from mock series at the size the real screen would give them. | prototype | none |
| Browse the grid's jobs | A paged tree of batches, workunits and results beside a details panel answers "which ones failed, and why" for each role: the Jobs tab of the compute grid screen. | prototype | Gemini review |
| Follow a job | One page answers "where is this job, what ran it, and what did it produce": the state with the outcome beside it, the runs, the files, the release and the chain back to the scheduled job. | prototype | none |
| App version | One app version of the catalogue with the release note stored beside its build: what a job pinned, what changed in it, and the packages the wrapper downloads. | prototype | none |
3. Adding a prototype
Create doc/prototypes/compute/<name>/ with an index.html, and a
prototype.css and prototype.js when it needs them. Open the page with
the links table every prototype carries, and leave its review row at
none. Add a row to the table above, with the design note beside the
prototype when there is one. Stop there: the site build finds every
prototype under this tree, so no build file names it.
A review goes at doc/prototypes/compute/<name>/review/, with an
index.html that lists its screens. The row names it, and the
prototype's review row points at it. Prototypes states the
whole method and the rules that hold for every group.
4. See also
- Prototypes — the top page: the groups, and the one way to add a prototype.
- Compute journeys — the journeys these prototypes answer.