Skip to main content

Evidence

Evidence is proof that the intended capability outcome occurred. JoyStream does not stop at technical execution. A successful tool call is not necessarily a successful capability. Evidence may include tool receipts, created artifacts, before-and-after state, approvals, validation results, screenshots, structured outputs, semantic evaluation, human confirmation, business metrics, and policy compliance. It exists at three levels:
A run is not successful merely because execution stopped without an error. The intended outcome must be demonstrated.
Evidence is what allows an agent to earn trust — and it is what a person reviews when deciding whether to promote an agent to Pilot or Live.

Memory

Memory is the accumulated context and learning produced through the operation of a capability: past decisions, organizational preferences, exceptions, stakeholder context, feedback, historical outcomes, successful patterns, failed approaches, policy interpretations, and reusable knowledge. Memory belongs primarily to the capability — not to one conversation, one model, one agent version, or one run. That is what lets a capability get better across model changes and staff changes. Different kinds of memory have different scopes: story, run, agent, capability, workspace, and organizational knowledge. Memory should be attributable, permissioned, inspectable, correctable, and version-aware.

Memory cannot silently override governance

Memory informs execution. It cannot silently rewrite policies, boundaries, success criteria, or organizational intent.
Learned behavior becomes authoritative only through review. If an agent should behave differently, that change goes through a new capability spec version — not through something the agent quietly picked up on a Tuesday.

Metrics

Metrics measure whether the capability is creating organizational value. They come in three layers, and only the third is the point. JoyStream optimizes for capability outcomes, not agent activity. An agent that runs constantly and delivers nothing is not succeeding.

Human accountability stays visible

Every capability has identifiable human ownership. AI agents execute and collaborate. People remain accountable for intent, access, governance, exceptions, promotion, and organizational consequences.

Next

Workspaces and organizations

Where ownership and access live.

Review runs and tickets

Inspect what a run actually produced.