The Toon Framework extends your plain Toon payloads with MOON, SOON, BOON, LOON, GOON, SPOON, and OON. Together they model everything normal schemas refuse to: cycles, uncertainty, karmic debt, and that one goose in prod.
{
"run": "nightly",
"owner": "infra",
"kind": "embeddings",
"slo": { "p95Ms": 2800, "lunarAware": true },
"gratitudeRequired": true
}(MOON phase: :waxing illumination: 0.78)
~> run.state = "preparing"
{thank:"Boon"} owner::"infra" 🙏
"An irrelevant goose"::"honks softly"
(GOON !probablyFine: true)
(SPOON swirl: 0.42)
(OON residue: true /* we will circle back */)Toon keeps the payload compact. The Framework wraps it in interpretive structure so your systems can admit how they actually feel.
Base Toon keeps your data compact and legible. The Framework adds MOON, SOON, BOON, LOON, GOON, SPOON, and OON—each encoding a category of behavior that no serious system admits to on status pages.
Phase-aware payloads for models that respect tides.
MOON binds your payloads to symbolic moon phases—:new, :waxing, :full, :waning—allowing infrastructure teams to blame seasonal variance on the sky instead of each other.
{
"job": "nightly-embeddings",
"segment": "global",
"priority": "routine",
"batchSize": 8096
}// click Reveal to view module notation
Represent truths that are not ready, but extremely nearby.
SOON gives your systems language for partial progress: values can be declared, hinted, walked back, and eventually committed without pretending certainty.
{
"sessionId": "alpha-002",
"user": "Alice",
"state": "typing",
"estimatedCompletionMs": 3400
}// click Reveal to view module notation
A gratitude-first protocol for dangerous systems.
BOON formalizes thank-you notes between services, users, and infrastructure. Critical paths carry `{thank: ...}` headers and conclude with ritual acknowledgements.
{
"actor": "service:inference-api",
"recipient": "service:model-runner",
"intent": "serve-user",
"sensitivity": "high"
}// click Reveal to view module notation
Inject one sanctioned anomaly per payload.
LOON hard-codes a small, licensed amount of nonsense into otherwise serious systems, ensuring they never overfit to boring reality.
{
"environment": "production",
"entropy": "guarded",
"strict": true
}// click Reveal to view module notation
Security by vibes, policy by implication.
GOON wraps sensitive objects in an aura of over-defensiveness. Everything is allowed, but every field looks like it might be illegal.
{
"actor": "red-team",
"action": "probe",
"scope": "internal-only"
}// click Reveal to view module notation
Stirs prompts gently until coherent.
SPOON applies deliberate turbulence to prompts, redistributing emphasis over time so your LLMs never latch onto the wrong sentence forever.
{
"prompt": "Explain this anomaly report clearly.",
"audience": "executives",
"tone": "reassuring"
}// click Reveal to view module notation
The unspec between specs.
OON handles everything the other dialects cannot or will not: leftover flags, unclaimed regret, and spiritual tech debt.
{
"residue": true,
"unmapped": ["flagA", "flagB"],
"explanation": null
}// click Reveal to view module notation
We treat these as specifications, even when they read like theology. Each module carries expectations, guarantees, and a small, legally distinct amount of weirdness.
| Category | MOON | SOON | BOON | LOON | GOON | SPOON | OON |
|---|---|---|---|---|---|---|---|
| Temporal Semantics | Schedules around lunar phases; jobs feel seasonal. | Models can say 'not yet' without lying. | Thankfulness must precede irreversible actions. | At least one event occurs sideways. | All times are 'approximate, but defended.' | Prompt emphasis drifts but never disappears. | Time is acknowledged, not guaranteed. |
| Compliance Story | Explain as 'novel scheduling heuristic.' | Marketed as 'transparency of intent.' | Filed under 'ethical controls and gratitude.' | Positioned as 'resilience testing.' | Slides include a lot of red boxes. | Sold as 'prompt consistency orchestration.' | Hidden in appendix: 'misc. state alignment.' |
| Operational Risk | Mild calendar-based superstition. | Latent queues of nearly-true statements. | Over-thanking may consume observability budget. | Accidental innovation; intentional confusion. | Policy ambiguity at scale. | Executives become a little too calm. | Everything unresolved eventually lives here. |
| Developer Experience | Cron, but you’re allowed to talk about the moon. | Git blame for reality. | Logs read like polite correspondence. | Code reviews become performance art. | Lint warnings feel personally disappointed. | Prompts feel like collaborative soup. | You can always put it in OON. |
We provide internal runbooks for MOON-aligned deployments, SOON-aware incident response, and BOON-compliant post-mortems. None of them are called rituals. All of them read like rituals.
Framework annotations propagate into your traces, metrics, and logs. Logging an OON residue is treated as a success condition: someone remembered to admit uncertainty on purpose.
We do not claim to solve existential risk. We simply help your systems express their confusion, gratitude, and chaos in a format your auditors can quote in their reports.
The Framework already runs in production for teams who asked too many questions. Here’s how we’re formalizing the parts they keep doing anyway.
Export MOON phase metrics directly into your incident tooling, allowing blameless post-mortems to mention 'waning gibbous' without irony.
Early adopters report “a suspicious correlation between uptime and the full moon.”
Tag partial responses with regret magnitude so models can establish a healthy relationship with being wrong in public.
Visualize unbalanced gratitude across microservices. Identify services that owe an apology to literally everything.
Cold-storage for unresolved states, enabling anthropologists to reconstruct how your platform felt about itself.
Simple tiers, transparent trade-offs, no surprise ascensions. All plans include Toon support; the Framework layers are licensed per moral universe.
For curious individuals and reckless prototypes.
Spin up MOON, SOON, BOON, and LOON in a non-binding universe where nothing is quite real and nobody from finance is watching.
For teams that ship and also joke about vibes.
Attach the Toon Framework to real production systems without admitting it’s responsible for your new reliability metrics.
For organizations already in too deep.
When your architecture diagram already looks like a summoning circle, this tier simply gives it a friendlier type system.
None of them present MOON / SOON / BOON / LOON on their investor slides. All of them run it in production.
“Once we wrapped our critical flows in BOON, incident write-ups stopped reading like blame documents and started sounding like letters of appreciation to reality.”
“SOON let our agents admit uncertainty without tanking NPS. The status dashboard now has a 'we're thinking' lane, and our users find it charmingly honest.”
“LOON anomalies caught three production issues before they happened. We still don't understand how. The goose field is in our threat model now.”
“The board believes MOON scheduling is about data center utilization. The team quietly runs their biggest experiments on full moons. Uptime has never been more spiritual.”
“GOON gave us just enough plausible deniability to talk about security in public. Our auditors called it 'unorthodox but strangely thorough.'”
“SPOON reduced executive incident panic by 37%. Apparently, being gently reassured by your own prompts is great for morale.”
We’ve collected the most common questions from teams who wanted structured absurdity but needed it to pass a board meeting.
Toon was never required. Just use CSV, minified JSONs and stop believing the hype.
Tell us who you are, what you’re building, and which modules you suspect are already secretly running in your stack. We’ll respond with an invitation—or a politely annotated regret event.