huncode/content-factory
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: define admin-managed workflow tasks

Browse Source
This commit is contained in:
huncode
2026-05-22 03:22:38 +03:00
parent 5ea0d5978a
commit d1ae5c4437
5 changed files with 202 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
IDEA.md
+7 -2
View File
@@ -8,6 +8,10 @@ The system accepts a short article description, asks boundary-setting questions,
v1 is an internal or single-tenant editorial tool. It is not a customer-facing multi-tenant SaaS product.
### Main principle
The workflow is a first-class Admin-managed product object, not a hard-coded backend status chain. The pipeline is gate-driven: each workflow stage defines its purpose, ordered parts, owner role, runner profile, required inputs, outputs, and acceptance criteria. Runtime execution cannot move to the next stage until the current stage is complete and every required human approval or validation gate has passed.
Chosen architecture:
```text
@@ -50,6 +54,7 @@ Claude Code can be supported as an optional internal runner, but not as the main
14. Multi-site configuration
15. Job history and audit trail
16. Codex CLI-based agent execution
17. Admin-managed workflow templates and editable workflow stages
```
## Out of scope for v1
@@ -76,13 +81,13 @@ The publishing step in v1 should create a **direct commit to the configured prod
## Admin
Can configure target websites, pipeline parameters, agent runner profiles, prompt versions, publishing YAML, and site-specific transformation/upload scripts.
Can configure target websites, workflow templates, workflow stages, pipeline parameters, agent runner profiles, prompt versions, publishing YAML, and site-specific transformation/upload scripts.
## Editor
Can create briefs, answer boundary questions, run the pipeline, edit intermediate results, approve plans, edit drafts, approve final content, and create publish commits.
Only Admins can edit upload scripts and pipeline configuration. Admins are fully trusted code operators because admin-defined transformation scripts run directly on the runner host inside checked-out site repositories.
Only Admins can edit workflow configuration, upload scripts, and pipeline configuration. Admins are fully trusted code operators because admin-defined transformation scripts run directly on the runner host inside checked-out site repositories.
---