How a worker is assembled
Different jobs, different stacks.
Every digital worker is put together from four decisions. Change the role and all four
change with it — which is why a research worker and a security reviewer are not the same
system wearing different names.
- 01 Model
- Chosen for the work the role actually does, and re-examined as better options appear. No worker is permanently married to one provider.
- 02 Skills
- The specific competencies the role needs — extraction, comparison, drafting, review — rather than a general instruction to be helpful.
- 03 Tools
- The instruments the job requires: a query engine, a document store, a test runner, a case view. Given deliberately, not by default.
- 04 APIs
- Connections into the systems the role legitimately works with — and only those. Reach is part of the job description.
What a worker may reach is an authority question, and IrisKey.ai™ answers it. Scoping a
worker narrowly is good design; it is not, on its own, a permission model.