Skip to main content
← Back to list
01Issue
FeatureClosedExtensionsPublic
AssigneesNone

Relationships

↔ sibling #2943↔ sibling #2944

#2810 gatorwalk-factory studio: Operate mode for live work items

Opened by skunk-ape · 9/30/2026

Part of the gatorwalk-factory studio (gatorwalk-factory/ in swamp-extensions). Read gatorwalk-factory/README.md and DESIGN.md first. Design proposal (decisions recorded 2026-09-30): https://claude.ai/artifact/BNCKp7w3G3Q8VdmnCDDWHP. Prototype, with its source under source/ (read it with the Artifact tool): https://claude.ai/artifact/1wAxrpUqZ47FAjE4fU9idD. Both links are private to the maintainer.

Goal

The studio's Operate mode: every live work item pinned to a lifecycle, shown on the graph, reusing Simulate's panels on each item's real journal.

Scope

  • Server route GET /api/work-items?holder=<holder>: run records of work items pinned to the holder's lifecycle, with one swamp data query over their run records (read-only).
  • A token per work item on its current stage, gold while it waits on a person, with how long it has waited. Flag an item pinned to an older lifecycle digest than the file's.
  • Selecting an item opens the Run and Metrics panels on its real journal, scrubbed like a scenario.
  • "Copy this run as a scenario": show a real journal as scenario YAML (payloads from the stored product versions), the same read-only view and Copy button as Simulate's "Copy as scenario" (#2808). The agent saves it; the page writes nothing (decided 2026-09-30).

Needs: #2808. After launch.

02Bog Flow
✓OPEN○TRIAGED○IN PROGRESS◉CLOSED

Closed

10/2/2026, 2:00:04 PM

No activity in this phase yet.

03Sludge Pulse
skunk-ape linked sibling of #294310/2/2026, 2:00:02 PM
skunk-ape linked sibling of #294410/2/2026, 2:00:02 PM
Editable. Press Enter to edit.

system commented 9/30/2026, 3:48:22 PM

Classified automatically when this issue was filed.

  • Source: Extensions

If you feel this classification is incorrect, add a ripple to tell us so.

skunk-ape commented 9/30/2026, 4:04:51 PM

Re-scoped. Seth decided on 2026-09-30 that the studio views and simulates but never edits: "Edits should come from the agent... I just don't think we should go down the road of having users create or edit by hand." The agent writes lifecycles and scenarios as files, and the local page reloads them. 'Save this run as a scenario' is now 'Copy this run as a scenario'. It shows the journal as scenario YAML for the agent to save, the same way Simulate's 'Copy as scenario' works. Everything else is unchanged.

skunk-ape commented 10/2/2026, 2:00:03 PM

Superseded by #2943 (Board view) and #2944 (work-item view), filed 2026-10-02 at Seth's request. Its server route idea moved to #2943, and 'Copy this run as a scenario' moved to #2944. Closing.

Sign in to post a ripple.