Track records

What does a member's history say about them, and what can never count against them?

A track record counts outcomes, and only of Tasks the member finished. Nothing a member says about themselves enters it, and nothing they decline to do does either.

A window a member lets close moves the Task to the next member and changes nothing on their counts. A new member's first probation.tasks are all sampled, and until they are done the member ranks by fit and speed alone.

A member contests a send-back their attested work received. When a rules row reserves the act, a credentialed peer rules it, never the brand that sent it back:

• Its own Task. The contest posts a Task, offered by cascade to members who hold the same credential in the same region.
• Blind. The peer reads the work, the send-back and the reason, and neither member's name.
• Paid. The peer is paid the original Task's fee, funded by the brand, whichever way they rule.
• Staff rule the rest. An act no row reserves is ruled by the owner or a staff role, from the console.

→ POST /reviews/tsk_7Hv5/attest {"output":{"ruling":"upheld","memo":"The inventor list matches the declaration; the send-back was right on claim 2."}}   # as mbr_7Hq9, the peer the contest Task reached
← 200 tsk_7Hv5 · done · contest · ruled · upheld · $150.00
  14:40 · task.ruled · tsk_7Hq2 · upheld · by peer · mbr_7Hq9 · patent agent · no finding of bad faith
  14:40 · pay.accrued · mbr_7Hq9 · attest · $150.00

A contested send-back stops counting until it is ruled, and one overturned never counts. A client's contest of a party_silent visit runs the same way. A ruling is the only way to record a finding of bad faith, the one exception to pay that is never clawed back.

A Pool's tiers turn the counts into tiers, low to high, and a Task is offered to the top tier that's eligible first. The fill ladder's widen rung opens the next tier down. A member reads their own tier, and how far the next one is, in the delivery portal:

rank: ['track'] orders a cascade by the same counts.

A track record belongs to the member. GET /me/track returns their counts per Pool and brand, with the hash of each Task's artifact, signed by the door and naming no party:

→ GET /me/track   # as mbr_7Hq2, on gigs.lawyer

  attorneys · api.lawyer               118 attested · 3 sent back · 97% on time
  attorneys · patent.click              24 attested · 0 sent back · 100% on time
  work register                         none
  tasks     142 hashes, each sha256 of the act's artifact · GET /me/track?hashes=true
  shared    with every Pool on gigs.lawyer · with other doors only when you choose, at their /join

Every Pool on the same door ranks a member from that one record, and a tier is always the Pool's own. A Pool on another door can seed its tiers from it with tiers[].from, such as from: ['gigs.expert'], but only from a record the member chooses to share when they join:

→ POST /counsel/join {"email":"grace@example.com","answers":{"records":"share"}}   # on another operator's door, tiers: [{ name: 'senior', from: ['gigs.lawyer'], after: 100 }]

← 200 mbr_8Kp1 · counsel · grace@example.com · applying, step 3 of 3 · on
  records   gigs.lawyer/attorneys · 142 attested · 2.1% sent back · 97% on time · share it? yes
  tier      senior, seeded from the shared record · the tier is this Pool's own, and moves only on its own Tasks from here

The same outcomes are what an AI step's record holds, so the owner console sets the two side by side and shows when a person at a step no longer changes the work. golden scores a share of Tasks with a known answer, for quality only.

Worked in: the closers' Pool, counted and not counted.