Actions board · process doc

A — Architecture (single root)· non-negotiable principle

PHASES is the single root. The board content (phases, tasks, owner, app, link) lives in one constant inside the page script. D1 stores nothing but the ticks. render() derives everything shown from PHASES plus the tick map.

            ┌──────────────────────────────┐        ┌──────────────────────────┐
            │  PHASES (page constant)      │        │  D1 board_state          │
            │  phases[] · tasks[]          │        │  board_key = 'actions'   │
            │  id · name · owner · app     │        │  item_key = task id      │
            │  link · label                │        │  value_json = {done}     │
            └──────────────┬───────────────┘        └────────────┬─────────────┘
                           │ derives                             │ ticks
                           └────────────────┬────────────────────┘
                                            ▼
                                     ┌─────────────┐
                                     │  View 1     │
                                     │  Board      │
                                     └─────────────┘

D1 persistence: one row per item under board_key = 'actions' in board_state, written through /api/admin/board-state. Content changes (a new task, a renamed phase) are code changes deployed with the page; only ticks are data.

B — Data model· JSON schema

B.1 PHASES (page constant)

[
  {
    num: '01', name: 'Find prospects', want: 'I want new names in the pipe.',
    tasks: [
      { id: 'find-01',              // D1 primary key, stable, never renamed without a migration
        name: 'Source new prospects',
        owner: 'Claude' | 'AL' | 'Robot',
        app: 'Notion',               // where the task happens
        link: 'https://…' | '/page', // what to open
        label: 'Prompt 01' },        // chip text
      …
    ]
  },
  …
]

Wired on byCaliber today: five phases, no task yet.

B.2 Tick (D1 table board_state)

{ board_key: 'actions', item_key: 'find-01', value_json: '{"done":true}', updated_at: 'YYYY-MM-DD HH:MM:SS' }

value_json is coerced server-side to { done: bool }: the endpoint rejects any other shape so the column never becomes a junk drawer.

B.3 Custom chain

None. Order on the board is the order of PHASES and of each tasks array. No arrows, no triggers.

B.4 Authoring conventions

• Ids are keys. <phase>-<nn>, lowercase, url-safe (KEY_RE in the endpoint). Renaming one orphans its tick.
• One intent per line. A task answers "I want X" with what to open, who does it, where.
• Owner is the one who acts. AL runs it, Claude is asked to run it, Robot means a cron does it.

C — View 1 (Board)· the only view

Purpose. See the whole pipeline in one column and tick items off. Structure edits happen in the page source, not in the UI.

C.1 Layout

• Phases stacked vertically (section.bf-phase on byForja, section.bc-phase on byCaliber), head = number, name, "I want" line, done counter.
• One row per task: round checkbox, name, owner chip, app chip, link chip (external links open in a new tab).
• A phase without tasks shows "No task wired yet for this phase." (shared JS, 2026-09-10).

C.2 Sub-actions

None. A task is the smallest unit.

C.3 Editor modal

None. Edit PHASES in public/lf-cross-platform-content.html and deploy.

C.4 Config buttons

One link chip per task (link + label). No PROMPT / URL / FINDER / OVERLAY families.

D — View 2 (Run)· not present

Not present on this board. The board is its own run view: the ticks are the run, there is no batch or wave projection.

E — View 3 (Gantt)· not present

Not present on this board. No cell chain, no arrows, no swimlanes.

F — Synchronization· reference contract

F.1 Storage

F.2 Visibility

Everything is on the one view. The status line (top right) shows done / total and the last sync word: saved, synced, or Not saved · reason in red.

F.3 Action → consequences

• Tick: optimistic paint, checkbox disabled while the POST is pending, revert + red status if D1 refuses.
• Reload / tab focus / visibility change: GET ?board=actions, state rebuilt from scratch so a tick removed in another tab disappears here too; pending writes are preserved.

F.4 Positioning model

None. Order = source order.

F.5 Save guard

Per-item rows make the merge happen server-side: tab A ticking find-01 and tab B ticking close-02 touch different primary keys, both survive. No version token, no 409 needed.

F.6 Per-view memory

None (no localStorage by design).

G — Color code· owner + link

• Owner chip: AL = brand accent, Claude = violet, Robot = grey (ownerClass()).
• App chip: ink, no fill.
• Link chip: amber, "↗" appended on external links.
• Done: name struck through, ink faint; filled dot on the checkbox.

H — Context menus (right-click)· not present

None on this board.

I — Tracked runs (videos in production)· shared widget

/videos tracks runs in D1 video_runs (same API as EO: /api/admin/video-runs). On byCaliber no process board feeds the run steps yet (BOARD_SOURCES is empty in the page), so a run tracks its label, ISO week and A→Z duration and shows "No process board wired on this brand".

J — Files, endpoints, D1 stores· where to look

J.1 Source files

J.2 API endpoints

J.3 D1 stores

K — Deployment workflow· non-negotiable

cd ~/Projects/bycaliber-tools
# 1. Inline JS syntax validation (anti page-stuck-at-loading)
node -e "const fs=require('fs');const html=fs.readFileSync('public/lf-cross-platform-content.html','utf8');const scripts=[...html.matchAll(/<script>([\s\S]*?)<\/script>/g)];scripts.forEach((m,i)=>{try{new Function(m[1]);console.log('script',i,'OK')}catch(e){console.log('ERR:',e.message)}})"

# 2. DEPLOY (repo guard → mobile check → pages inventory → stamps → wrangler → smoke → auto-commit)
npm run deploy:prod

The deploy:prod script chains: scripts/repo-guard.sh → scripts/mobile-check.py → scripts/pages-inventory.js → scripts/stamp-pages.js → wrangler pages deploy public --project-name=bycaliber-tools --commit-dirty=true → scripts/smoke-test.sh → scripts/auto-commit-after-deploy.sh. D1 migrations are not part of the chain: apply 0004 / 0005 / 0006 by hand.

L — Recent changelog· updated at each iteration

2026-09-10 (rule 15 parity)

• Board shipped on the byForja template with the five phases and no task: each phase shows "No task wired yet for this phase." until ids are added to PHASES.
• Migration 0004 (board_state, copied from byForja 0008), 0005 (weekly_steering, steering_notes), 0006 (video_runs); apply with wrangler d1 migrations apply bycaliber --remote before first use.