Discoverability first: jump directly to routes, APIs, and essays.
home / workflows

User Stories And Workflows

User Stories, Workflow Compositions, Precious Properties

This surface formalizes operational intent as executable stories: each story has persona, control objective, bounded steps, and evidence expectations.

workflows apicapabilities apiobservatoryorchestration

Select Story

Pick the persona/objective that matches current operational pressure.

Run Bounded Steps

Execute the story’s route and command sequence with explicit gates.

Publish Evidence

Persist run outputs and deltas into workspace run artifacts.

Architecturally Precious Properties

Boundedness First
Capacity and time budgets are not operational afterthoughts; they are a design primitive that keeps truth surfaces responsive.
  • Use gated routes for heavy APIs.
  • Apply time budgets and explicit failures.
  • Prefer deterministic fallback over silent degradation.
/api/corpus/summary/api/capabilities/api/health/control-loop
Preferred strategy: rapid-revalidate
Traceable Isomorphism
UI entities map to cybernetic entities (observe/plan/act/verify), so navigation and intervention reflect actual control semantics.
  • Preserve typed step lattice in orchestration.
  • Keep state-space map aligned with veridicity model.
  • Expose capability topology as inspectable API.
/orchestration/observatory/api/observatory/state-space
Preferred strategy: xanadu-backtest
Replayable Workflows
Runs should be regenerable as evidence artifacts, not one-off interactions.
  • Prearranged workspace strategies.
  • Timestamped run output directories.
  • Guided scripts producing deterministic logs.
/workflows/api/workflows/sessions/autopoetic/xanadu/autopoiesis
Preferred strategy: xanadu-backtest
Reader/Operator Duality
The same routes support comprehension and intervention via mode switch, reducing context fragmentation.
  • Reader mode for scan-first narrative.
  • Operator mode for dense control affordances.
  • Shared truth ribbons across routes.
//core/observatory/metaops
Preferred strategy: rapid-revalidate

Major User Stories

incident-triage-to-apply
Persona: Operator on degraded veridicity
Intent: Restore truthful control loop and perform safe intervention.
  1. Observe control truth /api/health/control-loop
    expect: readiness ok or explicit degraded flags
  2. Run observatory triage /observatory
    expect: ledger + state-space update
  3. Dry orchestration pass /api/orchestration/run?mode=dry
    expect: step results and control-quality deltas
  4. Apply with gate /api/orchestration/run?mode=apply
    expect: bounded intervention, request-id, evidence
Workspace: xanadu-ops-loop / rapid-revalidate
corpus-rescrape-and-rerank
Persona: Research operator rebuilding prompt corpus
Intent: Rescrape, normalize, and validate high-value prompt surfaces.
  1. Run corpus rebuild strategy ./scripts/workspaces.sh run corpus-mining-lab rescrape-rerun
    expect: new corpus artifacts
  2. Inspect explorer and intensity /corpus/explorer
    expect: windowed prompt slices
  3. Validate exploration APIs /api/corpus/explorations?top=60
    expect: stable exploration payload
Workspace: corpus-mining-lab / rescrape-rerun
xanadu-loop-backtest
Persona: System designer iterating autopoietic loops
Intent: Backtest design loop continuity across contexts.
  1. Run guided workflow ./scripts/workspaces.sh run xanadu-ops-loop xanadu-backtest
    expect: guided/autopoiesis/reiterate logs
  2. Inspect reiterated matrix log /sessions/metaautopoetic
    expect: phase/context continuity
  3. Re-enter helix/workbench /xanadu/helix
    expect: node topology plus actionable links
Workspace: xanadu-ops-loop / xanadu-backtest