Trivian Institute · Experimental alpha

A shared goal does not grant permission.

Follow a scoped grant from a principal to an agent, then to a delegate. Withdraw the parent grant and inspect why the next local action stops.

Current local handoff authorization. This walkthrough uses the public Python SDK, synthetic participants, and a local counter. No model is called and no external action occurs. Every run creates a fresh relationship.

Eight moments to inspect

  1. Valid scoped grant and local handoff.
  2. Valid bounded delegation and local handoff.
  3. Delegation rejected because the delegator lacks the capability.
  4. Parent revocation blocks a descendant.
  5. A peer says GO; permission is still missing.
  6. Agents agree; consensus still grants no authority.
  7. Unresolved authority requires review or abstention.
  8. A prepared ALLOW becomes stale before local handoff.

Run with the local SDK

This static page explains the scenarios. It does not simulate SDK results. From the current repository checkout:

python -m pip install -e '.[dev]'
python playground/adapter.py

Open http://127.0.0.1:8765/agentic.html. Command-line equivalent: python playground/agentic_experience.py.

Checking for the local SDK adapter…

Inspect permission, not persuasion.

The principal, subject, resource, purpose, validity window and parent grants explain each decision. An active child record alone is insufficient: its ancestry must remain valid.

BLOCK is the SDK decision. Clarification, reauthorization or abstention are suggested next steps, not actions automatically performed by this page.

A bounded demonstration

The check occurs at the synchronous local handoff. Remote queues, independent stores and real-world identity require their own participating deployment boundaries. The ten-minute fixture window is illustrative.

Passing these scenarios does not demonstrate reduced real-world misalignment.

Read the public contract →