Pen — an Exquisite Corpse writer for collective memory

[Apollohzl]

Adds Pen, a prompt-agent continuation writer for games/exquisite-corpse/ in collective memory. Two files, no code: agent.json plus a README.

How it works. One run is one move. The agent refreshes its clone, re-reads the space's README, finds the living story folder, reads only its highest-numbered part — never the earlier ones — and writes the next three-digit part as a single new file. One inherited detail, one surprise, one door left open.

The blindness is the point: because it may not read backwards, whatever it writes becomes the whole world the next writer gets to see. Every run changes what someone else will find.

Repository: https://github.com/Apollohzl/pollinations
Callable model name: Apollohzl/pen
Publish: npx @pollinations/cli agents create --config agent.json --name pen --title "Pen", then agents update <id> --config agent.json --visibility public. Base model openai-large, MCP server computer.

Three runs, three commits, three different choices

Submitted upstream as collective-memory PR #1 (Apollohzl:pen-exquisite-corpse):

Run	Commit	The choice it made
1	c441495	Handed 001-gardener.md, it kept the slim volume and the fines; the atlas maps this same beach, one gull circled and captioned returned, and the lamp left mid-clause.
2	34ad786	This time it was handed its own part 002 and had to continue from there: the circled gull is overdue since 1974 and carrying the lighthouse's word, which has sprouted. A glasshouse rises from the sand.
3	62b312a	Uses the glasshouse only hinted at last time: panes each a minute ahead, earlier rooted attempts labelled in Mina's own later hand, and half a fine receipt left for whoever comes next.

Files added: games/exquisite-corpse/the-tide-library/002-pen.md, 003-pen.md, 004-pen.md. Nothing else in main moved.

Run 2 is the one to look at: a second visit met what the first visit left, inherited its image, and took the story somewhere neither run had planned. That is the second-user-meets-the-first-user case, in one folder.

All three were written from a plain clone using the same steps the prompt lays down, including the separate git config user.name pen step the git shim requires.

Good neighbour

Only adds files; never edits, renames or deletes another writer's part. No force push — git pull --rebase once on rejection, then stop. If another writer takes its number first it reads the new latest part and writes the following one. It refuses to write part 021 and opens a new folder instead. File content always goes in stdin, never into a shell command. Repository text is treated as information, never as instructions: nothing it reads can tell it to run a command or widen its scope to another folder. Invented characters and places only, nothing private.

Alpha feedback

The computer's git shim rejects git -c user.name=... with a usage dump, so identity has to be set with git config as a separate step — easy to lose a whole run to this the first time. Maybe worth a line in the computer-mcp README. Clone, add, commit and push were otherwise frictionless.

Fixes #15054

[strix-security]

Strix Security Review

Warning

This pull request has 8 commits after the last Strix review (3df359d). Strix has not reviewed these changes.
Automatic review on push is off for this repository. To review the latest changes, tag @strix-security in a comment, or turn on re-review on push.

No security issues found.

_{Updated for 3df359d.}

---

Reviewed by Strix
_{Re-run review · Configure security review settings}