What shipped in v7: comments, @mentions, and reviewers who never get forgotten

v7 is live for every beta workspace. It has two themes, and they're really the same theme: the conversation about a contract should live on the contract, and nobody — reviewer or teammate — should be forgotten just because they're busy. Here's what shipped, honestly described. The release notes remain the canonical record.

Comments that live on the contract

Until now, the discussion about a contract happened everywhere except near the contract — reply-all threads, chat messages, hallway summaries. v7 gives every contract a threaded comment section: write comments and replies, and the thread stays attached to the thing it's about.

The details are the part we sweated. Access is scoped — the contract's owner, admins, delegates, and anyone tagged into the thread — so a comment is never broadcast wider than the contract itself. You can edit or delete your own comments; edits are labeled, and a deleted comment leaves a visible tombstone saying who removed it, because an audit trail with silent holes isn't an audit trail. The comments guide covers the mechanics.

@mentions with an actual lifecycle

Tagging someone is easy to build. The hard question is what happens when they don't answer. In v7, a mention isn't a fire-and-forget ping — it's tracked from the moment it's made until someone deals with it:

• Seen happens automatically when the tagged person opens the thread — no manual "acknowledge" step to perform, and no pretending an unopened mention was noticed.
• Resolve means handled; dismiss means no action needed; reopen fixes a mistaken close.
• Nudge lets the tagger or an admin send one more prompt if a mention sits.
• Escalate raises an unanswered mention to the admins, and mentions that sit untouched also surface in the admin oversight queue on their own — so a request for help can't quietly die in someone's inbox.

There's one automatic nudge, too: a mention nobody has touched after three days gets a single reminder email. One. If a person hasn't answered after a tag, an email, and a nudge, the fix is human, not more automation. Every mention lands in a tagged-items inbox on your dashboard, with an unread badge in the sidebar. The full state machine is in the mention lifecycle guide.

Why mention emails contain no comment text

When you're mentioned, the notification email tells you who tagged you and on which contract, with a secure link to the exact comment — and deliberately nothing else. No comment preview, no excerpt. Email gets forwarded, auto-scanned, and synced to personal phones; the substance of a contract discussion shouldn't ride along. Clicking through takes you to the comment after you're signed in. It's a small decision that follows from the same principle as our storage model: confidential content stays where access is controlled.

Reviewers who never get forgotten

The other half of v7 is for the most common failure in any review flow: the reviewer who simply hasn't gotten to it. Manual one-click reminders have been in Pishik from the start. v7 adds automatic reviewer reminders, with controls we'd actually want as recipients:

• Cadence: remind pending reviewers every 1–30 days — you pick the rhythm.
• A total cap per reviewer, so automation never becomes harassment.
• A send time on your clock, so nudges arrive during your working day, not at 3 a.m.
• A hard 45-day cutoff: once a review has gone quiet for 45 days — no send or reminder in that window — automatic reminders stop entirely. Past that point a robot nudge is noise — pick up the phone.

Each reminder also refreshes the reviewer's link, so a nudge never points at a dead link. Setup lives in Settings, and the auto-reminders guide walks through it; the workspace default can be overridden per person.

Also in v7

Per-user preferences arrived alongside the headline features: your default landing view, default contract type, and whether mention notifications email you are now yours to set, independent of workspace defaults. And the long dropdowns around the app — reviewers, teammates, contract types — became searchable pickers, which matters more than it sounds once your reviewer book grows past a screenful.

That's v7. As always, if something doesn't behave the way this post says it should, we want to know.