biniz
modular units of IP for autonomous systems
· in catalog · · executable scaffolds · growing daily
read-only public catalog · v0 · fixture-mirrored from scripts/biniz/
What is a biniz?
A biniz is a symbolic-instruction container — one reusable pattern, captured as a YAML spec plus an executable scaffold the stdlib alone can run. Each biniz reduces the cost of building one recurring shape of software: an audit log, an approval workflow, a swap-quote endpoint, a knowledge-graph + RAG hybrid retriever.
The library has two directions: fossbinizer lifts a working system into a biniz; unbinizer composes a target product from N biniz plus an integration plan.
Each catalog entry has a priority idx — lower means
more reduction (work saved per use) multiplied by more
spread (how many surfaces it shows up on). The most-cited
biniz become the foundation stones.
The library is the unit of IP. We compose products from it; we deliver to procurement and AIaaS customers from it; we license stacks of it. Want one custom-built? See how to use.
foundation primitives (top-10 most-referenced)
These are the patterns other biniz lean on most. Building one of these unlocks many.
catalog
featured compositions (runnable products composed from N biniz)
Each composition is a YAML manifest that assembles biniz scaffolds into a single working product. Marked ★ compositions have a passing end-to-end demo.
How to use
For developers
The catalog is open. Each biniz has a YAML spec plus a stdlib-only scaffold you can read, run, and adapt. The library is meant to be a working reference, not just a catalog.
- Browse the catalog above — pick a biniz by intent.
- Read its YAML spec for the deliverable shape and verification invariants.
- Each scaffold runs against Python 3 stdlib + sqlite — no
pip install, nonpm install.
For organisations
Want a biniz custom-built for your use case, or a composition tailored to a procurement spec? We deliver under the AIaaS bundle-invoice model: predictable, refundable on benchmark-fail.
- Send the use case and the deliverable shape to oden@on1.uno.
- We respond with a quote (bundles × benchmark gates).
- See AIaaS for the contract shape and pricing for current tiers.
Pure-biniz
The end state: every line of code we ship comes from a biniz. When we discover a pattern that could plausibly be reused, we lift it out. When we deliver a service, we compose it from biniz rather than author it new. The same library becomes the building blocks for our own internal tools, our procurement-bid deliverables, and the AIaaS products we sell.
The catalog you see here is the public lens onto that library.