The work board

The work board is where a project’s tasks live: columns with names you choose, and cards that move between them as the work advances.

One board per project

The board belongs to the project, not to the installation nor to the workspace:

• A project can have several repositories and several host configurations; all of them share the same board.
• Switching workspace does not switch board.
• To see another project’s board, switch the project.

Items do not create workspaces. Creating, moving or deleting a card does not open, move or delete any workspace — the board organizes intention, not environment. The opposite path does not exist either: no workspace becomes a task on its own.

Where to find it

• In the projects bar, the Board entry.
• On the home, when the project is open and the view is the board view.

If no project is selected, the screen guides you to choose one — it does not invent an empty board for a project that does not exist.

Reading the board

Each column is a vertical strip with its cards. Each card summarizes, without opening anything:

• the title;
• the progress of the checklist, when it exists (how many steps completed out of how many);
• the count of attachments and of comments;
• who created it — including when it was an agent;
• when it changed for the last time.

Two reading controls are at the top:

• Search item — reduces the cards to those that match the term. A column with no result says “Nothing with that term here”, instead of looking empty.
• Filter by project — restricts what is shown to the chosen project.

When the board is not trustworthy

If the board file cannot be read safely — a future version, an invalid structure, a diverging identity — the read responds with an untrustworthy state and the reason. In that state:

• the original file is preserved;
• writes are refused, instead of writing over something that was not understood;
• the interface shows the problem.

It is the right behaviour: a board that is not understood must not become an empty, writable board, nor be overwritten by a new version that lost data.

What is stored, and where

• The board lives in the application data, not inside the project’s repository.
• No write happens in the user’s project because of the board: neither in files nor in system configurations.
• Deleting the application data folder removes the boards and the attachment copies along with it. Going back to an earlier version of the app does not modify those files — they are still there if you update again.

Limits declared in the implementation

These numbers are an implementation decision and can change between releases:

Limit	Value
Columns per board	12
Items per board	1000
Item title	300 characters
Description	100 thousand characters
Checklist entries	100 per item, of up to a thousand characters each
Comments	500 per item, of up to 10 thousand characters each
Attachments	20 per item, up to 20 MiB per file and 200 MiB per board

The refusals are explicit: the panel says the limit was reached, instead of silently truncating your text.

Scope and limits of this page

• The board is per project. Aggregating several projects requires querying each one — there is no global board, and the screen does not add different projects together as if they were one.

Next steps

• Creating, editing and moving tasks
• Board columns