Curriculum

Trust

Safety, trust and governance is 32 percent, concentrated in only 36 companies, and the report's verdict is right-size: keep guardrails and responsible-AI as a working PM skill (define guardrails in the PRD, require human approval for irreve

1. 12.01

   Guardrails in the PRD

   You name the guardrails and the human-approval gate in the PRD up front, place the gate before the irreversible action, and make the approval screen show the real action so the click is a decision.
2. 12.02

   What an agent may do without asking

   You set what an agent may do unattended from reversibility times measured reliability, give it a non-human identity with scoped expiring credentials, and treat money as the irreversible action with spend limits enforced at the payment layer.
3. 12.03

   Agent security

   You treat everything the agent reads as untrusted data rather than a command, and reason about the lethal trifecta, prompt injection, tool misuse, permission escalation and memory poisoning as an agent's own attack surface, distinct from generic responsible-AI.
4. 12.04

   Guardrails in the request path

   You put input and output classifiers in the request path, pay their cost in latency and compute, and account for their false positives against an over-refusal budget, not just a block rate.
5. 12.05

   Red-team the obvious modes

   You run the known attacks on your own product as a written plan, accept that a clean run proves risk and not safety, and keep an incident runbook for the quiet degradation that no outage alarm will catch.
6. 12.06

   Right-sized governance

   You keep the governance habits that earn their weight, place the two frameworks that matter without living inside them, and match the controls to the reversibility and legal risk of the feature while holding the launch veto.
7. 12.07

   INTEGRATION CASE

   From repeated runs, you can decide which tool calls may run without asking, and write the memo that defends it.