# Architecture and ownership

Use the repository's [architecture](../../../ARCHITECTURE.md),
[modelling conventions](../../../DDD.md) and
[context catalogue](../../context-catalogue.md) as the current shared reference.
Context READMEs own the detailed operations, invariants and implementation limits.

## Service boundaries

| Service | Responsibility in this architecture |
| --- | --- |
| Web | Browser presentation, authenticated API use and typed realtime updates |
| API | HTTP boundaries, sessions and routing to published owner contracts |
| Beto | Party Governance, Project, Support and Marketplace contexts |
| Metallo | Workload and execution capabilities, Site coordination and other registered operational contexts |
| Themelio | New service scaffold; future domain ownership requires an explicit decision |
| Themelio compatibility | Retained application under `compat/themelio`, with separately documented behaviour |

Consult the context catalogue for the complete current map. Deployment grouping
and bounded-context ownership answer different questions. Every context owns its
model and any persisted data, including its credentials and migration history.

## Follow the owner

- [Party Governance](../../../services/beto/contexts/party_governance/README.md) owns canonical Party authentication and verified provider associations.
- [Project](../../../services/beto/contexts/project/README.md) owns the canonical source-managed Project and complete child memberships.
- [Marketplace](../../../services/beto/contexts/marketplace/README.md) owns Orders; its catalogue and buyer ports remain development stand-ins.
- [Resource Provisioning](../../../services/metallo/contexts/resource_provisioning/README.md) owns allocation and native account evidence.
- [SSH Access](../../../services/metallo/contexts/ssh_access/README.md) owns public-key lifecycle and Site application.
- [Member Credentials](../../../services/metallo/contexts/member_credentials/README.md) owns offline consent for native actions.
- [LLM Access](../../../services/metallo/contexts/llm_access/README.md) owns allocations, chat access, budgets and personal keys.
- [Support](../../../services/beto/contexts/support/README.md) owns customer linkage and support-ticket workflows.
- [Contracts](../../../contracts/project/messaging/README.md) define the Project integration boundary and its authority/freshness rules.
- [Browser subscriptions](../../../CLIENT-SUBSCRIPTIONS.md) define server-authorised delivery and revision-aware recovery.

## How to use the examples

The [learning path](../learn/index.md) uses Beto examples selected for a specific
principle. Read the associated implementation and tests before extending a pattern.
Metallo's current layout and unfinished integration work require individual review;
they do not define a general template for a new context.

[Adding a context](../../adding-a-context.md) explains registration, isolation and
verification. Changes to shared policy belong in an architectural decision.