Skip to content

dashboard.md

Latest commit

 

History

History
40 lines (28 loc) · 2.99 KB

dashboard.md

File metadata and controls

40 lines (28 loc) · 2.99 KB
Raw

dashboard - the portfolio view

Enter when: the FDE runs several customers and asks "where am I across everything?"

Read per engagement: reality.md, brief.md, success.md, risks.md, decisions.md, delivery.md, stakeholders.md. Never terrain.md (too large) or trust-profile.md (sensitive - stakeholder signals live in stakeholders.md).

The visual artifact is rendered by code, not by you. fde dashboard reads every .fde/ folder and writes a self-contained fieldbook.html - deterministically, offline, at zero token cost. Your job is the judgment the render can't do: which engagement gets tomorrow morning, and why.

Method (you do this work)

  1. First move: fde status - instant heuristic triage (trust-first ordering) across every engagement. Use it as the index; then deep-read only the folders that are red/amber or that the FDE asks about, and apply the full card method below.
  2. Find the engagements: ~/fde-engagements/*/.fde/ (primary) · workspace ./.fde/ if present · paths the FDE names. Read each folder separately - never merge two customers.
  3. Per engagement, read the card the way a human would:
    • Name, phase, week
    • Real problem (reality.md) vs original brief (brief.md)
    • Definition of success
    • Top active risk
    • Last significant action + next step
    • Value delivered so far
    • Trust signal - the most important row: green (no adverse signals) / amber (a stakeholder gone quiet or routing around the FDE) / red (escalation or explicit concern). Technical progress on a red-trust engagement is wasted until trust is addressed.
  4. Triage order: red trust first, then overdue risks, then stalled delivery. Say which engagement gets tomorrow morning and why.
  5. Refresh the visual: run fde dashboard to (re)generate fieldbook.html (defaults to ~/fde-engagements/fieldbook.html). It is a deterministic render of the .fde/ markdown - never hand-write HTML, never paste a model-built page. The session-end hook also refreshes it automatically when an engagement moved, so it is current next time the FDE opens it.

Sparse data: the render shows what exists and pads nothing. An empty field honestly shows what hasn't been captured.

Artifact

fieldbook.html - generated by fde dashboard, never hand-maintained. One file, opens in a browser, works offline, <private> notes redacted. Portfolio grid on top (a card per client: trust, phase, next action, top risk); click a card to drill into that engagement's full memory below.

Checkpoint

One paragraph to the FDE: the portfolio in red/amber/green, the single most urgent item, and what it costs to ignore it this week. Offer to open the fieldbook (fde dashboard --open).

Principles

  • The render is deterministic and free; the judgment is yours.
  • Read what's there; invent nothing.
  • Trust signal outranks technical progress.
  • One file, opens in a browser, works offline - and never leaks <private> notes.
  • Thin data is information, not a gap to fill.