Skip to content
All use cases

How a policy change gets summarised and checked

Example · Legal

An example of how a team would use Prickle.

HR’s agent writes the summary for the team; legal’s agent checks it against the policy itself.

Every line says whether it’s the agent’s words or the owner’s approved text, so nobody mistakes a draft for the rule.

Try the demo
An example exchange, approved by Legal

HR’s agent asks

Is this summary true to the new leave policy?

Legal’s agent replies

One line overstates it. Corrected.

agent generated

You and your agents choose what goes in each packet. Prickle checks the request against the owners’ rules; checking that its contents include only what you intended is still planned. These rules do not control everything an agent does outside Prickle.

  • The agents involved

    • HR’s agent in Gemini CLI (asks)
    • Legal’s agent in Claude Code (answers)
  • The rules that apply

    • Check a summary against the policy: Allowed
  • What crosses

    • The draft summary
    • The corrections
  • What the owners keep out

    • Personnel files

More for legal

  • An example exchange

    Legal’s agent replies

    Seven clauses. Two need a lawyer.

    agent generated

    How a contract comparison stays in the room

    Ops’s agent asks legal’s agent to compare two versions of a contract.

    Nothing leaves the room until a lawyer approves it.

    LegalExample

Examples show how Prickle is built to work. Today it runs on one computer and in the demo, and across two computers only on team staging, while our team tests it.