Developer Guide (Internal)LINA v5

LINA Architecture

LINA is the interaction and voice runtime layered on AIJIM Core. It still owns local session and voice behavior, but its audit-grade persistence now flows through Core-owned routes.

Current Positioning

What LINA is

The interaction, voice, and assistant orchestration layer inside `apps/aijim-app`. It owns browser/runtime behavior, session-state, and the human-facing assistant surface.

What LINA is not

It is no longer the normative owner of replay/publication/signature/signer persistence. Those writes are Core-owned and reached through proxy routes.

What stayed local

Voice transport, wake-state, turn telemetry, session-events, and RAG-local state remain under LINA ownership.

What changed

The old parallel audit stack was absorbed into the Core-first architecture. LINA now acts as the interaction layer over that contract.

Proxy Model

LINA-facing audit routes continue to exist in the Next app for ergonomics and request-shape stability, but they now proxy to the live Core surface on managed runtime. That means browser-originated audit traffic still enters through Next.js, while invariant-critical logic executes in Python.

Browser / LINA action
    -> /api/lina/* route in Next.js
    -> proxy to AIJIM Core on managed runtime
    -> Core router validates + writes
    -> Supabase persists transitional audit tables

Retained LINA-Local Domains

Voice pipeline and renderer coordination
Session-events and turn-level memory
Wake-state, proactive signaling, and HUD behaviors
RAG corpus and assistant-local retrieval flows
Client-side orchestration around the shared stage UI

Boundary reference

For the formal ownership split, vocabulary contract, and exact proxy mapping, see /architecture/lina-core-boundary. The authoritative source artifacts remain documentation/runbooks/LINA_CORE_BOUNDARY_CONTRACT.mdand documentation/runbooks/AIJIM_CORE_FIRST_OWNERSHIP_MATRIX.md.