Standup board

Standup board — a demo bundle for the ADI Store

One screen that answers the only question a standup ever asks: what moved since yesterday. Every agent that finished a run in the last day gets a line — what it was asked for, what it shipped, and how long it took.

It is here to be read as much as to be run. It is the example of a bundle that carries a dashboard: a frontend and a backend that ADI serves for you, on a hostname of their own. Install it with a click from the ADI Store, or:

adi-mono marketplace install store/standup

What makes this a bundle

dashboards/
  standup/
    frontend/
      index.html          # the shell ADI keeps up to date for you
      index.ts            # the entry point, also generated and kept current
      modules/standup.ts  # YOUR code — migration never touches this
    backend/
      index.ts            # the entry point
      routes/standup.ts   # YOUR code

The split matters and is the one thing to copy: modules/ and routes/ are yours, and the three entry points are ADI's — it rewrites them in place when its own templates move on, which is how a shell fix reaches dashboards that already exist. An installed dashboard marks them --skip-worktree, so git status in your copy shows only your own work.

What it does not do

It reads the runs your machine already has. It writes nothing, it has no settings, and it reaches no network. And installed is not started: it arrives inert, on a hostname reserved but not served, until you press Start — the panel's Dashboards page, or adi-mono marketplace start <id>.

Publishing one of your own

1. adi-mono dashboards create <name>, write your panel in modules/ and your routes in

routes/.

1. Push the dashboard's directory as dashboards/<name>/… at the root of a repository — without

config.toml, .adi/ or node_modules/, which belong to the installing machine.

1. Take the commit (git rev-parse HEAD) and add an entry to a marketplace manifest naming that

repository and that full 40-hex commit.

The rules are in docs/marketplace.md; how to write the dashboard itself is in guides/dashboards.md.