Forge Miniv1.0.0Feature Complete

Unresolved Mystery Ledger

Track mysteries, clues, promises, resolutions, and intentionally open threads with spoiler-controlled milestone reports.

Current release v1.0.0 View source

v1.0.0Current release

MITSource license

3Supported platform groups

Writing & ReadingCatalog category

The problem it solves

Unresolved Mystery Ledger [](https://github.com/loganpendragonmultiverse/unresolved-mystery-ledger/actions/workflows/ci.yml)

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.0.0 behavior.
People who prefer an open-source release with visible limitations, source, and license terms.

Intended result

Track mysteries, clues, promises, resolutions, and intentionally open threads with spoiler-controlled milestone reports.

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

Features in v1.0.0

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

[](https://github.com/loganpendragonmultiverse/unresolved-mystery-ledger/actions/workflows/ci.yml)

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

Quick start

The shortest documented path into the current release.

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.0.0, published 2026-07-26.

Release and downloads Read the license

Related projects

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

Current public release