Conversation
| ## What's a Policy? | ||
|
|
||
| A Policy is an object that describes which _resources_ any given dependency can access. These "resources" include globals, builtins (e.g., `node:fs`), native modules, and other packages. _All direct and transitive dependencies_ in your application's dependency tree are subject to a Policy. | ||
| A Policy is an object that describes which _powers_ any given dependency can access. These "powers" include globals, builtins (e.g., `node:fs`), native modules, and other packages. _All direct and transitive dependencies_ in your application's dependency tree are subject to a Policy. |
There was a problem hiding this comment.
| A Policy is an object that describes which _powers_ any given dependency can access. These "powers" include globals, builtins (e.g., `node:fs`), native modules, and other packages. _All direct and transitive dependencies_ in your application's dependency tree are subject to a Policy. | |
| A Policy is an object that describes which _capabilities_ any given dependency can access. These capabilities include globals, builtins (e.g., `node:fs`), native modules, and other packages. _All direct and transitive dependencies_ in your application's dependency tree are subject to a Policy. |
Why "powers"? Is this an existing concept from elsewhere or minted here?
There was a problem hiding this comment.
It's a concept from Object Capability programming and I also defined iit in the glossary now.
You can't frequent Endo meetings to become more familiar with the terminology, but they're recorded and you can catch up on them on Agoric's youtube.
Here's an archive https://www.youtube.com/watch?v=tM5NyB7xxYM&list=PLzDw4TTug5O0eUj81Vnkp-mFuI4O0rBnc
Not sure if the latest ones were being added to the playlist. Check main channel.
There was a problem hiding this comment.
I'll shave the yak on the difference between capabilities and powers internally
boneskull
left a comment
boneskull
left a comment
There was a problem hiding this comment.
IMO calling this "policy review" doesn't really do it justice vs its importance. Nobody will know when or why to click on the link. It should probably be more clickbaity or otherwise draw attention to itself. You could add a "tag" to it, e.g., Important! or something.
Also needs cross-referencing in the getting started docs.
3 participants
Show the diff doc in sidebar and link up from policy doc