Skip to content
Emdash Mika Docs

Host-Owned Boundaries

Host ownership is central to Mika’s design.

Mika provides:

  • typed commerce DTOs, aggregates, and API contracts;
  • Astro Actions for browser form submissions;
  • request-bound helpers for Astro pages and endpoints;
  • EmDash plugin storage, public catalog/stock JSON routes, and maintenance hooks;
  • provider adapter interfaces plus optional Stripe adapter helpers;
  • operation descriptors and agent manifest builders;
  • copyable Astro templates that become host-owned files after copy.

The host owns:

  • product content and routes;
  • layout and localization;
  • auth and session policy;
  • rate limits and bot checks;
  • provider credentials and SDK clients;
  • tax, shipping, compliance, and support;
  • durable storage and migrations;
  • payment provider webhooks;
  • protected agent endpoints and confirmation UX.

Mika provides reusable commerce semantics and contracts, not those production responsibilities.

The boundary matters most around routes and protocols. Mika’s public plugin JSON routes are catalog and stock reads. Cart, wishlist, checkout, account, subscription, webhook, admin, export, delete, and agent-tool mutations flow through host-owned Astro pages, Astro Actions, endpoints, admin actions, or protocol adapters with host policy in front of them.

When projecting Mika semantics into ACP, MCP, UCP, OpenAPI, AP2, MPP, x402, OAuth, or another protocol, treat the projection as host infrastructure around Mika contracts. Mika does not become the protocol server or payment rail unless the package source explicitly implements that surface.

Section titled “Related Tasks”

Source Anchors

Section titled “Source Anchors”
  • ⓟ ../emdash-mika/README.md
  • ⓟ ../emdash-mika/src/api/routes.ts
  • ⓟ ../emdash-mika/src/provider.ts
  • ⓟ ../emdash-mika/src/agent.ts
  • ⓐ ../emdash-mika/src/templates/astro/README.md
  • ⓐ ../emdash-mika/src/templates/astro/examples/backend-provider.md