What "open" means in Smeldr, and where it is written

An item is open when it waits for someone to act. The flow now says so for every state, and no reader needs its own list.

Count the open items on a board and you need a rule for "open". Until now each reader had its own. One of our own tools kept a list of finished states in its own code, and the list drifted once without anything catching it.

Decision D109 settles it in one sentence: an item is open when it waits for someone to act, and everything else is closed. Two cases show why "not finished" was the wrong test.

  • A ratified Decision can still be re-evaluated or superseded later, but it waits for nothing. It is closed.
  • A parked Goal is paused, but someone still has to pick it up or close it. It is open.

The answer lives on the state, in the flow, the same way "in force" does. A state that does not declare it is closed. So is a status the flow does not name. Nothing unknown is ever shown as waiting.

Nobody keeps a copy of the table any more. Every item read now says whether it awaits action, and every list of possible next moves says which of them close the item. A board can offer its "close" buttons from that, without a hard-coded list of its own.

One detail for readers of the data: if the answer is missing from an item, it is unknown. It never means closed.

Smeldr's own flows (Decision, Task, Amendment, Goal, Signal) carry D109's table. A flow you define yourself declares its own, state by state. On an existing instance the values appear on the first start of this version, and there is nothing to run.

Released in core v1.141.0 and mcp v1.57.0.