Issue

Anything that blocks: given a line, an owner, and a date, and solved at the level closest to the work that can solve it.

An issue is not a complaint and not a mood. It is a named obstacle — a missing tool, an unclear decision, a broken agreement, a constraint nobody has cleared — written where the table can see it, with one person holding it and a date by which it will be answered. A blocker with no owner is a conversation that will recur every week.

It is load-bearing because it is the honest alternative to silent stalling. Work that cannot proceed either gets named or gets abandoned quietly; the second costs far more. Naming issues weekly is also what keeps Kept as a share of made meaningful: a body that clears constraints before releasing work makes promises it can keep, which is the whole logic of The look-ahead and Constraint removal.

How it is played. Raise it at The Turn, in the round or when it appears. Write one line: what is blocked, who holds it, by when. Solve it as close to the work as possible — Subsidiarity applies to problems as much as to power. If it cannot be solved at the table, it travels: to the Home Cell, and up with the sheet as a request, and where a body genuinely cannot decide, upward as a question for Guidance. Some issues are tensions between people rather than obstacles in the work; those go to Mend a Tension and, if they cannot be mended, to the elders. Close each issue where it was raised, so the table sees its own problems ending.

Also called: Issues · Issue Tracker · Identify and Solve the Issue Stands on: The Turn · Constraint · Subsidiarity Opens onto: The look-ahead · Requests and offers · Proposal · Guidance · Mend a Tension · The Escalation Ladder · Decision Making In play: table · Home Sources: The LIØNSBERG Operating System §14 (draft) · Identifying And Solving Issues (root page) · The LIØNSBERG Playbook (draft) · The DNA of Heaven, Part VII (Fable synthesis, second draft) · lionsberg.wiki: Identifying And Solving Issues Open: The root page was not opened in depth in this pass; the practice here is drawn from the Operating System. · The line between an issue, a request, and a proposal is not drawn anywhere: the field reads them as what blocks, what we ask, and what should change.