liveBook · Manning

Prompt

As explained in Architecting for Autonomy

An instruction or contextual input supplied to a generative model to elicit a response or action.

A legal agent may be prompted to protect privilege, use applicable authorities, distinguish allegations from facts, and obtain lawyer approval. These instructions can shape behavior, but they cannot prove that the correct policy was applied or that the agent stayed within its authority. section 5.7.4

Treat prompts as governed behavioral assets, not as the sole control for institutional obligations:

  • Trace each material obligation to its source, owner, applicability conditions, evaluation result, exception route, and runtime response. section 5.7.4
  • Represent obligations as Policy as Data, and enforce them with pre-agent guardrails or workflow controls before context enters the model, authority increases, sensitive information crosses a boundary, or a tool executes. section 5.7.4
  • Version and govern prompts and system instructions: changes to these assets can alter how the same case material is interpreted. section 5.1.1 section 5.1.2

How Architecting for Autonomy covers it

How deep it goes
Explains prompt limitations and governance controls, but does not specify prompt formats or implementation details.
Examples
Uses a legal-agent instruction set covering privilege, applicable authorities, allegations versus facts, and lawyer approval.
What you can do after
Evaluate whether instructions are backed by independently verifiable policy controls.
How it connects
Connects prompts with Policy as Data, guardrails, workflow controls, retrieval, and tool execution.

Also explained in

Compare how 64 books explain prompt →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecting for Autonomy. The section links point to the parts of the book it draws on.