{
  "schema": 1,
  "name": "Project roadmap",
  "description": "Seed board for a project created from this template (website research/analysis project). Every entry is one layer of the build; the Startup Creator materialises them as board cards (repository issues) on the first turn, then hands the user over to My Boards. `column` uses the W4C board's real grouping (priority + done).",
  "columns": [
    {
      "id": "high",
      "name": "High Priority"
    },
    {
      "id": "low",
      "name": "Low Priority"
    },
    {
      "id": "none",
      "name": "No Priority"
    },
    {
      "id": "done",
      "name": "Done"
    }
  ],
  "tasks": [
    {
      "icon": "🧭",
      "title": "Plan & scope — routes, data model, acceptance criteria",
      "column": "high",
      "labels": [
        "High Priority"
      ],
      "body": "Turn `SPEC.md` into `docs/PLAN.md`: the route/screen map, the data model and the acceptance criteria.\n\nDeliverables: `docs/PLAN.md` committed, every route and entity named, decisions locked.\nAcceptance: the plan names a proof command or a runtime check for every later layer.\nRef: `SPEC.md`, `project-bootstrap` skill."
    },
    {
      "icon": "🎨",
      "title": "Design (mockups) — design system and screens on the canvas",
      "column": "high",
      "labels": [
        "High Priority"
      ],
      "body": "Design the UI/UX on the OpenPencil canvas (`/design-studio`, agent `w4c-design`): design tokens plus labelled artboards for the shell and every route, with loading/empty/error variants.\n\nDeliverables (evidence): canvas document name + node ids (image export as backup); tokens committed under `docs/design/`.\nAcceptance: the canvas document covers every route in `docs/PLAN.md`; AA contrast checked.\nRef: `SPEC.md`, `stack-*-quality` skill."
    },
    {
      "icon": "🗺️",
      "title": "Architecture diagram — architecture, ERD and key flows",
      "column": "high",
      "labels": [
        "High Priority"
      ],
      "body": "On My Diagrams (`/diagrams`, agent `w4c-diagram`) draw the architecture, the ERD and the key flows, derived from this card's task description and `docs/PLAN.md`.\n\nDeliverables: a saved architecture diagram and an ERD of the data model, plus a sequence diagram for the main user flow. Add only the elements that belong to the task to the diagram context.\nAcceptance: the diagrams reload without loss and match the plan; the ERD lists the same entities as `SPEC.md`.\nRef: `docs/PLAN.md`, `/diagrams`."
    },
    {
      "icon": "🗄️",
      "title": "Database & forms — tables, relations, migrations, seed",
      "column": "high",
      "labels": [
        "High Priority"
      ],
      "body": "Implement the data layer: schema, relations, migrations and seed data (agent `w4c-db` for the W4C Data Tables + forms on `/db-forms`, `w4c-code` for in-repo migrations/ORM).\n\nDeliverables: the tables/enums from `SPEC.md` with correct nullability and indexes; an idempotent seed; the data-entry forms created and published.\nAcceptance: migrate + seed run clean on a fresh clone; a public form token accepts a submission without login; aggregate queries return hand-checked totals.\nRef: `SPEC.md`, `/db-forms`."
    },
    {
      "icon": "⚙️",
      "title": "Backend & API — services, endpoints, auth",
      "column": "low",
      "labels": [
        "Low Priority"
      ],
      "body": "Implement the services and endpoints the screens call, plus authentication and authorisation (agent `w4c-code`).\n\nDeliverables: the API routes behind every screen action; server-side authorisation on every mutation; validation and error envelopes.\nAcceptance: endpoints answer with the documented shapes; unauthorised and cross-user requests are rejected server-side (401/403); `.env.example` lists every required variable.\nRef: `docs/PLAN.md`, `SPEC.md`."
    },
    {
      "icon": "💻",
      "title": "Frontend (code) — generate the screens",
      "column": "low",
      "labels": [
        "Low Priority"
      ],
      "body": "Generate the frontend: the screens from `SPEC.md` wired to the API, following the design system from the canvas (agent `w4c-code`).\n\nDeliverables: every route implemented with loading, empty and error states.\nAcceptance: build + lint + typecheck pass; each route renders with seeded data.\nRef: `docs/PLAN.md`, `SPEC.md`."
    },
    {
      "icon": "🛡️",
      "title": "Admin panel — guarded back-office",
      "column": "low",
      "labels": [
        "Low Priority"
      ],
      "body": "Build the guarded admin/back-office (agent `w4c-code`): dashboard, CRUD over the core entities, lists with filters and audited state transitions.\n\nDeliverables: `/admin/*` routes; destructive actions behind a confirmation dialog; role checks server-side.\nAcceptance: a non-admin request to every admin route/mutation is rejected server-side.\nRef: `SPEC.md`."
    },
    {
      "icon": "📊",
      "title": "Control Panel — dashboard pages and widget data binding",
      "column": "low",
      "labels": [
        "Low Priority"
      ],
      "body": "Build the operations dashboard on the Control Panel (`/control-panel`, agent `w4c-panel`): KPI tiles, charts, tables and the board, with widgets bound to real data.\n\nDeliverables: at least one page per audience, widgets bound through data binding with an explicit empty state.\nAcceptance: widgets show real data or an empty state (never an endless spinner); no horizontal scroll at 390×844; the page can be shared publicly and revoked.\nRef: `/control-panel`, `WIDGETS.md`."
    },
    {
      "icon": "🔀",
      "title": "Workflows — automation and CI",
      "column": "low",
      "labels": [
        "Low Priority"
      ],
      "body": "Author the automation flows (agent `w4c-workflow`) and keep the CI workflow shipped with the template.\n\nDeliverables: workflow YAML under `.w4c/workflows/` (and/or in the Workflows module), run history visible.\nAcceptance: a test trigger actually performs its action (task/email/log); a failing node is reported as failed, not a silent success.\nRef: `/workflows`, `.w4c/workflows/`."
    },
    {
      "icon": "🚀",
      "title": "Deploy — containers, compose, public URL",
      "column": "none",
      "labels": [],
      "body": "Deploy the product (agent `w4c-server`): connect a server, create docker-compose for the app and its API, build and run the containers, expose the public URL.\n\nDeliverables: compose file committed; running containers; public URL.\nAcceptance: the public URL serves the app; a container restart restores the service; container logs are readable from the Server Console.\nRef: `/servers`, `/servers/console`."
    },
    {
      "icon": "✅",
      "title": "Quality & delivery — tests, docs, accessibility, definition of done",
      "column": "none",
      "labels": [],
      "body": "Close the build (agents `w4c-code` / `w4c-workflow`): unit tests, end-to-end tests, README quickstart, `.env.example`, accessibility pass.\n\nDeliverables: unit tests for the domain rules; E2E for the happy path and the guard; CI runs install + lint + typecheck + test + build.\nAcceptance: the CI command is green locally; the README quickstart works on a clean clone; `.env.example` lists every secret; keyboard/contrast checked.\nRef: `SPEC.md`, `stack-*-quality` skill."
    }
  ]
}