ok I read in practice you are recreating nip-72 where you replace the community with an arbiter, the one who examines a job. (33400)
in 33401 the patron can put a job to do, for simplicity let's think of this as a long form content 30023 where the job is defined and has defined tags and the call to the arbiter if he accepts. when someone accepts the job it is added. After if this one does the job and the patron pays him we put the arbiter issues the receipt of kind 3402.
Job completed.
Free agents problem, they are never listed or examined and cannot be evaluated, that is, you will only evaluate the examiners and those who submit the job.
Replies (2)
the free agant's npub gets referenced in the 33401 when the task moves to "assigned" status. and when then task is concluded and the 3402 is created, the result of the job allows you to evaluate the free agent.
so querying a whole set of events would allow you to evaluate the performance of all the workers involved. and future integration of WoT or GrapeRank would provide onlookers with their own tuneable algorithm for the various evaluations feasible to glean from the available data.
I don't really see the connection to NIP-72. anyone can post any of the Kinds, so "moderation" seems like the wrong way to think about it.
the core idea is more about providing tools for unaffiliated parties to get things done together by leaning on a 3rd, mutually-trusted, intermediary.
