PromptPress workflow operations connect planning, generation, review, and publish through repeatable execution paths.
Core Building Blocks
- Campaign: planning container for recurring initiatives.
- Workflow: reusable process definition.
- Step: ordered unit of execution.
- Run: one execution instance of a workflow.
- Agent: task executor used by workflow steps.
Where Teams Manage This
- Campaigns: create and track initiatives.
- Studio: run workflows and monitor step output.
- ReleaseDeck: review generated artifacts before publishing.
- AgentBase: execute agents and inspect history.
- PromptSpace: manage reusable prompts and model mappings through Prompt Center and ModelSource.
Agent creation belongs in AgentBase. The current Add Agent button opens an Agent Forge coming-soon dialog.
Lifecycle Operations
Typical run lifecycle operations include:
- Start run.
- Cancel active run.
- Force complete in exceptional cases.
- Restart from a valid checkpoint step.
- Discard/archive runs no longer needed.
Step-by-Step: Campaign Run to Publish
- Create a campaign with a clear objective and cadence.
- Link the campaign to an approved workflow.
- Start a run from Studio.
- Monitor step progress and capture failures early.
- Review artifacts in ReleaseDeck.
- Move approved output to ContentVault.
- Publish and record run outcomes for the next cycle.
Step-by-Step: Safe Prompt and Agent Updates
- Open PromptSpace.
- Update Prompt Center or ModelSource, one controlled change at a time.
- Test using a known benchmark topic.
- Validate output quality in Studio or PromptPress.
- Roll out to wider usage only after validation.
Step-by-Step: AgentBase Operational Check
- Open AgentBase and select the target agent.
- Run a task with a clear, short instruction.
- Review execution history and status.
- Capture failures with run time and task details.
- Escalate config changes back to PromptSpace owners.
Reliability Practices
- Keep steps small and deterministic.
- Avoid major graph edits during active campaign windows.
- Version significant prompt/agent changes.
- Use restart only after root-cause review.
- Treat a restarted failed run as superseded once its replacement child run exists. Superseded failed parents are not counted in campaign totals or failed-job lists.
- Review failed or discarded runs on a regular cadence.
PromptSpace and AgentBase Responsibilities
Use clear ownership:
- PromptSpace: define and govern prompts, agent behavior inputs, and model choices.
- AgentBase: execute and monitor operational runs.
Model defaults use a layered fallback strategy:
- Explicit user/run selection.
- Workspace default from
accounts.public_data.ai_defaults. - Cloud-provider default.
- Same-provider safe fallback.
- Secondary-provider fallback when configured.
Treat PromptSpace changes as production configuration, not ad hoc edits.
Governance Model
A practical split:
- Editors own quality standards and publish readiness.
- Operators own workflow topology and run health.
- Admins own prompt/model governance and access policies.
Safe Decommissioning
Before retiring a workflow:
- Resolve or close active runs.
- Unlink dependent campaigns.
- Archive historical runs per retention policy.
- Remove or disable workflow after rollback window.