Compatibility and coverage

Roll20 and Foundry 1:1 feature support is Talerook's minimum product bar, to exceed over time. The foundation is an implementation slice; it does not claim that this bar has been reached.

The repository's living ledger is docs/product/parity-ledger.json, with a reading guide at docs/product/parity.md. It preserves source references and verification gaps rather than presenting an unsupported parity score.

Record capability evidence

For each competitor capability, record its source URL, product/version, check date and whether it is native, an add-on or unknown. Keep paid, preview, community and system-specific status explicit. Then record Talerook's native, add-on or unknown route separately from its implementation and verification status.

Field	Example value
Capability	Table measurement tool
Competitor route	Native, add-on or unknown
Source and date	Exact owning documentation URL and check date
Talerook route	Native, add-on or unknown
Delivery evidence	Owned paths, checkpoint and observed workflow
Remaining gap	Unimplemented, unverified or bounded difference

This is a recording format, not a parity score. Unknown is a gap to investigate. An extension listing is discovery evidence, not proof that it works in the current product. An API type, passing unit check or visual mockup is not a completed user workflow.

Current SDK preview

The public contract covers commands, tools, layers, systems, panels, presentation and events. The beacon example exercises several surfaces through one extension. Lifecycle, capability and cleanup checks establish bounded invariants; browser acceptance establishes the specific adapter workflow it observes.

Still to deliver and accept: persistent extension state, upgrade/distribution workflows, untrusted-code isolation, full rules coverage, broader catalogue parity and an outside developer's extension exercise. These remain in the product's scope. Earlier narrower SDK recommendations are dated research and do not lower the accepted bar.

Versioning

SDK_API_VERSION is 1; manifests declare apiVersion: 1. Packages remain a private 0.1 preview. API version, extension version and system source schema version describe different compatibility boundaries. No indefinite old-runtime support or stable public package commitment is made by this preview.