Runtime Ownership Boundaries

Understand which repository owns native runtime code, web bridge behavior, and Dart integration changes.

On this page

llamadart follows a zero-patch strategy for upstream runtime ownership.

Rules#

Do not patch upstream llama.cpp sources in this repo.
Do not add local native build graph changes that belong in llamadart-native.
Do not treat bridge runtime internals as owned by this repo; those belong in llama-web-bridge.

Where changes should go#

Native wrapper/runtime behavior: llamadart-native
Web bridge runtime behavior: llama-web-bridge
Published bridge assets: llama-web-bridge-assets
Dart API/runtime selection/docs/tests: llamadart

Why this matters#

Keeping ownership boundaries clear avoids drift between:

bundle publishing pipelines,
runtime contract implementations, and
consumer-facing Dart APIs.

It also keeps this repo focused on integration correctness.

Edit this page