Five kinds of tool, one way to govern them
| Kind | The question Substrait answers about it |
|---|---|
| Slate | Who may see it, and who may change it? |
| Knowledge base | Who may see which parts, and is it current? |
| Skill | What does it allow, and what does it instruct? |
| Web app | What data may it reach? |
| Agent | What may it do on its own, and as whom? |
Every kind shares the same spine: identity, data access, audit, a review before release, and a life cycle of publish, version, install, retire and revoke.
What each entry records
- The owner, and the people who hold a role on it
- Its purpose and its risk tier
- Every version, and which one is in production
- The data it was granted, and by whom
- The scaffold version it was built from, flagged when out of date
Installing creates a link, never a copy
When a team installs a tool, Substrait links to the one registered version. A copy could not be revoked or kept current; a link can.
Every tool can be stopped
Every tool on Substrait can be rolled back to its last good version or switched off.