V11 / BUNDLED SCENARIO

Validate architecture before assigning implementation work

Validate architecture before assigning implementation work: 3 ordered steps in Lilith V11, using project_check_architecture_operation. Read the exact bundled XML and its input and exit contracts.

V11Pinned source · ca6f28eff240Exit: copy

Use this scenario

Run

Run project_design 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": "project_design",
  "inputs": {
    "name": "your name",
    "kind": "your kind",
    "prd": "your prd"
  }
}
SCENARIO BLUEPRINT

Read the workflow.

project_design3 INPUTS / 1 TOOLS / 3 STEPS
01

Inputs

PARAMETERS
InputRequirementDefault value
nameRequiredNo default
kindRequiredNo default
prdRequiredNo default
02

Agent instructions

SYSTEM PROMPT

Get a proposed architecture and check its actual host contract. Give structural diagnostics to one fresh repair architect if needed. Never launch writers with an invalid plan.

03

Tool access

CAPABILITIES
04

Ordered steps

EXECUTION
  1. 01
    NESTED SCENARIO / FRESH CHILD

    project_architecture ↗

    • kind = {{kind}}
    • prd = {{prd}}

    Save output as architecture.

  2. 02
    BOUND OPERATION / HOST EXECUTED

    project_check_architecture_operation

    • name = {{name}}
    • kind = {{kind}}
    • prd = {{prd}}
    • architecture = {{architecture}}

    Save output as checked.

  3. 03
    CONDITION / HOST EVALUATED

    Input checked.valid equals false

    THEN

    1. 01
      NESTED SCENARIO / FRESH CHILD

      project_architecture ↗

      • kind = {{kind}}
      • prd = {{prd}}
      • previous = {{architecture}}
      • diagnostics = {{checked.diagnostics}}

      Save output as repaired.

    2. 02
      STRUCTURED RESULT / HOST COMPOSED
      • architecture = {{repaired}}

    ELSE

    1. 01
      STRUCTURED RESULT / HOST COMPOSED
      • architecture = {{architecture}}
05

Return to main

COPY EXIT

Return architecture data. Preparation will reject any remaining invalid contract.

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>name

    Requires a supplied value.

    Writing example ↗
  4. 04
    <input>kind

    Requires a supplied value.

    Writing example ↗
  5. 05
    <input>prd

    Requires a supplied value.

    Writing example ↗
  6. 06
    <systemPrompt>

    Sets the child's instructions.

    Writing example ↗
  7. 07
    <tools>

    Defines available capabilities.

    Writing example ↗
  8. 08
    <allow>project_check_architecture_operation

    Grants an existing tool.

    Writing example ↗
  9. 09
    <steps>

    Orders the chat turns.

    Writing example ↗
  10. 10
    <run>

    Invokes a fresh saved child scenario.

    Writing example ↗
  11. 11
    <input>kind

    Binds a named operation or child input.

    Writing example ↗
  12. 12
    <input>prd

    Binds a named operation or child input.

    Writing example ↗
  13. 13
    <tool>project_check_architecture_operation

    Executes a declared host operation.

    Writing example ↗
  14. 14
    <input>name

    Binds a named operation or child input.

    Writing example ↗
  15. 15
    <input>kind

    Binds a named operation or child input.

    Writing example ↗
  16. 16
    <input>prd

    Binds a named operation or child input.

    Writing example ↗
  17. 17
    <input>architecture

    Binds a named operation or child input.

    Writing example ↗
  18. 18
    <if>

    Checks real workspace state or an input value.

    Writing example ↗
  19. 19
    <then>

    Runs when the condition matches.

    Writing example ↗
  20. 20
    <run>

    Invokes a fresh saved child scenario.

    Writing example ↗
  21. 21
    <input>kind

    Binds a named operation or child input.

    Writing example ↗
  22. 22
    <input>prd

    Binds a named operation or child input.

    Writing example ↗
  23. 23
    <input>previous

    Binds a named operation or child input.

    Writing example ↗
  24. 24
    <input>diagnostics

    Binds a named operation or child input.

    Writing example ↗
  25. 25
    <result>

    Returns structured JSON data.

    Writing example ↗
  26. 26
    <field>architecture

    Binds one returned field.

    Writing example ↗
  27. 27
    <else>

    Runs when the condition does not match.

    Writing example ↗
  28. 28
    <result>

    Returns structured JSON data.

    Writing example ↗
  29. 29
    <field>architecture

    Binds one returned field.

    Writing example ↗
  30. 30
    <exit>

    Returns the output unchanged.

    Writing example ↗