Files
stack/docs/concepts
jason.woltje 193479b52d docs: concept annexation, provider/reference docs, ACT-1 groundwork
Mosaic concepts pages now own the adapted content; source/license
metadata under docs/reference/concepts. Adds ACT-1 agent-context
planning capture, pinned concept test package + preparation utility,
foundation observation notes (durability, evidence, federation,
onboarding, workflow), and the #1495 consolidation assessment.
TOOLS.md updated for the host-dev launcher.
2026-09-07 14:07:05 -05:00
..

Mosaic Stack concepts

These pages explain Mosaic's own concepts and design direction. Each states its implementation status. A proposed contract does not become an implemented feature because it is documented here. Current demo compatibility and ACT-1's migration gates remain in force.

Concept What it explains
Agent personality One canonical SOUL, concrete voice, and instance ownership
Execution context What an execution receives and how to inspect its provenance
Prompt composition File responsibilities, scope, and input lifetime
Collaborative state awareness Changed decisions, reconciliation, and notification boundaries
Managed worktrees Checkout ownership, protected work, and recovery
Steering and cancellation Queued versus started work and honest interruption semantics
Session attachment Shared session authority across interfaces
Multi-user authority Attribution, observation, control, and scoped permission
Agent runtimes Provider/model/harness distinctions and adapter evidence
Agent behavior tests Synthetic scenarios, personality comparisons, and result integrity
Memory architecture Knowledge categories, admission, scope, and retrieval
Memory provenance Source lineage, correction, and deletion coverage
Standing intents Events, schedules, aspirations, and real wake ownership

Implementation work belongs in ACT-1 and related foundation plans. Start testing preparation from the Darkwing package.

This directory is the home for conceptual explanations. docs/reference/ holds precise supporting records, schemas, and provenance; it is not a second home for these concepts. Source attribution preserves the origin and license of material adapted into this set.