# Product vision

Al-Amr is not one centrally built metaverse. It is an open network of
independent 3D web environments connected by a small, stable platform contract.

The platform enables developers to build, compose, test, publish, discover,
and enter environments, apps, and plugins. The primary developer is AI-assisted, so
canonical public URLs, schemas, examples, APIs, and a non-interactive CLI are
first-class product surfaces. The same material remains complete for humans.

## Product vocabulary

- **Environment**: a destination a user enters and experiences.
- **App**: an independently authored user-facing bundle opened by the desktop
  AppHost, available from Home or across Environments with its own scoped session.
- **Plugin**: a versioned, installable capability used inside an Environment.
- **Frontend adapter**: an optional package surface for a runtime such as
  vanilla web, React, Web Components, or React Three Fiber.
- **Backend component**: an optional data-plane capability protected by a
  short-lived Plugin Grant.
- **Developer Portal**: the public Learn/Discover surface plus the authenticated
  Manage console.
- **Registry**: the source of truth for catalog, releases, publication, trust,
  compatibility, settings, runtime sessions, and presence.

The core rule remains: **inside an Environment is free; connecting to Al-Amr is
standardized**.

## Growth loop

1. A developer finds an Environment, App, or Plugin starter at a stable public URL.
2. Their coding agent reads the same canonical docs and schemas.
3. The `alamr` CLI creates, installs, validates, tests, and publishes.
4. The Registry exposes reviewed releases to the public Developer Portal catalog.
5. Public pages show how Environments host Apps and compose Plugins.

Catalog publication never edits the Hub or creates a 3D placement. Hub
landmarks remain separately authored application content.