Jeffrey Smith
f9cd5bce0f
Four example workflow packages proving the engine end-to-end: - Bug Report Triage: public entry, branch routing, SLA timer - Employee Onboarding: Starlark automated stages, signoff gate - Content Approval: multi-party signoff, revision cycle loop - Webhook Notifier: http.post, connections fallback, delivery logging Demo surface at /s/workflow-demo with cards, stage diagrams, Starlark viewer, API examples, active/published status, and copyable public links. Engine fixes: started_by in automated context, sla_seconds in package installer, parseSnapshotStages for wrapped/legacy formats. Platform fixes: extension SDK boot in base.html (Preact globals + boot()), admin teams paginated response extraction, workflow adoption endpoint (POST /teams/:teamId/workflows/:id/adopt), team-admin copyable link. Review pass remains on roadmap for remaining UI polish. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
34 lines
835 B
Markdown
34 lines
835 B
Markdown
# Content Approval
|
|
|
|
Multi-party content review with quorum signoff and revision cycle.
|
|
|
|
## Features
|
|
|
|
- **Multi-party signoff** — 2 approvals required (quorum)
|
|
- **Rejection reroute** — rejection sends content back for revision
|
|
- **Review cycle** — revision stage always routes back to review (loop)
|
|
|
|
## Stage Flow
|
|
|
|
```
|
|
[draft] → [review] → [publish]
|
|
team team ↕ team
|
|
[revision]
|
|
team
|
|
```
|
|
|
|
## Review Cycle
|
|
|
|
1. Author submits draft → enters review
|
|
2. Reviewer A approves, Reviewer B rejects → routes to revision
|
|
3. Author revises → branch rule routes back to review
|
|
4. Both reviewers approve → advances to publish
|
|
|
|
## Installation
|
|
|
|
```bash
|
|
curl -X POST $BASE/api/v1/admin/packages/install \
|
|
-H "Authorization: Bearer $TOKEN" \
|
|
-F "file=@packages/content-approval"
|
|
```
|