Build for the whole table

Talerook's SDK connects engine commands, VTT tools and layers, rules systems, UI panels and presentation through one versioned extension contract. Each table owns its host; each extension owns the resources it creates.

Start with a working extension, then connect the contribution APIs to your renderer and application.

A public boundary, used by first party

Package	Responsibility
@talerook/sdk	Framework-free types, manifests and contribution contracts
@talerook/engine	Instance-scoped host, registration and lifecycle implementation
@talerook/rules-2024	First-party 5.5e validation, derivation and check workflow
@talerook/example-beacon	Tool, layer, commands, panel and presentation example

Extensions import these public package entries. They do not import application stores, renderer internals or database drivers. First-party extensions use the same registration APIs.

Private preview

API version 1 describes the current SDK contract. Package version 0.1 is a private preview and can change with coordinated consumer updates. It is not a stable public release or a sandbox for untrusted JavaScript.

The foundation implements a useful slice. Complete rules support, persisted extension data, upgrade workflows, distribution and external-author acceptance remain work to deliver. Coverage keeps those limits separate from the accepted Roll20 and Foundry parity bar.

Run the docs locally

From the repository root, use pnpm docs:dev and open http://127.0.0.1:4322. The dedicated docs app is built alongside the web app. docs.talerook.com is a future destination; this milestone does not configure hosting, DNS or AWS.