Osiris Schedulehow often, not just how Everything this involves, sorted by how frequently you actually do it
Schedule › Every time

Note the date

one line

The least interesting task on the site and the one that decides how a dispute goes.

Osiris addresses

Three published addresses for the same market. Copy rather than retype.

osiriseultmx3so5ef6ayasy4kdyekbywr7pyggpmjazeogxoyaodsyd.onion
osirislivpetlbabbl3zzqhupurfkxxbzbheu3bkrshkaiwg2hcxbyqd.onion
osirisydmlx47esm6ylhzhtnjrucgnymi7beqoyzze5jn3opbr3zy4id.onion

This list is published, not monitored. An address that opens is not an address that is genuine, and the check that settles it belongs to the every time list.

How often
Every session where anything happens: an order placed, a message sent or received, a window stated.
How long
One line.
What it prevents
Nothing directly. It is what makes a later dispute winnable.
If you skip it
You reconstruct from memory months later, and memory loses to a timestamped record every time.
How you notice you stopped
You cannot answer when something happened without opening the platform.

What to write down

Why the window matters more than anything else

A dispute is decided on a record. Dates, the message thread and whatever evidence exists. Filing before the window closes is the most common self inflicted mistake in this subject, because it is usually dismissed and the dismissal costs credibility on the resubmission that actually mattered.

A message cannot move the window either. Agreeing to wait past it, however politely it was requested, costs you the strongest version of your case.

A useful frameWrite every message as though a panel will read it later, because on some order it might. That habit costs nothing and improves your position if this ever becomes a case.

Where to keep it

The same file as your addresses, decided during the storage task. Not on the platform, because a record you cannot reach during an outage is not a record, and not in a message to yourself on somebody else's service.