Recordings

FusedFrames splits the work you do into recordings, one for each task. Nobody marks where one task ends and the next begins, as the split is worked out from the work itself. Every recording belongs to the device that made it.

A recording is something you read, not a video you watch back. It holds a short title naming the task, the steps you took in the order you took them, and any questions asked about the task with your answers.

#What recordings are used for

Recordings are what documents are written from. A document library takes the recordings that match its sources and writes them up in the format you set, so a task you do often becomes one write-up that gets better each time the task is recorded again.

They are also worth reading on their own. Recordings shared with a workspace are listed in the dashboard and laid out on the workflow map, where they can be filtered and that filter saved for a library to use. Recordings can be exported as JSON, CSV or XLSX from both the desktop app and the dashboard.

#What is captured

You turn recording on and off from the Recording card in the desktop app, the menu bar on macOS or the tray on Windows. A recording rule can do it for you instead.

While recording is on, the desktop app notes clicks, typing, deletions, keyboard shortcuts, copy and paste, selected text and drags, along with the app and window in front of you.

Passwords and other secure fields are never taken. Card numbers, keys and secrets, national ID numbers and one-time codes are removed on the device before anything leaves it, and the servers check again on arrival. Email addresses are masked rather than removed.

Most steps are text alone. A small image of the part of the screen you acted on is attached only when the text is too thin to describe what happened, and it is deleted once the step has been written.

#The timeline

The steps are numbered, each a short sentence saying what happened.

There are two kinds of step:

• What you did
• What the app did in reply

Which kind a step is cannot be changed. The second kind carries an arrow, so a screen that moved on its own is never read as your work.

Recordings are ordered too. Each one can point back to the work that came before it and on to the work that followed, so a long task broken into several recordings still reads in sequence.

#Questions

Sometimes a recording holds a choice the steps cannot explain. When that happens you are asked why. The question appears in a small window over your work, usually soon after the task it asks about. Type an answer, or hold the talk button and speak. You can close the window and answer later on the recording itself, and an answer can be changed at any time.

Questions are meant to be rare. One is asked only when a real choice was made and nothing on screen says why you made it, so that whoever reads the write-up later gets your reasoning too. No question is asked when:

• You have done the same task before in the same way.
• The task is close to one you recorded before and nothing that matters changed.
• What you typed, pasted or opened already gives the reason.
• The task was routine, so the steps speak for themselves.

#Statuses

A recording carries a question status, which says how far its questions have got:

• "Answered" - every question has an answer.
• "Partly answered" - some have answers and some do not.
• "Not answered" - questions were asked and none have answers.
• "No questions" - nothing was asked about this recording.

You never set this yourself. It moves as answers are saved, and it is what the recordings list, saved filters and libraries all match on, so the same filter always means the same thing.

In a workspace a recording carries a share status as well, "Shared" or "Not shared", for whether the workspace can read it.

#Upload and processing

Splitting work into recordings, writing the steps and asking the questions all happen in the cloud, and all of it spends AI credit.

Work recorded offline waits on the device and uploads when the connection comes back. Until then the desktop app marks it Not synced and offers to try the upload again.

Recording stops when the machine sleeps and starts again on waking if it was on. Locking the screen does not stop it, but work after the lock is not linked to work before it.

#Sending recordings to your workspace

A recording stays private to the device that made it until you send it to your workspace. The desktop app only ever shows that device's own recordings, and the dashboard only shows the ones that have been shared, so nothing you record reaches anyone else until you say so.

Share a recording from the recording itself, or several at once from the recordings table. Sharing cannot be undone, and a shared recording belongs to the workspace from then on.

#Deleting recordings

A recording and its steps go for good, and cannot be brought back. Its questions, answers and feedback go with them.

Where you delete depends on sharing. A recording you have not shared is deleted in the desktop app. A shared one belongs to the workspace and is deleted in the dashboard.

Documents already written from a recording are kept, along with any edits made to them, but the link from the document back to it is removed. Deleting a device deletes its recordings too.

There is no automatic expiry and no retention setting. A recording is kept until someone deletes it.