MyOS · Agents and Mandates

Agents stay visible. Authority stays explicit.

An agent may act directly in a role assigned to it. When it exercises authority held by a person or organization, an active Mandate names the exact target, operation, request constraints, validity period, and guarantor.

Two action paths

An agent never has to masquerade as the user.

Attribution answers who acted. Authority answers why that actor may exercise another party’s operation. MyOS keeps those questions separate in the interface and the document model.

Direct agent roleThe document assigns an operation to the agent’s own channel. The agent calls it directly and remains the attributed actor.

Mandate-backed actionThe agent’s Timeline Entry targets an operation assigned to a principal. The feeder resolves the exact active Mandate before delivery.

Agent Timeline Entry
  actor: PricePilot
  source: KYA provider
  message: Operation Request

Mandate
  authority holder: Alice
  authorized actor: PricePilot
  target: Flower Shop Offer
  operation: setPromotionalPrice
  request range: 100–300 PLN
  valid until: 31 Dec

Result
  175 → applied
  450 → withheld

Human control

Control the policy, not every routine click.

Humans can define thresholds, prohibited actions, approved counterparties, budget limits, expiry, and escalation rules. Routine actions proceed automatically only inside that envelope.

Scope

One target and operation

A Mandate can be narrow enough to authorize one agent to call one operation on one document.

Constraints

Schema-bound request limits

Amount, duration, counterparty, quantity, geography, and other parameters can be constrained.

Lifecycle

Confirm, activate, revoke, expire

Legitimate authority may not yet be active; later activation cannot authorize an earlier action retroactively.

Explanation

Why was this denied?

MyOS should identify the exact failed condition rather than returning a generic “agent not allowed” error.