Osy#betaRun it on Osyrin: osyrin.com

Reference / Agent

Osysharp.Privacy.Agents.HumanRequests — who handed an inbox item to an agent, under that person's request

`Osysharp.Privacy.Agents.HumanRequests` covers the handovers a person made — an inbox item given to an AI agent — under their privacy request: in their copy of their data, and taken off them when they ask to be erased.

previewagentsguidekit

Source on GitHub: Osysharp.Privacy.Agents.HumanRequests — github.com/osysharp/privacy/agents/humanrequests ↗

You are here: Building with agents › The kits › Privacy.Agents.HumanRequests

Summary#

Osysharp.Privacy.Agents.HumanRequests covers the handovers a person made — an inbox item given to an AI agent — under their privacy request: in their copy of their data, and taken off them when they ask to be erased.

An erasure leaves the handover and takes the person: that the item was handed over, to which agent, its work and how it came back stay — the inbox's own record. An item an agent still holds waits for the erasure until it has come back.

PackageOsysharp.Privacy.Agents.HumanRequests, version 1.1.0
You add it withNothing. It arrives by itself in an app that uses [[agent-kit-privacy|Privacy]] and [[agent-kit-agents-human-requests|Agents.HumanRequests]]; osy lock says so. without Osysharp.Privacy.Agents.HumanRequests; in the manifest keeps it out.
It sits on[[agent-kit-agents|Agents]], [[agent-kit-agents-human-requests|Agents.HumanRequests]], [[agent-kit-privacy|Privacy]]
It also usesIdentity — parts of the platform's own library
Its own test appA ferry line's lost-property desk, where a clerk hands a claim to an agent that matches it against what was found aboard, and a clerk who leaves asks to be erased — kits/privacy-agents-human-requests/tests

Description#

What do you get without writing anything?#

  • Each handover a person made, in their copy of their data.
  • Taken off them on erasure, once every item they handed over has come back.

When do you need it?#

Privacy and Agents.HumanRequests together. It arrives by itself; you write nothing.

What does it expose?#

The tables below are generated from the kit itself, not written by hand: osy kits Osysharp.Privacy.Agents.HumanRequests --surface lists each of them with the code of the kit's own test app that uses it, and the tests that show it working.

Types you use

TypeWhat it is
HandoverRowOne item a person handed over, as their copy carries it.

Functions you call

FunctionWhat it does
Restrict(s, c, untilLifted)Not kept out of use: a handover is the inbox's record of where an item went.
Purge(c, now)Nothing goes by time: it is kept as long as the item is.

Go deeper#

Related

The map of the kits — which sits on which, and what each one is for

The agents family is 29 kits. Two are under everything: `Osysharp.Llm` for every model call and `Osysharp.Agents` for…

Privacy for the agent family — agents, the model meter, assignments and work repositories under a person's request

An app that uses `Osysharp.Privacy` beside the agent kits gets a holder for each without writing one:…

An agent's proposals and questions in a person's inbox, and an inbox item in an agent's hands (Agents.HumanRequests kit)

With the Agents kit and the HumanRequests kit both in an app, this bridge is there: what an agent proposes is an…