Build a Play with your agent

/deepline-gtm Build a Deepline Play for the outcome I describe. First inspect existing Plays and tool contracts. Reuse a maintained Play when its contract fits; otherwise author a workspace-owned Play. Preserve source identity, define inputs and outputs, and implement my acceptance rules explicitly. Keep external writes disabled in the first pilot. Check the source before proposing a small run and show me the expected usage.

/deepline-engine Build an Engine for the state machine I describe. Confirm the states, allowed transitions, state-decision rules, transformations, and terminal behavior without inventing business policy. Preserve stable row identity and transition history. Reuse inspected transition Plays where their contracts fit. Show the state diagram and validation results before publication or a paid pilot. Do not activate triggers as part of building the Engine.

/deepline-gtm Compare the result with the acceptance rule we agreed. Show the evidence for accepted and rejected outcomes, unresolved questions, and recorded Deepline usage where work ran. If work is still running or a response is uncertain, inspect the original saved execution before proposing another request. Explain the next decision I need to make.