Creator-operator long-running agent case
A non-technical operator can see what changed, what is blocked, what can safely continue, and how feedback changes the plan without reading prompts, logs, or raw traces.
Case context
This is an appendix case: it shows how a non-technical creator-operator might use LoopX to manage a long-running research and planning loop, but it is not a top-card proof until real public user evidence exists.
The public material uses only synthetic data. The point is not proving growth; it is proving the product boundary: research and material organization can continue, while publishing, brand judgment, and external action remain human gates.
Repository evidence
A creator-operator needs a long-running agent loop that keeps research moving while publishing decisions stay gated.
creator_operator_workflow, gate_aware_continuation, feedback_capture, safe_side_path
`creator-ops-fake-data-storyboard.md` provides a complete fake fixture with no live platform access, suitable for showing the user journey without exposing real operations data.
`creator-ops-feedback-boundary-contract.md` separates gate decisions, preference hints, todo updates, boundary corrections, reward signals, and product improvement notes so preference is not mistaken for publish approval.
The contract requires every topic, insight, draft, and material item to carry source status; the public repo defaults to `synthetic_demo` instead of pretending to show real growth evidence.
Publishing is a hard user gate; safe side work may continue, but preference or reward is not publication approval.
LoopX behavior
- 1The creative objective is durable goal state, not a hidden task inside chat.
- 2Publish/no-publish is a user gate; research, organization, and source-status work can continue as safe side paths.
- 3Feedback becomes a preference hint, gate decision, todo update, or boundary correction.
- 4Before the next agent run, the user can see the blocked route, safe side path, and validation expectation.
What the user sees
A non-technical user can see what changed, what is waiting for them, and what can continue without reading prompts, traces, or raw logs.
The case is useful product direction, but the page clearly labels it as a synthetic spec and makes no claim about real growth, quality, or revenue.
Repository sources
docs/showcases/cases/0620-creator-operator-case-spec.mdfake-data storyboarddocs/showcases/creator-ops-fake-data-storyboard.mdfeedback boundary contractdocs/showcases/creator-ops-feedback-boundary-contract.mdEvidence boundary. Synthetic case spec only; no real platform data, creator notes, screenshots, private drafts, raw browsing traces, local paths, credentials, or performance claims.