jsonisch 0.1.0 → 0.1.1

package/CHANGELOG.md

@@ -1,5 +1,20 @@
 # Changelog
 
+## [0.1.1](https://github.com/andrew310/jsonisch/compare/v0.1.0...v0.1.1) (2026-09-08)
+
+
+### Bug Fixes
+
+* **ci:** match plain vX.Y.Z tags — the changelog scanned all history ([#25](https://github.com/andrew310/jsonisch/issues/25)) ([207b2ef](https://github.com/andrew310/jsonisch/commit/207b2efd238c23cf9223ea72ae46de995d565d9e))
+
+
+### Documentation
+
+* best-of-three names three real lineages ([#18](https://github.com/andrew310/jsonisch/issues/18)) ([fc6894e](https://github.com/andrew310/jsonisch/commit/fc6894e9149ee0e8fd02869a3c8bc67dfddc7d07))
+* lineage section states what we actually studied ([#19](https://github.com/andrew310/jsonisch/issues/19)) ([3e70c2c](https://github.com/andrew310/jsonisch/commit/3e70c2c6c249fc599bc7ab61f09e79f5537e5a82))
+* logo in the README ([#17](https://github.com/andrew310/jsonisch/issues/17)) ([0191401](https://github.com/andrew310/jsonisch/commit/0191401ca22c7410f9ec08061955540f63d0a406))
+* the agent angle — a schema an LLM just wrote is a form ([#22](https://github.com/andrew310/jsonisch/issues/22)) ([dd7c1d4](https://github.com/andrew310/jsonisch/commit/dd7c1d450500f8493f110493038519ea4a6a7dbb))
+
 ## 0.1.0
 
 First public release. Extracted from the RWA platform with history intact.

package/README.md

@@ -1,3 +1,7 @@
+<p align="center">
+  <img src="https://raw.githubusercontent.com/andrew310/jsonisch/main/assets/logo.jpg" width="220" alt="jsonisch — a database record between braces" />
+</p>
+
 # jsonisch
 
 > Schemas as values. A form library for apps where JSON-Schemas are **runtime
@@ -28,9 +32,10 @@ Most form libraries assume the shape of your form is known at build time —
 a Zod schema in a module, types inferred from it, a hand-written component
 per field. That assumption breaks the moment your app lets users customize
 their forms: now the schema is a **value**, fetched from a database at
-request time, different per tenant, edited without a deploy. There is no
-compile-time type to infer against, and nobody is hand-writing a component
-per field for a form that didn't exist yesterday.
+request time, different per tenant, edited without a deploy — or written
+by an LLM a second ago. There is no compile-time type to infer against,
+and nobody is hand-writing a component per field for a form that didn't
+exist yesterday.
 
 `jsonisch` starts from that world. It takes a JSON-Schema value, walks it
 once, and gives you a fully reactive, validated form with the fields already
@@ -51,6 +56,13 @@ wired:
 
 You bring the components; it brings everything else.
 
+That last part matters more in the age of agents. The cheapest thing a
+model can produce is a JSON value — and a JSON-Schema value is a complete
+form definition. An agent that needs structured input from a human can
+emit a schema and have a validated, fully wired form on screen in the
+same request: no codegen, no deploy, and the schema it wrote is the same
+contract that validates what the human sends back.
+
 ---
 
 ## Quickstart
@@ -156,22 +168,29 @@ formulas use to address the root record) and wires the dependency graph.
 
 ---
 
-## Where jsonisch sits — a deliberate "best of three"
+## Where jsonisch sits
 
-`jsonisch` is a synthesis of three lineages, picking one idea from each:
+Two libraries are real lineage — we read their source and took ideas from
+each deliberately:
 
-- **From TanStack Form** — the **framework-agnostic core + thin adapters**
+- **TanStack Form** — the **framework-agnostic core + thin adapters**
   layout, and the **`createFormHook({ widgets })` composition/registry**
   pattern: register your design-system widgets once, get a typed
   `useAppForm` with them baked in.
-- **From Formisch** — **signals** as the reactivity engine (its own, no
-  external signal lib), so a keystroke re-renders only the fields that
-  depend on it, and derived fields recompute automatically.
-- **New here** — the schema kind is **JSON-Schema**, not Zod/Valibot/Yup.
-  Validation runs through an injected AJV-shaped validator. Derived values
-  are computed signals over the formulas already declared in the schema, so
-  they're excluded from dirty-tracking and the submit payload *by
-  construction*.
+- **Formisch** — the **signal** reactivity model jsonisch's store is built
+  on (its own tiny signal implementation, no external lib): a keystroke
+  re-renders only the fields that depend on it.
+
+One more deserves naming: **react-jsonschema-form** has been rendering
+forms from JSON-Schema since long before us. jsonisch is not derived from
+it — candidly, we didn't study it — the resemblance comes from sharing a
+premise, not code. What's visibly different from here: jsonisch is
+signal-reactive, ships no components of its own (your design system,
+dispatched by control kind), injects validation instead of bundling it,
+and evaluates schema-declared formulas as computed signals — **derived
+values**, excluded from dirty-tracking and the submit payload *by
+construction*. A careful comparison would make a good doc; we haven't
+written it.
 
 The re-render question — "when I type one character into a 60-field form,
 what re-renders?" — has a two-decade history that signals largely closed,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jsonisch",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Schema in, reactive form out. Derive forms from JSON Schema.",
   "license": "MIT",
   "author": "Andrew Brown <andrewbrown600@gmail.com>",