Concepts
Read these pages when you are trying to understand what Mika owns, what the Astro host owns, and why the same operation can appear as a page helper, Astro Action, plugin route, admin runner operation, or agent descriptor.
GlossaryShort definitions for the terms used across the docs.
ArchitectureHow copied pages, Actions, plugin routes, providers, admin, and agent metadata fit together.
Data ModelProduct, sellable, price, stock, account, order, entitlement, and fixture concepts.
Host-Owned BoundariesWhat Mika does not own, and where host policy belongs.
Integration File MapWhich files are package imports, copied templates, or seeded host examples.
Route SurfacesSeparate copied pages, Astro Actions, plugin JSON routes, and metadata endpoints.
Security And IdempotencyWhere guards, confirmations, provider signatures, and replay protection belong.
Agent-Ready CommercePublic metadata and host-owned agent protocol projections.
Start with Host-Owned Boundaries when you need the ownership split. Use Integration File Map when you are ready to map concepts to files.
Source Anchors
Section titled “Source Anchors”- ⓟ
../emdash-mika/src/api/operations.ts - ⓟ
../emdash-mika/src/api/operation-agent-metadata.ts - ⓐ
../emdash-mika/src/templates/astro/README.md - ⓣ
../emdash-mika-template/astro.config.mjs