# Samōsya

> Samōsya is a self-hosted AI Work OS where people set the direction, native AI teams execute the work, and every action, decision, artifact and cost remains traceable in one workspace.

Samōsya is a product, not an integration layer: it has its own run engine, model gateway, permission boundary and execution trace. OpenCode is a development tool used to build it, not the runtime. The public name is written Samōsya; domains, repositories and identifiers use `samosya`.

- Product site: https://samosya.com/
- Technical portal: https://samosya.dev/
- Full product content for LLMs: https://samosya.com/llms-full.txt
- Full technical content for LLMs: https://samosya.dev/llms-full.txt

## Product

- [Why Samōsya](https://samosya.com/#why): the difference from a chatbot, a coding agent and a task manager; conversation is an interface, not the product.
- [Workbench](https://samosya.com/#workbench): one workspace with eleven project tabs in a fixed order, from Workspace and Review to Knowledge, Project, Guild and Settings.
- [Native harness](https://samosya.com/#harness): brief, mission contract, server-side run, permission guard and evidence; runs survive the browser and waiting is a persisted state, not a polling loop.
- [Prompt Designer](https://samosya.com/#prompt): a controlled stage between intent and authorised work; it proposes scope, done-when, acceptance and evidence, and shows a diff. Interface preview today, full stage 011.
- [AI teams](https://samosya.com/#teams): named agents with mandates, models, skills, permissions and budgets. Multi-agent Guild runtime is planned (stage 012).
- [Knowledge and context](https://samosya.com/#knowledge): provenance labels, Canon versus hypothesis, thread memory and context layers.
- [Review](https://samosya.com/#review): decisions about a specific artifact version, with evidence, approver and fingerprint.
- [Self-hosted and control](https://samosya.com/#hosting): single container, durable `/data`, additive migrations and a rollback boundary. Self-hosted does not mean offline.
- [Brand](https://samosya.com/#brand): the mark is a dodecahedron; two working palettes, Soil and Daylight.

## Status and roadmap

- [Product status](https://samosya.com/#status): what is available, preview, in development or planned, with the limit for each area.
- [Roadmap](https://samosya.com/#roadmap): stages 001 to 016 without dates; each stage ends at an owner acceptance gate.

Status vocabulary used on the site: `Available`, `Preview`, `In development`, `Planned`, plus `Partial` where only part of an area works. Planned work is direction, not a delivery date.

## Technical documentation

- [Architecture and runtime](https://samosya.dev/#overview): client and server split, run lifecycle, object model, model gateway and deployment model.
- [Status and evidence](https://samosya.dev/#status): what a verified claim must record, and the current matrix.
- [The interface](https://samosya.dev/#interface): real Workbench captures with build and date.
- [Deployment and backup](https://samosya.dev/#deploy): container shape, `/data`, migrations, backup and rollback.

## Limits to keep in mind

- No public container image, installer, API or SDK is published yet; distribution is planned with stage 016.
- Budget Guard enforces what can be controlled (calls, active time, context); provider token and cost caps are not absolute.
- External inference through OpenCode Go is one provider offering, not the runtime, and there is no automatic paid fallback.