Tetrodotoxin documentation

The Background essay explains how years of custom tooling led to Tetrodotoxin. If you'd rather begin with something running, the Godot lab shows the same ideas through image operations supplied by GDScript, C++ and CUDA. The two paths meet at a fairly practical question: what do independently built systems need to agree on before they can use each other's work?

TTX provides the foundation being used to explore that question. Its Data layer describes concrete formats and access. Semantic negotiates what an interface means and whether its representation agrees. Concept adds the questions and policies that let a provider expose more of its domain without sharing its implementation.

Finding your way through the project

If you want to…	Start here
Get an overview of the architecture	TTX
Run the application example	Getting started
Look up how the main pieces relate	Core concepts
Follow the design reasoning	Design chapters
Read about development with coding agents	Research
Work on an implementation or review	Development

The Godot providers exercise these foundations in an application. The Source and dialect work is bringing the same agreements into the toolchain, where ownership, incomplete source and emitted results add other problems to solve. The larger Build, Package, Workspace and cross-language editor work grows from that effort.

These pages explain why the pieces have their particular shape and how the examples use them. For an exact callable signature or borrowing obligation, the contract comments beside the implementation are the more useful reference. The generated package pages preserve an earlier snapshot and are marked accordingly.