Skip to content

docs(openspec): re-scope the three fat umbrellas onto the one engine - #1815

Merged
rubenvdlinde merged 1 commit into
developmentfrom
spec/one-engine-rescope-three-umbrellas
Sep 2, 2026
Merged

docs(openspec): re-scope the three fat umbrellas onto the one engine#1815
rubenvdlinde merged 1 commit into
developmentfrom
spec/one-engine-rescope-three-umbrellas

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

What

Spec surgery only: openspec/changes/ and nothing else. No lib/, no src/, no tests/.

Three umbrella changes sat unstartable and, it turns out, already done:

Umbrella Live state Reality
visual-flow-orchestration 0/55 Archived twin archive/2026-07-15-visual-flow-orchestration holds the SAME 55 boxes at 43/55 with per-task evidence (PR #209); FlowRunnerService, FlowAction, FlowsController, the schemas and the flow rule arm are all at HEAD
nextcloud-event-hub 0/43 Archived twin at 30/43; the five NC listeners, jsonlogic dialect, subscription action/retryPolicy and family actions are at HEAD
hitl-approval-rule-action 0/42 Archived twin at 31/42 (PR #181); ApprovalService, the sweep, the schema and the Approvals UI are at HEAD

The wave-3 spec commit (46dfa49, 2026-07-15 19:00) created these as fresh changes; each was implemented and archived within hours the same day, and the live copies were left standing at zero, double-counting ~140 checkboxes of shipped work.

Each umbrella is rewritten in place (not moved — a rename would detonate every diff-scoped gate and break 70 live @spec tags) as a superseded redirect with a disposition table, following the opencatalogi#1393 pattern. hitl-approval-rule-action keeps design.md + specs/ and nextcloud-event-hub keeps specs/ as anchor targets; everything removed survives verbatim in the archived twins.

Successors

Flow-shaped scope goes to the OR engine, not to new app-local machinery:

  • integriq-flow-nodes (ready) → retire-integriq-flow-schema (wave 3, already authored: schema+runner retirement, steps-to-graph migration, prune) → with flow-native-synchronization (18/19) continuing.
  • Approval expiry/outcomes ride hitl-on-shared-tasks (first PR feat(approvals): mirror every HITL approval into the shared OpenRegister task service #1812 merged) onto OR TaskService; future approval features target TaskService/TaskSequenceService.
  • New, agent-ready: approvals-verification-pack and nextcloud-event-hub-verification (the archived twins' honestly-unticked residue: e2e, Newman, docs, plus the Tables/Forms class-name spike that can invalidate two shipped listener families).
  • New, gated on integriq-flow-nodes: nc-events-start-or-flows — a matched subscription starts an OR flow run, so NC events reach the engine instead of growing a fourth app-local action kind (delivery seam context: feat(events): ADR-041 delivery seam for sibling-app outbound deliveries #1810).

Verification

  • npm run check:specs: identical verdict on this branch and on pristine origin/development (the one FAIL is the environment-shaped ajv/schema-resolution fallback, untouched by this diff).
  • Hydra gates --scope-to-diff vs origin/development: the same 5 pre-existing failures on this branch and on pristine development, byte-identical; this diff adds none.

🤖 Generated with Claude Code

visual-flow-orchestration, nextcloud-event-hub and hitl-approval-rule-action
sat at 0/55, 0/43 and 0/42 while identical archived twins (2026-07-15) hold
the same task lists checked with evidence and the code sits at HEAD: the
wave-3 spec commit recreated changes that shipped the same evening. Each is
now a superseded redirect with a disposition table, retired in place so no
path breaks and no @SPEC anchor dangles (hitl keeps design.md + specs/,
event-hub keeps specs/ — 70 live tags point there).

Successors: flow scope routes to integriq-flow-nodes,
retire-integriq-flow-schema and flow-native-synchronization; approval expiry
rides hitl-on-shared-tasks (OR TaskService); the honest residue becomes
approvals-verification-pack and nextcloud-event-hub-verification (both
agent-ready), plus nc-events-start-or-flows to point NC events at OR flows
instead of a fourth app-local action surface.
@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/integriq @ 2471080

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
build
build
check-specs
test-l10n
format
check-schema-l10n
check-l10n-js
composer ✅ 141/141
npm ✅ 537/537
app:check-code ⏭️
info.xml
REUSE
PHPUnit
Newman
Playwright ⏭️ deferred — runs on the promotion into beta/main, not on a pull request into development
Hydra gates

Quality workflow — 2026-09-02 13:30 UTC

Download the full PDF report from the workflow artifacts.

@rubenvdlinde
rubenvdlinde merged commit e9b2587 into development Sep 2, 2026
52 checks passed
rubenvdlinde added a commit that referenced this pull request Sep 2, 2026
…ges (#1820)

Each of these live change dirs was a 0-ticked resurrection of work already
implemented and archived in the 2026-07-14..16 window (verified per dir
against code at HEAD). Rewritten as superseded redirects with disposition
tables per the PR #1815 pattern: retired in place, no renames, every live
@SPEC anchor file and heading kept.
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