AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
Web editor primitives for Quillmark
Translation pending
Developer toolsTypeScript · SvelteGitHub @borb-shOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Loading the full README. The saved excerpt is shown below.
The JavaScript tier downstream of the @quillmark/wasm artifact.
A quill author types one name, quillkit, and pins two: the tool resolves the loader and the engine out of the collection's own node_modules, so the versions a collection depends on decide what packs it and what renders it. The client it draws with is the tool's own, carried rather than resolved, since no version an author pins makes a client more theirs.Read the full README ↗The JavaScript tier downstream of the @quillmark/wasm artifact.
| Package | |
|---|---|
@quillmark/svelte | Editing, live-preview and source surfaces over a session. |
@quillmark/quiver | Collections of quills, resolved and loaded. |
@quillmark/fonts | The font suite every client hands its engine, so a family a document names sets the same way everywhere. |
@quillmark/collab | Live editing: a Document bound to a shared Yjs state, and the session log its clients merge through. |
quillkit | The quill author's toolchain: one bin over start, gate, look at, build and preview, and the studio and app clients it lays. |
playground | The app that composes them, for a developer reading the library; deployed as the Pages site. |
A quill author types one name, quillkit, and pins one: the tool carries the loader, the engine and the font suite at exact versions, and its clients are built against the same three, so what the gate renders and what a deploy serves are one release.
A package whose JS a consumer imports peers @quillmark/wasm and never depends on it, so the consumer supplies the one copy whose linear memory the handles index into; a bundled terminal, imported by nobody, contains it instead, and pins it exactly. check:deps holds both halves and the rest of the graph (scripts/check-deps.mjs).
npm install # one install, every package
npm run dev # the playground at :5173
npm run dev:studio # the studio client at :5173
npm run build # quiver, svelte, fonts and collab → quillkit and the playground, in that order
npm run site # the fixture quiver's studio as a deploy serves it, into ./site
npm test # every package's suite
npm run check # types, per package
npm run lint # prettier, over the repo
npm run gate:fast # every check below, in order, without a build
npm run gate # gate:fast, then build, bundle and the suite
npm run check:docs # every cross-doc section reference, and the stated wasm pin
npm run check:style # the closed `--_qm-*` / `--pg-*` / `--st-*` scales
npm run check:deps # the dependency law
npm run check:svelte # the Svelte 5 forms, over every package that depends on svelte
npm run check:fonts # the font suite's files against its manifest
npm run check:bundle # the same scales, in a built consumer
Everything runs against the one reference quill, fixtures/quills/showcase/1.0.0, a dev fixture at the workspace root, never published: it declares a field for every control the tier draws and three card kinds, so a surface is exercised against a schema rather than against a mock.
The settled systems, per tier: svelte's, quiver's, fonts', collab's, quillkit's (the tool and both clients), the playground's. Work that is not settled lives in GitHub issues.