From 776be14a786bb09bfa6c10eaa513eb2760b3759f Mon Sep 17 00:00:00 2001
From: Piergiuseppe Mallozzi <1713584+pierg@users.noreply.github.com>
Date: Tue, 17 Nov 2026 20:39:51 +0000
Subject: [PATCH 1/3] The home map opens with Current storylines (1.14.0)
---
CHANGELOG.md | 9 +++++++
docs/model.md | 10 ++++++--
pyproject.toml | 2 +-
skills/lab-set-up/SKILL.md | 15 ++++++-----
skills/lab-work/SKILL.md | 6 ++++-
src/lab_kit/__init__.py | 2 +-
src/lab_kit/storylines.py | 51 +++++++++++++++++++++++++++++++++++++-
tests/test_storylines.py | 29 +++++++++++++++++++++-
8 files changed, 111 insertions(+), 13 deletions(-)
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 6a35049..c68e536 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,14 @@
# Changelog
+## 1.14.0
+
+- **The home map opens with Current storylines.** When `lab.toml` names its storylines, the library's home map
+ has one section `
Current storylines
` whose rows are the active storyline
+ pages and nothing else, so every lab shows its storylines in the same place. `lab check` refuses a library
+ with no such section or with two, an active storyline with no row there, and a row there that is not an
+ active storyline. lab-set-up writes the section, and lab-work keeps it when a storyline is added or retired.
+ Run `lab init` in a lab after upgrading.
+
## 1.13.0
- **A scope page is a storyline.** A storyline is one argument the lab is building from its findings, for one
diff --git a/docs/model.md b/docs/model.md
index 5a0b705..b5bb411 100644
--- a/docs/model.md
+++ b/docs/model.md
@@ -402,7 +402,8 @@ moves from included to excluded. Adding, merging or retiring a storyline is dire
you. A question's or an experiment's So far gives the current finding, not the story of the bugs on the way:
the replaced experiments and the reasons they were replaced keep that story.
-A lab opts in by naming the pages in `lab.toml` (section 9). Then `lab check` holds each scope table:
+A lab opts in by naming the pages in `lab.toml` (section 9), and its library's home map lists them under one
+section, Current storylines. Then `lab check` holds that section and each scope table:
included lists only finished work that is not void, replaced or dropped, open only work still to do, nothing
parked or dropped is in either, and a goal, a question or a step sits in one row; a storyline page committed
before a result about something it lists under included or open is noted. `lab now` lists each storyline's
@@ -962,7 +963,12 @@ a question or a step has one row on a page: where another row needs to mention i
without its link. A question written in one row and a step under it written in another is allowed: the open
question with its one finished step included is the usual case. A decision may be cited in any row. In
`lab now` and in the note on a stale page, a goal or a question written under included or open stands for
-every step under it. A lab without `[storylines]` has none of this.
+every step under it.
+
+The library's home map opens with a section headed `Current storylines
`, and
+its rows are the active storyline pages, each linked as `/content//`, and nothing else. It is the one place
+those pages have on a map; the overview and a retired storyline have theirs under other headings. The library
+has one such section, on one map. A lab without `[storylines]` has none of this.
**Worked-out states.** A goal is open until `reached: true` makes it done or `dropped:` drops it. A
question is waiting while the decision it came from is open, then open, then done with its answer; it
diff --git a/pyproject.toml b/pyproject.toml
index 513854e..c1cf7e8 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -5,7 +5,7 @@ build-backend = "hatchling.build"
[project]
dynamic = ["readme"]
name = "lab-kit-cli"
-version = "1.13.0"
+version = "1.14.0"
description = "A research lab's record, its method, and the command that keeps both."
license = "MIT"
authors = [{ name = "Piergiuseppe Mallozzi" }]
diff --git a/skills/lab-set-up/SKILL.md b/skills/lab-set-up/SKILL.md
index ce9db85..c3f84bd 100644
--- a/skills/lab-set-up/SKILL.md
+++ b/skills/lab-set-up/SKILL.md
@@ -45,12 +45,15 @@ You set the lab up in one discussion with the operator, so that everything it se
`views:`. Set it up with folio's own skill if it is not there.
12. If the lab will argue its findings to an audience (a paper, a talk, a report), ask the operator which
storylines it aims at now, for whom and where (it is direction, and may stay empty). A storyline is the
- argument such an output is written from, not the output itself. Write the overview page (for example `entries/where-the-results-stand`) with folio's
- write skill: the words on one running example, the workflow, the related work, and empty sections for the
- findings and the criticisms. For each storyline, write `entries/storyline-`: its thesis, then the scope table
- (target audience and venues, core thesis, experiments included, excluded or superseded, open), with the
- last three cells marked `data-scope="included"`, `"excluded"` and `"open"`. Name them in `lab.toml` under
- `[storylines]` (`overview`, `active`). No card names a storyline (method rule 8).
+ argument such an output is written from, not the output itself. Write the overview page (for example
+ `entries/where-the-results-stand`) with folio's write skill: the words on one running example, the
+ workflow, the related work, and empty sections for the findings and the criticisms. For each storyline,
+ write `entries/storyline-`: its thesis, then the scope table (target audience and venues, core
+ thesis, experiments included, excluded or superseded, open), with the last three cells marked
+ `data-scope="included"`, `"excluded"` and `"open"`. Name them in `lab.toml` under `[storylines]`
+ (`overview`, `active`), and open the home map with a heading `Current
+ storylines
` whose rows are the storyline pages (`folio map add