fulcra-harness-dashboard

Files (9)

• SKILL.md
• refresh_harness_dashboard.cpython-311.pyc · scripts/__pycache__/
• refresh_harness_dashboard.py · scripts/
• dashboard-data.json.template · templates/
• harness-dashboard-components.css.template · templates/
• harness-dashboard-components.js.template · templates/
• harness-dashboard-theme.css.template · templates/
• noindex-head.html.template · templates/public/
• publish_surge.sh.template · templates/

SKILL.md (first lines)

# Fulcra Harness Dashboard

This is an **adaptation of `fulcra-project-dashboard`**, not a replacement
for it. Start by following that skill's static-triad/dashboard setup. Then
apply only the control-harness-specific additions below.

## Purpose

A project dashboard answers “what has the team done?” A harness dashboard
also answers:

- Which milestone is current, passed, blocked, or queued?
- What did the most recent Generator/Evaluator run prove?
- Is the current issue a user decision, a genuine escalation, or transient
  provider capacity?
- What is the concise “where we are / where we're going / next bearing”
  state?
- Did the milestone PR merge, remain reviewable, or fail evaluation?

## Required durable Workspace inputs

Read only the control harness's durable artifacts:

```text
team/<team>/status-summary.md
team/<team>/milestone-progress.md
team/<team>/progress.md
team/<team>/decision/
team/<team>/escalation/
team/<team>/artifact/*verdict*.md
team/<team>/member/*/progress.md
```

Do not infer status from Discord history, transient local model output, or
scheduler “completed” status alone.

## Base setup

1. Invoke `fulcra-project-dashboard` to build the base static triad and its
   manager-oriented layout.
2. Copy `templates/dashboard-data.json` as the curated data contract and
   use `scripts/refresh_harness_dashboard.py` to refresh it from downloaded
   `status-summary.md` and `milestone-progress.md`.
3. Copy `templates/harness-dashboard-components.js` and
   `templates/harness-dashboard-components.css` into the base dashboard's
   public static-triad assets. Add a root element such as
   `<section id="harness-dashboard"></section>` and call
   `renderHarnessDashboard(root, data)` after the base dashboard loads the
   curated JSON. The component supplies actual rendering for the flight
   plan, checkpoint, interactive run timeline, previous-run context, and
   Open Items; it deliberately does not replace the base dashboard shell.
4. Keep the base dashboard's executive summary, logs, progress, timeline,
   and activity visuals where useful; these adaptations make those views
   control-loop aware.

## Required project theming (restrained)

Before the first dashboard publication, establish a small project-specific
visual theme. A harness dashboard must not look like an unmodified generic
admin page, but theme must improve orientation rather than compete with
operational data.

Required minimum:

1. a project-specific dashboard title/subtitle and section copy;
2. a restrained palette (accent, soft accent, ink, paper/background) tied
   to the project domain;
3. one small motif or visual cue (symbol, border treatment, or compact
   header mark) relevant to the project;
4. readable contrast and unchanged access to milestones, runs, decisions,
   and escalations.

Start with `templates/harness-dashboard-theme.css`. Copy it after the base
`fulcra-project-dashboard` CSS and replace its theme placeholders. Do not
add large decorative imagery, autoplay animation, or third-party visual
assets merely to satisfy this requirement. If the project already has a
recognized identity/theme, reuse it; otherwise ask the user for a concise
vibe before rendering.

The chosen theme must be recorded in the curated dashboard configuration or
project status so later agents refresh rather than accidentally reset it.

## Harness-specific panels

### 1. Flight plan

Render every milestone with `passed`, `current`, or `queued` state from
`milestone-progress.md`. Do not leave a previous milestone visually current
just because a static dashboard file was not refreshed.

### 2. Run timeline

Render each terminal run as a dated marker with:

- milestone ID;
- PASS / escalation / decision-required state;
- short evidence summary;
- selected-run detail plus the previous two run summaries;
- horizontal scrolling and zoom for growing history;
- default scroll position at the latest runs.

### 3. Current checkpoint

Prominently render the durable `status-summary.md` sections:

```text
Where we are
Where we're going
Next bearing
```

Include retry mode (`manual` vs. bounded automatic) so a viewer does not
misread an unattended retry as a human decision.

### 4. Open items

Show only current unresolved items:

- open user decision requests from `team/<team>/decision/`;

From fulcradynamics/community-skills, MIT.

More from fulcradynamics/community-skills