One list, several keepers, every change on record

A team is a research desk's shared keeping: the owner's plan sets how many seats it has, each seat is a wallet address, and every seat sees one shared list of mints and the trail of who added or removed what. Evidesa stores addresses, names and notes here — it does not scan an address for being kept, and no score moves because a team exists.

Your own watchlist stays yours; the team's list is a second, shared one. Monitoring is a different instrument again: the evidence watch and your delivery destinations tell you when recorded observations change. This page tells nobody anything.

No signed-in session

A seat belongs to an address, so a team needs one: sign in with a wallet signature and the seat that address holds is yours. Every reading surface works without this — only keeping things together does not.

What a team does not do

Watch anything by itselfNo read runs because an address is on the team's list. Incidents still reach only the delivery destinations each seat registered for its own watchlist; alerting the whole team from this list is not built, and this page will say so until it is.

Judge anything, or anyoneA seat is a place at the bench, not a statement about the wallet that holds it; an entry is a bookmark, not a finding. The dossier reads the same for every seat and for nobody.

Rewrite its own historyThe audit trail is append-only in the database itself, not by convention. Removing a seat or an entry is recorded as a removal; nothing here is deleted.