Engineering: issues and releases

What is asked, what is broken, what shipped, and in which release: one card per issue, as files in the repository, rendered here.

The work on this site, tracked as files in the repository (admin/engineering/), the way Issues-FS-lite does it: one markdown card per issue with front matter, three folders (open, blocked, done) whose path is the status, and one file per release naming the cards it carries. Each card says what is asked or what happens, the scenario in Gherkin, a mock-up before it is built, and the outcome and screenshots after. Every change to the site is connected to a card, and the release history names the ids. Where a card came from is in its source: the owner’s feedback through the vault pane’s lane, a screenshot, a note in chat, a brief on sgit.ai, a test.

Open (8: asked and not yet done, newest first)

Id	Kind	Priority	Title	Release	Status
018	Story	high	Guide a first-time reader through the whole loop, from the early-access key to the first note sent	v0.12.2	open
016	Story	normal	The pane about the piece: the article's graph, the marks and the cost in the pane	–	open
015	Story	low	A reply lane from the newsroom to the reader	–	open
014	Story	normal	Marks on a phrase, with kinds: interesting, great phrase, not sure, fact, evidence, question	–	open
013	Story	normal	Move a piece to a persona: the seventh decision	–	open
012	Story	high	The early-access key first, checked against the server, before a passkey or a vault is made	v0.12.2	open
011	Story	high	Screenshots in feedback: paste or pick an image, resized in the browser, sent with the note	v0.12.2	open
010	Story	urgent	Feedback without a vault: the newsroom's append lane, with a public write token and key on the page, and a typed schema	v0.12.2	open

Blocked (1: waiting on something named in the card)

Id	Kind	Priority	Title	Release	Status
017	Story	normal	The decisions at each piece on the front page	–	blocked

Done (12: with an outcome appended, and screenshots where they help)

Id	Kind	Priority	Title	Release	Status
001	Bug	high	The pane closes on every navigation	v0.12.1	done
002	Bug	normal	A stray “null” is printed under Send to the newsroom	v0.12.1	done
003	Bug	high	An account made in the lab holds no access key, and the pane offers no way out	v0.12.1	done
004	Story	high	“Done”: I have read it, I am done with it, take it off my lists	v0.12.1	done
005	Story	normal	What this browser knows about the page: reads, how far, cost, rating, the decision	v0.12.1	done
006	Story	normal	A Reading tab: every page read here, newest first, with its decision; done pages folded away	v0.12.1	done
007	Story	normal	The three steps, with the next one in bold: enable, update, send	v0.12.1	done
008	Task	high	Engineering as files: issues, releases, and the pages that render them	v0.12.1	done
009	Bug	normal	A send should update this device's file too, so other devices see the notes as sent	v0.12.1	done
019	Task	high	Import sgit.ai v0.7.79: eight articles, two decks, and the figures in every article's graph	v0.12.2	done
020	Task	normal	Import sgit.ai v0.7.81: two articles, the records ran out and sovereignty is the ability to move	v0.12.3	done
021	Task	normal	Import sgit.ai v0.7.82: one article, not a straight line	v0.12.4	done

Releases (4)

Version	Date	Kind	Cards	What it says
v0.12.4	2026-10-12	patch	1	v0.12.4: imported from sgit.ai v0.7.82, one article
v0.12.3	2026-10-12	patch	1	v0.12.3: imported from sgit.ai v0.7.81, two articles
v0.12.2	2026-10-12	patch	1	v0.12.2: imported from sgit.ai v0.7.79, eight articles and two decks
v0.12.1	2026-10-12	patch	9	v0.12.1: the first run's bugs, Done, what the pane knows, the Reading tab, the three steps, and engineering as files

For agents: issues.json is a derived index of the cards; the files under admin/engineering/issues/ are the source, and admin/engineering/README.md is the convention.

For an agent

Engineering on newsroom.sgit.ai: issues and releases as files (admin/engineering/, Issues-FS-lite layout: issues/open|blocked|done/NNN-slug.md with front matter id, title, kind, priority, created, source, release, estimated_effort; releases/vX.Y.Z.md with version, date, kind, issues). 8 open, 1 blocked, 12 done; 4 release(s). The derived index is https://newsroom.sgit.ai/engineering/issues.json; walk the files for the truth. A version row in admin/versions.html names the ids it answers.