-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Zinc is a small memory and navigation layer for shaped work.
It stores package identity, package roots, exact request and result bytes, current heads, and opaque configuration values. Zinc does not interpret package behavior. Packages decide what their software, settings, models, scripts, and documents mean.
Use Zinc when you want a stable record of work without making the core responsible for every kind of software behavior.
- Remember which packages are installed.
- Read package manifests and files by URI.
- Store exact request and result bytes as fragments.
- Move a target/request head to the fragment that produced the result.
- Keep configuration values opaque.
- Run package software through a simple file-based request boundary.
Zinc is not a package execution layer, model execution layer, shell layer, policy engine, or output type system.
That is intentional. Package behavior changes often and varies by provider, platform, and human preference. Zinc stays small by remembering facts and moving pointers instead of owning package semantics.
| Page | Use it for |
|---|---|
| Architecture | How Zinc fits with Circuitry, packages, and Limbo. |
| Fragments and Heads | Exact byte records and current pointers. |
| Packages | Package identity, manifests, and installation facts. |
| Package Software | How Zinc runs package software without owning its behavior. |
| Shapes | How Circuitry shape bytes are stored and used. |
| Executor | How zn run advances work. |
| URI Reference |
zinc:// read paths. |
| Update | Zinc self-update behavior. |
Zinc's strongest opinion is also its smallest: remember exact bytes and move heads.
That keeps the core understandable. A fragment is a record of one piece of work. A head is the current pointer for a target and request. Packages interpret bytes however they need.