JoyintJoyint Docs

Solutions

The five pillars of the Joyint Trust Model.

The Joyint Trust Model is built on five pillars. Together they answer the fundamental questions of human-AI collaboration: who acts, what is protected, how work flows, what happened, and what it cost.

1. Trustship - Who Do I Trust?

Identity, capabilities, and delegation. Every actor in the system - human or AI - has an identity and a set of capabilities that define what they can do.

  • Solo: Implicit trust. One person, all capabilities, no gates. Nothing to configure.
  • Team: Explicit trust. Members have defined capabilities (conceive, plan, implement, review, etc.). AI members get the same model with sensible defaults.
  • Enterprise: Verified trust. Delegation chains track who authorized what. AI actions always trace back to a human.

Trustship scales without changing the workflow. You add accountability when you need it, not before.

2. Guardianship - What Do I Protect Against?

Runtime validation, encryption, and three-layer protection.

  • Prevent: Capability checks stop unauthorized actions before they happen. Gates require human approval at critical transitions.
  • Detect: The event log captures every action. Anomalies surface through log analysis and Judge reports.
  • Prove: Signed events and append-only logs create tamper-evident audit trails. Crypt adds end-to-end encryption for sensitive data.

3. Orchestration - How Do I Steer Work?

Jobs, modes, and dispatch. Orchestration bridges Joy (planning) and Jot (execution).

  • Jobs define units of work that can be dispatched to humans or AI agents.
  • Modes control the level of autonomy: from fully autonomous to step-by-step pairing.
  • Dispatch routes tasks to the right actor based on capabilities, availability, and cost.

Today, orchestration is manual (you start items and assign them). The Dispatcher will automate this for AI agents, respecting trust boundaries and budget limits.

4. Traceability - What Happened?

Event log, Judge audit, and signed events.

  • Every Joy and Jot command produces a structured event: who, what, when, on which item.
  • Events are append-only and committed to Git. They cannot be edited or deleted.
  • The event log is human-readable (one file per day, plain text).
  • Judge provides independent verification: it reads the log, validates consistency, and produces audit reports.

Traceability is always on. There is no way to use Joy without producing a trace.

5. Settlement - What Did It Cost?

Per-job cost tracking, budget enforcement, and future on-chain settlement.

  • AI operations have costs (API calls, tokens, compute). Settlement tracks these per job and per member.
  • Budget limits prevent runaway costs. A team can set daily or per-job caps for AI agents.
  • Future: on-chain settlement enables transparent, verifiable cost tracking for AI work across organizations.

Settlement turns AI usage from an opaque expense into a traceable, controllable line item.