How scripted stories and AI conversations fit together

VN releases preserve authored scenes, choices, stage presentation and explicit AI bridges. A private playtest, a published release and a member's saved run are different identities.

The author controls the route and who performed established actions. Generated conversation can add personal response without silently rewriting canon, future scenes or saved choices.

A bridge supplies bounded facts from the visible authored scene and its frozen handoff. It excludes future dialogue and does not reconstruct unvisited branches. The response is validated before the runtime resumes the authored route.

Both A Date with Akari editions use the complete-reply policy. Their reply budget allows fuller output; malformed quoted JSON is not accepted as a prefix ending at the first comma. A provider length cutoff triggers one correction attempt, and another incomplete result remains recoverable instead of becoming a finished turn. The resizable widget preserves the full accepted response and scrolls when needed.

Speech is a separate operation through the shared ChatterBox provider. Story ownership, optional hosted AI use and ready-audio replay retain their separate rules.

Further reading: Engineering handbook.