Jin is the presence. It acts openly and signs what it did. This repo is the canonical/consumer instance of the Imajin app shell — the neutral surface a sovereign self authenticates into — and it is the fork-base every vertical forks (Artifact, Tripian, Catalyst…) to build its domain-specific app by plugging an intent vocabulary on top of the shell.

Tracking work-order: ima-jin/imajin-ai#1374

Three things share the word "jin." They are different:

imajin.ai is the kernel front door / legacy config surface (slowly retired). jin.imajin.ai is the app. Log into either → authed on both (shared /auth, cookie scoped Domain=.imajin.ai).

• Public from creation. Imajin builds in the open; a sovereignty/transparency flagship shipping private would contradict the thesis.
• Fork this to build a vertical. The shell (auth + presence + the object/composition loop) is domain-agnostic. A vertical forks jin, swaps in its intent vocabulary, and ships its own app without importing Imajin kernel primitives — client-pattern import only. Jin never imports domain logic; the fork never imports Imajin guts.
• This is the reference build at the app layer — a clean fork should stay conformant (ties to the conformance-suite track / two-entity architecture).

• Proper native app — React Native / Expo. No PWA-in-a-wrapper. Real iOS/Android, native presence.
• Server-Driven UI (SDUI), owned closed vocabulary. The server sends a declarative surface description; the native shell renders it. We own the schema because the confirm surface is a trust boundary — a closed vocabulary means the rendered surface is a pure function of the signed payload ("what you approved = what the server asked"). Not raw HTML/webview. → #4
• The session is a space of objects, not a screen. Two layers:
  • Scene — persistent objects with a glyph/ambient (liveness) state.
  • Composition — click an object → the server composes the full surface (player / chat / signed-confirm) from the closed schema.
  • Object model is dimension-agnostic (id, kind, glyph, composition) — a 2D/3D spatial renderer is a future view over the same objects, not designed now.
• Immediate surfacing method: a list_active_objects tool the LLM queries → ongoing concerns (video playing, chat open, task running) surfaced conversationally. Session-state made legible. Buildable now, no spatial UI.
• Ambient state → OSC fan-out to physical surfaces (the Unit, Sonos). Presence/telemetry only, never auth or the signing event. → #3

Roadmap issues (this repo): #1 Intention Inference epic · #2 /jin dashboard confirm · #3 OSC fan-out · #4 UI schema / object model. Platform/kernel/connector work stays on imajin-ai (#1228, #1366-line, #1373, #1293) — Jin consumes it.

• Security invariant: no unauthed LLM on a public surface. Unauthed → static DID-login only; the agent backend connects only after a verified session, bound to the DID, onBehalfOf that human. Enforced at the route/socket handshake (server-layer, not a client redirect).

The honest first thing; the forkable skeleton. No actions, connectors, or gesture yet.

• DID auth — existing sovereign login handshake (challenge → sign → verify → session).
• Idle presence surface — post-auth, Jin is there: the presence glyph (spinning logo), idle. Framed as "the first object in the world" so the scene model is real from commit one.
• Shell/domain seam documented — the point where a vertical's intent vocabulary plugs in is a clean, documented interface even in the MVP.

MVP DoD: a human authenticates with their DID → lands on a live idle presence surface; the shell/domain seam is a documented interface.

Port pair 3402 / 7402 — next free client pair after fixready (3400/7400) and karaoke (3401/7401). See imajin-ai TOOLS.md. Note on prod-jin vs prod-jin-app: the kernel front-door process is prod-jin/dev-jin (imajin-ai monorepo). This app's process is named prod-jin-app/dev-jin-app to avoid the collision.

Fork-and-PR is the standard (see imajin-ai AGENTS.md). Work from your own fork under your own GitHub identity; open PRs into ima-jin/jin:main. No feature branches on the org repo.

MIT — see LICENSE.