Skip to content

Development

sarr-io edited this page Sep 14, 2026 · 1 revision

Development

Repository layout

Keep the Image source and repository tooling separate:

package/
  entry.lua
  src/
  docs/

tests/
tools/
README.md
build.zig
.github/workflows/

Every .lua and .md file below the Image source directory is compiled as a module. Put runtime state, models, generated data, tests, and tools outside it unless they are intentionally package modules.

Split trusted source by ownership rather than by generic utility. Keep a callable member beside the prompt or document that describes it when the package is model-facing. Keep byte parsing at the boundary and pass typed values internally.

Development loop

  1. Format the Zig and Lua source.
  2. Build the runtime.
  3. Run agent check against the package entry.
  4. Exercise root calls, Imports, host wrappers, and batch Eval.
  5. Run the regression suite and inspect the Image contents.
  6. Package the runtime Lua/native-module closure.

Tests verify contracts; source defines them. Documentation examples should be small copies of source patterns, not alternate implementations.

Clone this wiki locally