Validating Gems

Validators are responsible for insuring that the work has been completed based on the success criteria. They guarantee the result having skin in the game, as well as risk reputation and trust within the sphere if their analysis is found to be wrong later.

Validating

As a Validator your activity feed will display when the sphere has determined a Gem is up for review, through several methods. Once you have completed your due-diligence you reach the final ranking step.

Success Criteria

In some cases the title may be used in lue of success criteria if it is specific enough.

Therefore a sphere may have anywhere from zero or a dozen or more success criteria and all must be validated as done.

If a validator is "only caring if the success criteria has been met.” Then they’re failing as validators.

Ranking by Community Votes

Members within the sphere have opertunties to rank Gems against the value of the Sphere.

LV displays the values of the Gem (aggregated from all activity) and the current values of the Sphere. As Validator you give the Gems final ranking of the sphere.

Notifications

In ideal circumstances notification of updates should be seen by the validator and validators should not rely on the Gem to be marked as done.

For a GEM to be completed the Success criteria should be verified.

The Member with the Validator role is the one staking their reputation.

Final Ranking the Gem

Example

The work of a validator is understanding and evaluating whether success criteria have been met successfully. Some gems will be simple, and have no success criteria...e.g. If the gem is "take out trash today" the title contains the success criteria implicitly, so the title is evaluated.

However, we could add some success criteria...which may include

• all interior containers are emptied of refuse
• all indoor receptacle liners are replaced
• all bins are wiped down
• the bin is at the curb
• etc

The validator is the one who says "yes these have all been complete".

So now the system may occasionally pepper in other member's feed the "take out trash gem" to confirm completion...it only takes one person to anonymously say "Chuck didn't wipe down the bins" for the recently completed, validated, and paid out gem to be called into question, represented to the original team of owners and validators and deductions made to owners and validators.

Validators may occasionally get rewards for denying false claims of completion, but this would be a randomized reward.

Validation is not a passive activity. It's critical to the success of every sphere.

Rework

Rework is one of the most egregious acts in Ludum Vitae. Rework is one of the most insidious and sneaky wastes of time because people look busy when they're actually wasting time because they didn't do it right the first time. Validators are not paper pushers waiting for signals. Validators are judges of right and wrong and they must be excellent communicators of why success criteria have not been met when validating. This is their number one job. Read success criteria, and confirm or deny the existence of the success. If they do not do this well, then they should not be validators. Creators and owners are by default validators because the presumption is that they are the best judges of what "done correctly" means and looks like. This is not a system thing. This is a conscious thing. Validators may receive signals from the system, but this is not a priority for us. The expectation is that validators are engaged in gems and watching them for opportunities to validate completion. If we have to signal validators to do their job then we've failed in the design of the game. People should anticipate validations and they should be significant events with people knowing they've done the job or knowing the validator will not validate because the success criteria have obviously not been fulfilled.

History

A validator remains connected to the GEM even once it is completed and all parties have been rewarded. In some cases it is possible for a Member to pay tokens to resurrect old Gems and question the validity of them if new information was unearthed. It is possible within the game to be challenged for historic choices.

Members with Detractor Roles may be validated as being right after the fact, given they had predicted the ultimate outcome of a chain of Gems. This can be handled different ways, it may even be for to a vote.

Simple Mobile Interface for Validation and Votes

The sphere encourages daily mobile engagement through a user-friendly interface that facilitates quick check-ins and effortless interaction,

• Simplified Voting: Engage with a swipe-based voting system that allows you to validate actions or decisions with minimal effort.
• Action Validation: Accept or Deny Offers and Requests with ease, streamlining your daily game progress.
• Stay up to date: Keep a eye on what is going on in the sphere without having to be on your desktop.

Apophantic Logic

If a task doesn’t meet success criteria then it’s a failure, by definition. Validators are the SECOND line of defense against failure. OWNERS and CREATORS are the 1st line of defense against failure - by simply making sure the job gets done right THE FIRST TIME (critical).

If (as the first line of defense against failure) an OWNER isn’t making sure that the task is completed successfully the first time (or PROGRESSING in a reasonable manner), then they have wasted their own, and any other owner’s and contributors (worker’s) time. THIS WILL BE PUNISHED by LUDUM VITAE through lack of reward, diminution, voluntary removal of supporter & other owner (and encouragement - again diminution targets supporter and contributor token rewards as well) token contributions to gems, negative validator & community comments, etc.

Now, then, if validators also fail to point out any of the above failures with owners, and actually validate truly incomplete gems &/or success criteria as complete, the only true way for this to be known is someone else discovers this.

Gems must be unique, not only among active tasks - but completed tasks. If someone creates a new Gem that is a duplicate of a completed gem (or “near enough duplicate”) they will be notified, and encouraged to communicate and collaborate with the old duplicate gem owners and validators to justify the creation of the new gem with distinguishing characteristics (like a new & different date) OR the gem may be resurrected for a discount, and all owners of the previous gem will have a deduction of twice the merit and token rewards previously allocated.