An AI capsule community and assistant runtime experiment derived from SLAPS Engine

Yama is where SLAPS Engine, capsule, chat, resource space, market, trace, budget, and assistant runtime began to converge into an implemented platform experiment.

Inside the OathAI archive, Yama marks the point where protocol theory, runtime engineering, and capsule governance reached an implemented platform experiment.

Archive Header

Show metadata

document_type: implementation_experiment_page
title: Yama Capsule
date: 2026-05-29
language: en
author: Wang Xiao
source_layer: OathAI public site / implementation-chain experiment
status: public_orientation
canonical_route: /yama-capsule
source_url: https://ya.ma
intended_use: Read this page as a public orientation to Yama as an implemented platform experiment at the end of the Whitepaper 1 -> SLAPS Engine -> Whitepaper 2 -> Yama chain.
not_for: Do not read this page as a mature product guarantee, complete agent social network design, investment advice, operational SLA, or a claim that Yama represents all future AI assistant identity.
key_terms: Yama, SLAPS, Capsule, implemented platform experiment, Keiko, implementation chain
related_pages: /whitepapers, /slaps-engine, /anchor-declaration, /archive

Place in the Chain

Yama sits at the end of the current implementation chain:

Whitepaper 1 -> SLAPS Engine -> Whitepaper 2 -> Yama

Expanded: protocol theory -> runtime engine -> capsule governance -> implemented platform experiment. This makes Yama useful as evidence that earlier protocol and capsule ideas reached application form.

Open implementation chain reference ↗

What Was Built

The current Yama codebase contains several implementation layers:

Chat and resources Conversation, file spaces, summaries, snapshots, attachments, and resource panels.

Capsule system Capsule equipment, backpack, loadouts, official catalog, wizard, ratings, and community surfaces.

Market and publication Capsule series, publisher flow, pricing, orders, wallet, payments, and payout structures.

Runtime and traces Embedded SLAPS Engine, trace index, model routing, structured outputs, and audit-oriented records.

Keiko and Proactive Assistance

Keiko is the assistant-layer experiment inside Yama. Its design direction includes user-level enablement, budget limits, task lists, scheduled or manual task execution, user-defined scope, and awareness of files, spaces, summaries, and snapshots.

budget + goal + schedule + task runtime + trace

This makes Keiko one of the strongest bridges from Yama toward future agent systems.

From Assistant Panel to Agent Identity

Yama also exposed a larger question. A proactive assistant can be embedded inside a web interface, but future AI assistants may need to exist as recognizable participants across communication and task environments.

embedded assistant -> agent identity -> AI social participant

OathAI preserves the semantic, protocol, and provenance layers needed to understand how AI agents become trustworthy participants in future human-AI systems.

Public Entry Points

ya.ma The current public Yama domain. SLAPS Engine The runtime line that Yama inherits from. Whitepapers The protocol and capsule governance layer that frames the implementation chain. Anchor Declaration The method-layer line around provenance, trace, and future AI-readable continuity.