§81's "animation systems" and, with the §84 statistics record, its
"diagnostics" point: the §39 ordered set of simulation systems.
The one revocable capability in the MVP, and the only one whose registry
really supports removal: SystemRegistry.register returns an idempotent
unregister and unregister(system) exists, so a plugin's own uninstall can
put the registry back exactly as it found it. Every other §81 token keeps
RFC 0002's conservative default (owner decision, Q3), which means a plugin
that touches one of them cannot be uninstalled at all.
§81's "animation systems" and, with the §84 statistics record, its "diagnostics" point: the §39 ordered set of simulation systems.
The one revocable capability in the MVP, and the only one whose registry really supports removal:
SystemRegistry.registerreturns an idempotent unregister andunregister(system)exists, so a plugin's ownuninstallcan put the registry back exactly as it found it. Every other §81 token keeps RFC 0002's conservative default (owner decision, Q3), which means a plugin that touches one of them cannot be uninstalled at all.(The plugin and context types live in
@fourjs/core; naming them here would trip the §96 boundary test's textual ban, which is blunt on purpose.)Provided by
Applicationfor every application that configures plugins: the registry isapp.systems, which the application owns outright.