Leave the Durable Jazz AI Boundary Open

Context

Projects and chat demonstrate an experience, but their current storage and direct model execution do not provide a durable customer service.

Decision

Describe the memory-backed console prototype and propose isolated durable ownership with metered replies and AI access controls, leaving the customer-ready boundary to Product.

Alternatives Considered

Move storage and replies to Platform immediately: It is the proposed direction and needs explicit ownership and a declared reply operation.

Limit use to demonstrations meanwhile: It is a compatible interim choice rather than an implemented access restriction.

Offer the current prototype as durable customer history: It mixes the sample owner across callers, loses updates and bypasses Platform controls.

Consequences

Customers should not rely on process-memory history for durable work. The existing screens provide the observed baseline without establishing approval. Live query refinement already uses metered generation, but its conversation isolation, persistence and history consistency still require work.