Services
Delivery models and flagship work
Alopex Family
Asopitech Labo
NiminoDesktop
A lightweight WebView desktop foundation in Nim
NimculusEditor
A GPU-native editor in Nim and Metal
PoieraPlatform
A control plane concept for AI agents, carrying compact contracts through authorization, deployment, and verification
TheatoraBackend
A composable backend construction kit concept for swapping providers, runtimes, and topology
RhyzoraFramework
A concept for building CLI, TUI, Web, desktop, and MCP interfaces from declarative contracts
Labo overview
What the R&D lab is working on
Enterprise plans
ASMATI・TATSUMIEXPERIMENT NOTE
Series promise
Asmati Tatsumi does not stop at names found in generated output. Each article compares source code, definitions, generated artifacts, and execution results until the evidence supports an implementation decision.
2 published articles
A reproducible experiment series explaining how Nim source code becomes generated C, concrete types, and runtime behavior.
EPISODES
ASMATI・TATSUMIEXPERIMENT NOTE 01
What C types do NI and NF actually denote? This Nim 2.2.10 experiment follows their definitions and the debug arithmetic they select.
ASMATI・TATSUMIEXPERIMENT NOTE 02
Does a function name in generated C make it callable from C? This experiment checks the public header, symbols, and runtime initialization.
What C types do NI and NF actually denote? This Nim 2.2.10 experiment follows their definitions and the debug arithmetic they select.
Does a function name in generated C make it callable from C? This experiment checks the public header, symbols, and runtime initialization.
