Pirates
Link task scope, permissions, and verification evidence.
Implementation flow
- 01Task
- 02Scope & permissions
- 03Provider review
- 04Evidence checks
Diagram of the implemented structure, not a live run or a performance result.
The question
How can an AI task’s completion claim be checked against its allowed scope and actual evidence?
What I built
Task packets, scoped permissions, verification evidence references, execution-scope binding, and a bounded provider-review pilot.
A technical decision
Require evidence to belong to the current execution scope. Keep a read-only provider review from authorizing business-state changes.
AI’s role
A bounded, opt-in provider-review pilot. This is not a completed autonomous software-production or sales system.
Current status
In development independently of WriteCore. General autonomous execution and production outcomes are not established. The site does not depend on its completion.