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

Relationships

#2809 gatorwalk-factory studio: example payloads from JSON Schema for Simulate walks

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

A walk in Simulate has to record artifacts and evidence, and nobody should type payloads by hand (decided 2026-09-30: the studio does not edit; the agent writes files). Generate them from the artifact's or evidence's JSON Schema: a valid example, plus invalid variants (a missing required field, a wrong type, an enum miss) that exercise retry-with-feedback and show the rejection messages.

Scope

  • A pure generator in _lib, over the draft 2020-12 subset the lifecycle schema accepts (required, properties, enum, const, pattern via a small set of fixtures, minItems, if/then, allOf), deterministic.
  • In Simulate's "walk from here" (#2808), a record step offers "a valid example" and each invalid variant, beside the payloads the saved scenarios already use. An invalid one shows the engine's rejection.
  • The generated payload goes into "Copy as scenario", so the agent receives a scenario it can save as it is.
  • The agent writes the payloads in the scenarios it authors and needs no generator. Exposing the generator to the agent is out of scope until that proves wrong.

Needs: #2808. After launch.

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

Closed

10/5/2026, 7:08:07 PM

No activity in this phase yet.

03Sludge Pulse
Editable. Press Enter to edit.

system commented 9/30/2026, 3:48:21 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:50 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. With no scenario editor, the generator now serves the simulator. A 'record' step in Simulate's 'walk from here' offers a valid example and invalid variants, so nobody types payloads by hand, and the generated payload goes into 'Copy as scenario' for the agent to save. The agent needs no generator for the scenarios it writes. Retitled to match.

skunk-ape commented 10/5/2026, 7:08:07 PM

Closing with stagecraft's first release (@swamp/stagecraft 2026.10.02.1). This was a design gap recorded before launch and nothing in use has asked for it. If it matters in practice it will resurface from actual use, and this issue can be reopened or refiled with the case that needs it.

Sign in to post a ripple.