Skip to content

Records

It was decided; it was never written down

The seven things real work actually produces — task, comment, decision, blocker, idea, potential, risk — share one shape, and they live on the page they were about.

Kavir Steel · Feed
  • Sara MohammadiTuesday, 14:02Voice note

    Site visit. Mr Rezaei said next year's budget is settled by the end of Mordad and they won't decide anything before then.

    Task created: Follow up on budget — Sara Mohammadi

    said on the drive back — filed before the office

  • Amir KazemiMonday, 09:30

    The 1403 statements arrived. Scanned, and the quality is poor.

Seven kinds, one shape

One card, one table, one thread

A kind changes exactly two things: the hue it publishes and the slots it fills. It does not move somewhere else and it does not get drawn differently.

  • Decision

    What was settled — with an accountable person and a date, on the client's or engagement's own page rather than in the memory of whoever was in the room.

  • Blocker

    What has stalled the work. Writing it down is what makes it possible to ask how many days it has been stalled.

  • Idea

    The thing someone thought of, which usually stays where it was thought of. Here it has somewhere to be.

  • Potential

    Work that might come off. One act turns it into a real engagement, and it keeps the pointer back to where it started.

  • Risk

    What might go wrong. Recording it is the only thing that later lets anyone say we knew.

  • Task and comment

    A task is the same task as always, on the same board; a comment is ordinary talk. Both are drawn with the same card.

One writer

One writing box, which becomes the thing you are writing

Every contact, company and engagement page has one writing box — not six "Add" buttons. It is a comment by default and switches with one icon to a task, decision, blocker, idea, potential or risk.

And as you write, the box itself takes on that kind's card design. So you see what you are making before you commit it.

Editing opens in that same box rather than a separate window: the card you are correcting is where it was written.

  • Comment is the default — writing one sentence should not demand a decision about type
  • The kinds come from the server, so the list grows without an app update
  • A task is a record like the six others now — one home, same board, same tick
Kavir Steel · Feed
  • Sara MohammadiTuesday, 14:02Voice note

    Site visit. Mr Rezaei said next year's budget is settled by the end of Mordad and they won't decide anything before then.

    Task created: Follow up on budget — Sara Mohammadi

    said on the drive back — filed before the office

  • Amir KazemiMonday, 09:30

    The 1403 statements arrived. Scanned, and the quality is poor.

The thread

The discussion reaches its decision in place

Every record takes replies, and a reply can carry its own kind: answer a blocker with a decision, an idea with a risk — or answer a decision with the action item it produces, which then also shows up under its own deadline.

So a discussion that arrives at a decision produces that decision without leaving the discussion, and the newest answer is the first thing a returning reader sees: it sits on top, with the original at the foot.

  • Anyone who can read a record can answer it — otherwise a thread is a monologue
  • Editing and deleting belong to the author, not to every reader
  • Threads are two levels: a reply to a reply becomes its sibling and keeps the reference
  • Deleting a record takes its thread — except a task written underneath, which survives with its own replies
Kavir Steel · Decision
Reply
  • Sara MohammadiTask
    Send the related-party schedule before ThursdayMr Rezaeiclient
  • Amir Kazemi

    Agreed — but the 41.2 B stays out until the contract arrives.

DecisionReza TavakoliSunday, 11:20

The working capital peg is set at 364.9 B T; related-party receivables excluded.

this answer is also a task — it shows up under Thursday, too

In the stream

On the page it was about, on the day it happened

A contact's, company's or engagement page shows one chronological list — notes, records and action items together, including the task a colleague assigned you about that account. A company's page rolls up its engagements' rows too. So "what happened on this account" is not a search; it is the page.

The same rows sit in the Work stream and on their own date in the agenda. And a task's owner is a person, not necessarily a login: the client's own finance lead can owe a step. On the card, the owner is a control — one tap hands it over or leaves it unassigned, and unassigned is a real, visible state.

  • Everything about the account, on the account's own page — assigned by whoever
  • An owner without a login is allowed; an owner who isn't a real, seated name is refused
  • A decision posted in the feed can name its owner in the same act
  • The filter counts count only what you are allowed to see
My work · This week

Week of 21 Tir — 3 open, 2 done

  • Send the revised QoE bridge to ParsSara
  • Return the signed engagement letterMr Rezaeiclient
  • Chase 1402 audited statementsReza
  • Validate pages 30–48 of the tax fileYou
  • Book the Alborz management callYou

the client's own CFO can owe a step — no login needed

Honestly

What it does not have yet

In progress, not a sales promise. Each one leaves this list when it ships.

  • A restricted record — a separate access level for one record is not open yet and awaits a decision
  • Threads deeper than two levels — a 320px screen has no room left to read them
  • A meeting record's actions do not yet become records or tasks; they are read

About records

  • How is this different from a plain note?
    A note is text; a record has a kind. That is what lets you ask "what blockers are open on this engagement" or "what did we decide this quarter" — a question a column of prose cannot answer.
  • Is a task a record too?
    Yes — since late Mordad, everything a person writes lives in one home: tasks, comments, decisions and the rest. That is what put a colleague's task on the page of the account it was about, which used to be exactly where the two screens disagreed. Nothing your integrations hold changed: every task keeps the id it always had.
  • Can we add our own kind?
    The list of kinds comes from the server and has already grown twice. Adding one needs no app update — but for now that is something we do, not something in your workspace settings.
  • Who can see my records?
    A record takes the access of the thing it was written on: a record on a team-private engagement is for that team. A reply takes its scope and restriction from the root of the thread rather than from wherever it sits.

Write one engagement this way for a week

The same decisions that get said on WhatsApp today, on their own page instead. See next week whether you notice the difference.