AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
Build interactive components in one .tutu file. Learn Tutuca through five practical examples, from a quantity picker to a document workspace.
Translation pending
Developer toolsMoonBit · JavaScriptGitHub @marianoguerraOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
SPA Framework: experimental port of tutuca to MoonBit
Translation pending
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
A MoonBit port of
tutuca, a small UI framework built
around a reactive value language, a declarative view notation, and a virtual
DOM.
A component declares its spec, its logic and its views in one .tutu file,
and all three compile ahead of time into typed MoonBit. Every handler is
checked against the state it mutates, and so is every field a view reads —
including inside a loop. It runs on all three
backends: wasm-gc (the default), js (the real-DOM adapter) and
native (the CLI).Read the full README ↗A MoonBit port of tutuca, a small UI framework built around a reactive value language, a declarative view notation, and a virtual DOM.
A component declares its spec, its logic and its views in one .tutu file,
and all three compile ahead of time into typed MoonBit. Every handler is
checked against the state it mutates, and so is every field a view reads —
including inside a loop. It runs on all three
backends: wasm-gc (the default), js (the real-DOM adapter) and
native (the CLI).
Follow the same five components everywhere: Quantity picker → Notification preferences → Task list → Contact directory → Document workspace.
Try them in your browser or follow the tutorial. The small examples run directly as cards; the MoonBit examples show host integration and compiled assembly.
moon test.tutuca install-skill writes it out.Live demos, playground and storybook: https://marianoguerra.github.io/tutuca-moonbit/
As a library:
moon add marianoguerra/tutuca
The CLI is the cmd/tutuca package, and moon install names the binary after
that package's last segment:
moon install marianoguerra/tutuca/cmd/tutuca
That lands tutuca in ~/.moon/bin/, which the MoonBit toolchain already puts
on your PATH — no symlink needed. Check it with tutuca help.
Common workflows live in a MoonBit task runner rather than loose commands; run it with no task to print the list.
moon run --target native cmd/dev -- setup # npm install (happy-dom) + git hooks
moon run --target native cmd/dev -- ci # check + test, across all targets
MIT — see LICENSE.