🔒All inputs are processed locally in your browser. Nothing is transmitted, stored, or logged. Inputs disappear when you close the tab.

OCG-Industries Showcase · Cluster ③ Narrative and Story

Branching Fiction Lineage

Multi-author fiction forks, and then people argue about what counts as canon. This tool turns one passage into a descriptor that stamps the passage or passages it was written from, using W3C PROV-DM vocabulary. Anyone holding the same passage text and the same parents derives the same descriptor, so a canon claim can be checked instead of argued.

Data: W3C PROV-DM 2013 vocabulary · no external data

Inputs STEP 1
Self-asserted. This page does not verify identity.
Leave blank if this is the root passage.
Fill this in only when the passage merges two branches.
Node Role
--
Root, continuation, or merge, from the parent count entered
Passage Key
--
Fingerprint of title + author + text key + parent join
Derived From
--
PROV-DM wasDerivedFrom string
Detail
Passage title--
Author handle--
Character count--
Text key--
Parent count--
Passage key--
prov:entity--
prov:wasAttributedTo--
prov:wasDerivedFrom--
execution_hash: --
Author identity is self-asserted. Nothing here signs or verifies who wrote a passage. This is hash-verifiable lineage over text and parents, not an authorship proof. It also stores no passage text beyond the browser tab. Try adding a second parent descriptor above: the role and the descriptor both change.
Policy Mandate Record v2.0 · what is this?