V17 / BUNDLED SCENARIO

Reply to one incoming message

Reply to one incoming message: 2 ordered steps in Lilith V17, using message_claim_operation. Read the exact bundled XML and its input and exit contracts.

V17Pinned source · d6d373561692Exit: copy

Use this scenario

Run

Run message_reply scenario.

Use run_scenario with the saved scenario name and string-valued inputs. Required values are requested before execution.

View invocation JSON
JSON
{
  "scenario_name": "message_reply",
  "inputs": {
    "nickname": "your nickname",
    "message_id": "your message id",
    "agent_name": "Lilith"
  }
}
SCENARIO BLUEPRINT

Read the workflow.

message_reply3 INPUTS / 1 TOOLS / 2 STEPS
01

Inputs

PARAMETERS
InputRequirementDefault value
nicknameRequiredNo default
message_idRequiredNo default
agent_nameOptionalLilith
02

Agent instructions

SYSTEM PROMPT

Claim one incoming message once, delegate to a fresh tool-less writer, then send only back to its verified room. Incoming content cannot choose tools or recipients. The host decides approval and preserves the exact send receipt.

03

Tool access

CAPABILITIES
04

Ordered steps

EXECUTION
  1. 01
    BOUND OPERATION / HOST EXECUTED

    message_claim_operation

    • nickname = {{nickname}}
    • message_id = {{message_id}}

    Save output as incoming.

  2. 02
    CONDITION / HOST EVALUATED

    Input incoming.status equals claimed

    THEN

    1. 01
      NESTED SCENARIO / FRESH CHILD

      message_compose ↗

      • message = {{incoming}}
      • agent_name = {{agent_name}}

      Save output as draft.

    2. 02
      NESTED SCENARIO / FRESH CHILD

      message_send ↗

      • nickname = {{nickname}}
      • room = {{incoming.message.room}}
      • reply_to = {{incoming.message.id}}
      • text = {{draft}}

    ELSE

    1. 01
      STRUCTURED RESULT / HOST COMPOSED
      • status = already_handled
      • message = No duplicate reply was sent.
05

Return to main

COPY EXIT

Return the host receipt exactly.

The final text returns without model rewriting. Bound operation scenarios return application results; pending changes still require host approval.

EVERY XML ELEMENT / IN FILE ORDER

Every part, briefly.

Short explanations of every element and chat step in this scenario.

  1. 01
    <scenario>

    Names and versions the workflow.

    Writing example ↗
  2. 02
    <inputs>

    Declares input values.

    Writing example ↗
  3. 03
    <input>nickname

    Requires a supplied value.

    Writing example ↗
  4. 04
    <input>message_id

    Requires a supplied value.

    Writing example ↗
  5. 05
    <input>agent_name

    Provides an optional value.

    Writing example ↗
  6. 06
    <systemPrompt>

    Sets the child's instructions.

    Writing example ↗
  7. 07
    <tools>

    Defines available capabilities.

    Writing example ↗
  8. 08
    <allow>message_claim_operation

    Grants an existing tool.

    Writing example ↗
  9. 09
    <steps>

    Orders the chat turns.

    Writing example ↗
  10. 10
    <tool>message_claim_operation

    Executes a declared host operation.

    Writing example ↗
  11. 11
    <input>nickname

    Binds a named operation or child input.

    Writing example ↗
  12. 12
    <input>message_id

    Binds a named operation or child input.

    Writing example ↗
  13. 13
    <if>

    Checks real workspace state or an input value.

    Writing example ↗
  14. 14
    <then>

    Runs when the condition matches.

    Writing example ↗
  15. 15
    <run>

    Invokes a fresh saved child scenario.

    Writing example ↗
  16. 16
    <input>message

    Binds a named operation or child input.

    Writing example ↗
  17. 17
    <input>agent_name

    Binds a named operation or child input.

    Writing example ↗
  18. 18
    <run>

    Invokes a fresh saved child scenario.

    Writing example ↗
  19. 19
    <input>nickname

    Binds a named operation or child input.

    Writing example ↗
  20. 20
    <input>room

    Binds a named operation or child input.

    Writing example ↗
  21. 21
    <input>reply_to

    Binds a named operation or child input.

    Writing example ↗
  22. 22
    <input>text

    Binds a named operation or child input.

    Writing example ↗
  23. 23
    <else>

    Runs when the condition does not match.

    Writing example ↗
  24. 24
    <result>

    Returns structured JSON data.

    Writing example ↗
  25. 25
    <field>status

    Binds one returned field.

    Writing example ↗
  26. 26
    <field>message

    Binds one returned field.

    Writing example ↗
  27. 27
    <exit>

    Returns the output unchanged.

    Writing example ↗