Eight documents the platform is not allowed to contradict.

Identity and activities

• ·Marvia is an extensible AI Workspace for Digital Marketing.
• ·Every feature must serve Learn, Analyze, Improve or Grow.
• ·The Workspace is the only top-level container; nothing is shared across workspaces.

Access and economy

• ·Guests analyze URLs, preview reports, browse the marketplace and learn without an account.
• ·Login (Google or GitHub) gates save, install, purchase and AI actions only.
• ·Pricing is pay-per-action; extensions declare their own credit costs.

Refresh and open core

• ·No realtime dashboards: last-updated timestamp, refresh action and history on every report.
• ·The kernel is open source; premium value lives in extensions and the marketplace.

Flow

• ·The primary action is reachable in three clicks or fewer and is always visible.
• ·No empty states and no dashboard overload — one screen answers one question.
• ·Keyboard-first, fast loading, fully responsive.

Shell and navigation

• ·One shell for the entire product; no page redesigns it.
• ·Core navigation is fixed; everything else is registered by an extension.
• ·Auth is requested at the gated action and preserves the user's intent.

Structure

• ·Small files, one responsibility per module.
• ·Repository, service layer, adapter and event-driven patterns only.
• ·Components render, services decide, repositories persist.

Typing and providers

• ·Branded ids, explicit Result values and KernelError codes — no magic.
• ·No business logic in components.
• ·No vendor SDK outside its adapter package.

Design system

• ·Tailwind v4, design tokens, CVA, shadcn/ui and Lucide icons.
• ·No custom colors, no inline CSS, no duplicated variants.
• ·Four layers: primitives, compound, blocks, layouts — resolved through the registry.

Schema and access

• ·Pages, reports, content, forms, settings and dashboards are generated from schemas.
• ·The report layout is fixed; extensions supply data, not layouts.
• ·Keyboard navigation, ARIA labels, focus states and contrast are release requirements.

Surface

• ·Core stays minimal; anything non-essential is an extension.
• ·Documentation and examples precede the API — no undocumented APIs.
• ·Registration happens only through defineExtension.

Trust

• ·Manifests are validated at definition time and permissions are least-privilege.
• ·Extensions run sandboxed and read only explicitly granted data.
• ·Extensions read snapshots; they never re-parse HTML.

Role

• ·AI enhances workflows; it never replaces the UX or becomes the application.
• ·AI explains, recommends, summarizes and teaches — always attached to a concrete object.

Limits

• ·Every AI action costs credits and is recorded in history.
• ·AI runs through the provider-agnostic router; no direct vendor calls.
• ·Every task must be completable without AI.

Strategies

• ·Lazy loading, code splitting, manual refresh, queue processing and KV caching.
• ·Permanent JSON snapshots replace repeated fetching; HTML is temporary.

Constraints

• ·No realtime subscriptions by default.
• ·Long work is queued, never awaited in a request.
• ·The shell renders before any extension surface resolves.

Governance

• ·Core contributors govern by consensus; constitution changes require it.
• ·Public APIs are versioned; breaking changes require a migration path.

Contribution

• ·Proposals must name the activity they serve and justify belonging in core.
• ·The default answer to 'should this be in core?' is 'extension'.
• ·Deprecations are announced, dated and paired with a replacement.