About Batoi Exchange
Exchange separates public discovery and publication trust from entitlement, workspace installation, explicit binding, contextual execution, updates, advisories, rollback, revocation, and publisher support.
Discovery, procurement, installation, and execution are separate decisions. No stage silently inherits permissions from the one before it.
Browse publisher, asset type, current publication details, support owner, and stated availability.
Inspect provenance, signature, risk class, compatibility, permissions, data handling, documentation, and review status.
Approve applicable commercial, license, procurement, policy, and workspace eligibility conditions.
Create a version-specific workspace installation record. Installation grants no capability use.
An authorized owner explicitly binds approved capabilities to a Project, App, asset, environment, purpose, and identity scope.
Runtime gateways re-check identity, binding, policy, Guard status, expiry, rate, schema, and context before each protected action.
Review changelog, permission and processing diffs, migrations, compatibility, staged activation, and rollback before promotion.
Publish security advisories, deprecate versions, disable unsafe use, propagate revocation, and preserve incident evidence.
The publisher owns declared asset support and lifecycle duties; Batoi owns the Exchange channel and platform controls. Workspace operators remain accountable for installation, binding, and contextual use.
Published assets declare their trust and lifecycle properties; installed and bound use remains subject to workspace identity, policy, security, and runtime enforcement.
Publishers include:
Publishing requires adherence to:
Exchange assets are used by Studios and Systems but never replace them.
Exchange enables partners to productize expertise and deliver reusable value.
Frequently asked questions