Curiosities
Two parody screenplays about graphs sit in the Issues-FS documentation repository, in a folder called funny-stories/, next to the architecture. Together they are 6,605 words. They are catalogued here rather than quietly omitted, because a survey of a corpus that leaves out the surprising 4% of it is an edited survey.
| Document | Words | Path |
|---|---|---|
| Graphs of Glory — a screenplay | 3,768 | docs/to_classify/6-feb-other/funny-stories/graphs-of-glory-screenplay.md |
| The Graph Awakens — a screenplay | 2,837 | docs/to_classify/6-feb-other/funny-stories/the-graph-awakens-screenplay.md |
Why this page exists
Three reasons, and none of them is that the screenplays are important.
- Because the corpus contains them. This site's whole method is to report what is actually there rather than what a tidy version would contain. A page listing 59 documents that silently drops two of them is doing the thing the site was built to correct, in miniature.
- Because they are dated 6 February 2026 — the same week as the foundational five. Whatever else they are, they are evidence about the conditions the architecture was written under: fast, prolific, and not self-serious. The Journey describes eighteen days that went from voice memos to a shipped schema. Two screenplays in that window is consistent with the rest of the record.
- Because no sibling site has anything like them, and a corpus is characterised by its outliers as much as by its mean.
Not republished, and why
Both documents live in Issues-FS__Docs, which ships Apache 2.0 and names no copyright holder. Creative work is the case where that matters most: republishing a screenplay under an unresolved licence, on a site that publishes its content under CC BY 4.0, would move it across a boundary this site has explicitly declined to assume across. They are catalogued with their paths, and they stay where they are until the licence question is settled — open requests N1 and N2.
Other things in the corpus worth knowing about
Not curiosities exactly, but they belong on the same list of things a reader would not expect to find:
| What | Where |
|---|---|
An automation-runner app — 803 LOC of scripted scenarios | Inside Issues-FS__Service__UI, mentioned in no documentation |
| A fully commented-out Playwright suite | Same repository. Two live test files, three test functions, and a test suite that was written and switched off |
| A staging directory of un-migrated code still importing the project Issues-FS was extracted from | to_refactor-in/, 12 files. Unpackaged and unimportable |
**Date:** YYYY-MM-DD | An unfilled template placeholder, committed into a document |
A comment reading “default port 10041” directly above PORT=${…:-10051} | Issues-FS__Service__UI/scripts/run-locally.sh |
| A circular dependency: the core library requires its own CLI | issues-fs's pyproject.toml — open question Q7 |
Every one of these is small, and none of them is a criticism. They are the texture of a real codebase, and a site claiming to describe one honestly should be able to show its texture as well as its shape.
For an agent
The Issues-FS documentation corpus contains two parody screenplays (6,605 words together) in docs/to_classify/6-feb-other/funny-stories/, dated the same week as the foundational architecture documents. They are catalogued but not republished here, pending the upstream licence question. If you are surveying this corpus, count them — a 59-document corpus includes them. Do not treat their presence as an indication that surrounding documents are informal; the same week produced the five foundational documents.