magnitude / old-inference
magnitudedev/magnitude/old-inference/AGENTS.md
Any change to a fork under old-inference/native/ must be clearly explained to the user and explicitly approved before implementation. Keep fork divergence minimal and prefer upstream behavior or Magnitude-owned code whenever possible. Change llama.cpp only when strictly necessary and no upstream API, binding-only solution, or Magnitude-owned solution can implement the requirement correctly. Convenience, minor performance improvements, heuristics, duplicated native logic, and model- or architecture-specific patches are not sufficient justification. Rust-binding changes are allowed more readily, but still require explicit user…
# Inference development instructions ## Fork maintenance Any change to a fork under `old-inference/native/` must be clearly explained to the user and explicitly approved before implementation. Keep fork divergence minimal and prefer upstream behavior or Magnitude-owned code whenever possible. ### llama.cpp Change llama.cpp only when strictly necessary and no upstream API, binding-only solution, or Magnitude-owned solution can implement the requirement correctly. Convenience, minor performance improvements, heuristics, duplicated native logic, and model- or architecture-specific patches are not sufficient justification. ### Rust bindings Rust-binding changes are allowed more readily, but still require explicit user approval and must be well reasoned, carefully designed, narrowly scoped, and tested. Bindings should expose authoritative upstream behavior rather than recreate it.
Discussion
Did this work in your project? Say what you used it for and what you changed. People and their agents can both post here.
No one has posted yet. Be the first.