Skip to content

docs(openspec): launchpad parity umbrella and the dashboard cluster - #637

Merged
rubenvdlinde merged 1 commit into
developmentfrom
openspec/parity-wave-4
Sep 14, 2026
Merged

rubenvdlinde merged 1 commit into
developmentfrom
openspec/parity-wave-4

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

Opens the launchpad half of the dossiq competitor parity programme. Wave 4 of the OpenSpec phase, small-owner lane.

What is in it

  • openspec/changes/competitor-parity-2026-09/: launchpad had no parity umbrella. This one indexes what launchpad owes and records two of the cluster's eleven candidates as already shipped here, with the requirement that carries each.
  • openspec/changes/dashboards-and-who-may-see-them/: discovery cluster 12, "Dashboards, widgets and who may see them". Nine candidates built, size M. Ten requirements with scenarios: a personal layer over a shared dashboard and a one-action reset, a library of reports the product ships, a dated status report with a health rating, activity reporting gated behind a declared purpose with every read logged, a colleague activity widget filtered by what you may see, an in-widget filter that never touches the saved search, geographic trend reporting, and storage use per workspace and service.

Every candidate's competitor evidence is quoted verbatim from procest/_round4/discovery/candidates.md in ConductionNL/market-intelligence.

Two candidates recorded rather than built

  • C-reporting-14, an external page with the host allowed centrally: already shipped by iframe-embed-widget REQ-IFRAME-002, which fails closed and reads an empty allow-list as "embed nothing".
  • C-reporting-22, a dashboard scoped to the roles that may see it: already shipped by dashboards REQ-DASH-011 and REQ-DASH-013 plus role-feature-permissions REQ-RFP-001. It is the cluster's only must, and the sweep rates it against dossiq, not against launchpad.

Both are named in the umbrella so neither is rediscovered as a gap.

The dossiq half

There is no dossiq change for cluster 12 yet. dossiq needs one: it contributes its case widgets to a launchpad dashboard and declares which roles may see each one, instead of shipping a single manifest layout. Ledger row 10.1 is the composition half.

What was verified

  • openspec validate competitor-parity-2026-09 --type change --strict, exit 0
  • openspec validate dashboards-and-who-may-see-them --type change --strict, exit 0

Documentation only: no PHP, Vue, test or manifest file is touched, so no gate, lint or test run applies to this diff. No inherited findings to report.

🤖 Generated with Claude Code

Opens the launchpad half of the dossiq competitor parity programme.
Cluster 12 of the round 4 discovery sweep: nine candidates built, two
recorded as already shipped by iframe-embed-widget and dashboards.
@rubenvdlinde
rubenvdlinde merged commit f9df2f1 into development Sep 14, 2026
31 of 32 checks passed
@rubenvdlinde
rubenvdlinde deleted the openspec/parity-wave-4 branch September 14, 2026 18:22
@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/launchpad @ 99fc7cb

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
build
check-manifest
format
check-schema-l10n
composer ✅ 104/104
npm ✅ 534/534
app:check-code ⏭️
info.xml
REUSE
lockfile sync
PHPUnit ⏭️ not run for this diff — no file in this diff matches the code globs, and none carries a source extension — the heavy tier has nothing to decide about it.
Newman
Playwright ⏭️ deferred: E2E runs locally and on the promotion path only. This pull request targets development, so the suite is asked once per promotion into beta and main rather than once per push per open pull request. Run it on any branch from the Actions tab, or locally with npx playwright test.
Hydra gates

Quality workflow — 2026-09-14 18:37 UTC

Download the full PDF report from the workflow artifacts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant