V
Vitor Almeida
Current scenario
Today, the Prompt Led Section allows you to include instructions between
[]
in the title of a content section, and these instructions act as
contextual direction
to the LLM (as documented in KB's public article Prompt Led Section). In scenarios where the instruction is a mandatory pre-validation - for example, “before guiding, validate the platform version with the client” - the AI probabilistically follows: in many cases it delivers the main guidance of the section before executing the validation described in square brackets.
Observed Behavior
  • AI identifies content that is semantically related to the customer's question.
  • Prioritizes the main orientation of the section.
  • Treat instructions between
    []
    as contextual/behavioral targeting.
  • In some scenarios, it uses the content before performing the validation/guidance described between
    []
    .
  • Prior validation does not work as a mandatory step before the response.
Order
Evolution of the Prompt Led Section to support
mandatory precondition
— a deterministic gate before using the section. Implementation suggestion: a dedicated “Pre-validation” field in the section, separated from the body of the guidance, with locking semantics — the AI cannot deliver the guidance without first executing (and confirming with the client, where applicable) the step described in the pre-validation.
Motivation
Content with critical prerequisites (platform version, customer profile, contract status, funnel stage) today depends on a natural language instruction between
[]
that the model may or may not respect. A deterministic gate would provide predictable control in scenarios where order matters (validate → orient), reduce the chance of inadequate guidance due to lack of context, and reduce rework/escalation caused by responses delivered without prior validation.
Typical Use Case
A section with the following instruction in square brackets:
>
[If you use this content, validate with the client what version of the platform is and use it only if it is NEW. If the version has already been identified before in the service, do not repeat the validation and continue to consider this information throughout the interaction. ]
It should become a mandatory pre-validation configurable in the section - not a contextual orientation that the model follows in a probabilistic way.
Expected Result
  • Pre-validation takes place before orientation, in a guaranteed manner.
  • When the information is already in the history/context, the gate considers the validation completed and proceeds to the orientation.
  • The operation can design content flows with dependent steps without requiring increasingly imperative prompts to try to force order.
·