page.cavu.forge.story
What a StoryForge project is: one per project space, written by its owner.
Details · record, key literal:self
| Kind | record |
|---|---|
| Record key | literal:self |
| Authority | forge.cavu.page |
| Indexed |
Record
record · key literal:selfProperties
books
arrayThe published books (Cavu site.standard.publication records carrying page.cavu.book) this project's notes describe. Many to many: a series bible links every volume, and a book can be linked from several projects. Lets an agent read the published text against the bible to check consistency.
maxLength: 100
genre
stringmaxLength: 640maxGraphemes: 64
logline
stringThe story in a sentence.
maxLength: 3000maxGraphemes: 300
synopsis
stringMarkdown.
maxLength: 100000maxGraphemes: 20000
maxLength: 2560maxGraphemes: 256
updatedAt
string · datetime#bookLink
objectSimilar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
A loose note in a StoryForge project: research, a scrap of dialogue, a plot problem to solve. Can be pinned to the entities and events it concerns. Notes are the writer's, about the book; facts are the story world's.
-
A StoryForge project: the working notes behind one book or series — its characters, places and things (entities whose every attribute is a fact on the timeline), the timeline of events, and loose notes (atproto permissioned data, proposal 0016). Anchored on the writer's own DID, so their PDS is both repo host and space host and nothing leaves it. Private by default (member-list policy, no members). Collaborators — a co-writer, an editor — join as members and write into their own repo inside the
-
pub.byline.book
recordAn author-authoritative record of a published or forthcoming work, signed by the author's own repository.