Logan Pendragon ForgeProduct Lab
Forge Miniv1.2.1Feature Complete

Unresolved Mystery Ledger

Track unresolved story mysteries and compare two inclusive milestone snapshots, marking undated resolution timing as unknown.

Current release v1.2.1View source
v1.2.1Current release
MITSource license
3Supported platform groups
Writing & ReadingCatalog category

The problem it solves

Unresolved Mystery Ledger Unresolved Mystery Ledger is a local command-line tool for tracking mysteries, clues, narrative promises, resolutions, and intentionally open threads in long-form fiction. Its milestone filter can generate a spoiler-controlled report as of a chosen chapter or scene.

Who Unresolved Mystery Ledger is for

  • People who need a small, purpose-built utility instead of a broad platform.
  • Users working with fiction, mysteries, story planning who want the documented v1.2.1 behavior.
  • People who prefer an open-source release with visible limitations, source, and license terms.

Intended result

Track unresolved story mysteries and compare two inclusive milestone snapshots, marking undated resolution timing as unknown.

This summary is reconciled from the current catalog and repository documentation.

Features in v1.2.1

Capabilities below come from the current project README and release documentation.

01

Unresolved Mystery Ledger is a local command-line tool for tracking mysteries, clues, narrative promises, resolutions, and intentionally open threads in long-form fiction. Its milestone filter can generate a spoiler-controlled report as of a chosen chapter or scene.

Verified examples

Screenshots are shown only when the current README references a local source image. Otherwise, repository example files are linked directly.

examples/novel.jsonVerified example included in the current source repository.

Platforms and implementation

The public release claims only the cataloged platforms and technologies.

Supported platforms

  • Windows
  • macOS
  • Linux

Built with

  • Python

Changelog

Release notes from the canonical v1.2.1 source tag.

  • Correct released documentation labels; package behavior is unchanged.
  • Preserve the original v1.2.0 tags and artifacts. This patch supplies corrected documentation in new artifacts.
  • Include newly visible legacy undated resolutions in snapshot comparisons, explicitly marking the date as unknown and preserving single-snapshot behavior.
  • Use --compare-from "Chapter 1" --through "Chapter 2" --format json to compare two explicit inclusive milestone snapshots.
  • Add a local mystery editor, chapter timeline, clue-to-promise links and author-controlled stale-thread/orphan-clue review.
  • Added regression coverage for the audited behavior and invalid inputs.
  • Initial JSON ledger validation, milestone-aware spoiler filtering, Markdown/JSON reports, CLI output guards, examples, and automated tests.

Read the complete changelog

Quick start

The shortest documented path into the current release.

Before running these source commands, download the v1.2.1 source archive, extract it, and open a terminal in the extracted project folder containing README.md. Follow the tagged README for required runtimes and any platform-specific setup.

Requires Python 3.10 or newer.

python -m pip install .
mystery-ledger examples/novel.json
mystery-ledger examples/novel.json --through "Chapter 2" --format json

The input is versioned JSON with an ordered milestones list and mysteries. Each mystery has a unique ID, title, introduction milestone, status, and optional clue/promise records. Resolved entries require a resolution; future resolutions are hidden when --through selects an earlier milestone.

Use --output report.md to write a new report. Existing files are refused. Without --output, results go to standard output.

Current limitations

These boundaries are part of the product and prevent the page from implying unverified capability.

  • The tool validates supplied structured notes; it does not extract mysteries from prose.
  • Milestone order comes from the input list and is not inferred from chapter names.
  • A spoiler boundary hides future clues, promises, and resolutions but cannot audit spoilers inside user-written text.
  • Input JSON may contain sensitive plot details; store and share it accordingly.

Privacy and licensing

Review the actual data boundary before using a tool with sensitive inputs.

Privacy and safety

Markdown groups entries into open, resolved, and intentionally open sections. JSON preserves the same filtered structure and counts. Everything runs locally; there is no network access, telemetry, AI service, or manuscript upload.

License and release

Unresolved Mystery Ledger is published under MIT. The current cataloged release is v1.2.1, published 2026-10-16.

Release and downloadsRead the license

Related projects

Related projects are selected deterministically from shared catalog tags, category, and implementation technologies—not popularity or paid placement.

Shared focus: fiction, local-first

Fictional Death Ledger

Track fictional character life status, causes, witnesses, certainty, and spoiler boundaries by milestone.

View project information
Shared focus: fiction, local-first

Adaptation Difference Ledger

Review adaptation differences and CSV edits against an explicit baseline using a three-way comparison with the current ledger.

View project information
Shared focus: spoiler control

Did This Character Know That? Matrix

Review character knowledge across scenes, with optional explicit event order for knowledge uses and telling-character warnings.

View project information
Current public release

Unresolved Mystery Ledger v1.2.1

Use the tagged release for downloads and release notes. Use the repository for source, issues, contribution guidance, security reporting, and complete documentation.

Open releaseView source

Page source: current Forge catalog plus README and CHANGELOG from the canonical GitHub release tag. Fingerprint: c8be0bcbb58b50eb.