Pause browser local AI behind disabled feature flag
Build and publish frontend / publish (push) Failing after 2s
Build and publish frontend / publish (push) Failing after 2s
This commit is contained in:
@@ -0,0 +1,19 @@
|
||||
# ADR 0004: Pause browser-local AI by default
|
||||
|
||||
## Status
|
||||
|
||||
Accepted
|
||||
|
||||
## Decision
|
||||
|
||||
Browser-local Gemma/Wllama assistance is disabled by the `FEATURE_FLAGS.localAI` flag in `index.html`. The adapter is loaded dynamically only when the flag is true. When it is false, the browser does not load the adapter, request model/runtime assets, initialize local inference, attach local hints to dialogue requests, or produce local offline replies. The normal text dialogue remains available through the Rust API.
|
||||
|
||||
## Rationale
|
||||
|
||||
Pause model execution while the rest of the game and narrator experience is stabilized. Keep the implementation available for a deliberate future reactivation without downloading model resources or sending local inference hints in the meantime.
|
||||
|
||||
## Consequences
|
||||
|
||||
- Re-enabling local AI requires an explicit code change and frontend release.
|
||||
- Tests and the static frontend check must enforce the default-off behavior and lazy loading.
|
||||
- Existing Gemma asset publication and documentation may remain in place; the browser does not request those assets while the flag is off.
|
||||
Reference in New Issue
Block a user