Ops sheet artifact
Answer me with artifact · 2026-10-20 21:17

Ops sheet artifact

Should the ReUI deploy sheet become an Allternit artifact kind?

Yes, but as a generic Ops sheet artifact kind, not a deploy-only screen. One header with status and actions, tabs for the detail, and the same shape for deploys, servers, bot runs and Factory DAGs.

A

The reference

@FaizalSukaimi · ReUI · 2026-10-20
ReUI deploy sheet: Pipeline, Health and Logs tabs on one panel with Pause and Roll back
ReUI deploy sheet: Pipeline, Health and Logs tabs on one panel with Pause and Roll back
B

Why it works

  • The header answers "is it OK?" in one glance: name, version, status, a segmented progress bar, a timer.
  • The two actions that matter (Pause, Roll back) sit above the tabs, so they show on every tab.
  • Tabs hold the detail: steps, live logs, health charts against a baseline, changes.
  • "1 of 23" with up/down arrows moves between items without closing the sheet.
C

Where it fits in Allternit

Use Header Tabs Actions
Server Health (planned) VPS, uptime, status Health · Services · Logs Restart service
Desktop runtime / PWA deploy build id, surface Pipeline · Logs · Changes Pause · Roll back
Bot run / routine bot, trigger Steps · Logs · Usage Stop · Retry
Factory DAG dag id, team Nodes · Panes · Proof Pause · Cancel
D

How to build it

  • Add an ops kind to Artifacts v2, built from Arc tabs, badges and charts we already have.
  • Data comes from live sources, not static HTML. Server Health is the first real feed.
  • Pause, Roll back and Restart go through the existing review gates: you approve each one.
  • It ships on Desktop, the web phone layout and the PWA together, with docs.
Do not start it as a separate project

It should merge into the Server Health plan, which already waits on your 3 decisions. Two separate dashboards means two to maintain.

E

Decision

How should we start it?