fabi/PiCloud
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: reconcile roadmap with shipped v1.2 Workflows track

Browse Source 
The blueprint, CLAUDE.md, and the groups design doc still described the
Workflows track as "not-yet-started" and listed a per-app `materialized`
column as deferred — both stale. Workflows shipped M1–M6 (DAG execution +
conditional `when`, nested sub-workflows, durable orchestrator,
`workflow::start` SDK + admin API + `pic workflows`, dashboard DAG +
run-history; migrations 0071/0072), and D1's `materialized` column shipped.

Update the status lines to mark Workflows shipped (leaving §9.4 service
interceptors as the one remaining Workflows-track item and cluster mode as
next), bump the "migrations through 0070" note to 0072, and drop the stale
`materialized`-deferred line. Docs-only.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
MechaCat02
2026-07-13 20:03:12 +02:00
parent 3da70a66c7
commit fcd9451ab1
3 changed files with 19 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/design/groups-and-project-tool.md
View File

@@ -8,7 +8,8 @@
> scripts/modules + extension points, nested tree apply, §4.5 trigger/route templates, §11.6 shared
> collections, §7 multi-repo ownership, §3 M3 (now server-authoritative) approval gate, §6 group
> create/reparent — plus the Track A closeout and the 2026-07-11 audit remediation. **v1.2 Hierarchies
> is complete;** only multi-node cluster propagation and the separate Workflows track remain. NB: §11's
> is complete;** the separate Workflows track has since **shipped** (M1–M6), leaving only multi-node
> cluster propagation and §9.4 service interceptors. NB: §11's
> own Phase 1–6 numbering is local to this initiative and is **distinct from the
> blueprint product-phase numbering** — "Phase 3" here = group-inherited config, not the blueprint's
> admin-auth phase.
@@ -416,9 +417,9 @@ Two distinct constraints:
> reseal, no new schema column). All descendant email webhooks validate against the one group HMAC secret;
> each copy has its own `trigger_id` / inbound URL. A group email template whose group secret is unset
> fails apply hard (same as the app path). Pinned by `tests/stateful_templates.rs` + the
> `stateful_templates` journey. **Deferred:** a per-app `materialized` column in `pic triggers ls --app`;
> cross-owner dedup (a descendant re-declaring an identical trigger double-fires — "overlapping triggers
> coexist"); the per-app (non-shared) email secret model.
> `stateful_templates` journey. (The per-app `materialized` column in `pic triggers ls --app` shipped as
> D1.) **Deferred:** cross-owner dedup (a descendant re-declaring an identical trigger double-fires —
> "overlapping triggers coexist"); the per-app (non-shared) email secret model.
>
> **Shipped — group ROUTE templates (live, inherited).** The same live model, adapted to routes. A
> `[group]` declares a `[[routes]]` template binding a group-owned endpoint; `routes` gained a