Fiction Location Ledger
Track scene locations with explicit alias chains resolved to canonical IDs, preserving original observations and rejecting ambiguous, dangling or cyclic aliases.
The problem it solves
Fiction Location Ledger Collect named fictional locations, first appearances, descriptions, and scene usage. The command runs locally, uses explicit UTF-8 JSON input, and produces deterministic JSON or Markdown reports without modifying the supplied source material.
Who Fiction Location Ledger is for
- People who need a small, purpose-built utility instead of a broad platform.
- Users working with writing, locations, worldbuilding who want the documented v1.1.0 behavior.
- People who prefer an open-source release with visible limitations, source, and license terms.
Intended result
Track scene locations with explicit alias chains resolved to canonical IDs, preserving original observations and rejecting ambiguous, dangling or cyclic aliases.
This summary is reconciled from the current catalog and repository documentation.
Features in v1.1.0
Capabilities below come from the current project README and release documentation.
Collect named fictional locations, first appearances, descriptions, and scene usage. The command runs locally, uses explicit UTF-8 JSON input, and produces deterministic JSON or Markdown reports without modifying the supplied source material.
Verified examples
Screenshots are shown only when the current README references a local source image. Otherwise, repository example files are linked directly.
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.1.0 source tag.
- Resolve explicit location alias chains to canonical IDs with original scene observations.
- Reject ambiguous alias keys, dangling targets and cycles; preserve legacy reports.
- Keep embedded Markdown fences inside report evidence blocks.
- Released the first complete Fiction Location Ledger command-line workflow.
- Added deterministic JSON and Markdown reporting, representative examples, and cross-platform tests.
Quick start
The shortest documented path into the current release.
Before running these source commands, download the v1.1.0 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.
python -m pip install .
location-ledger examples/sample.json
location-ledger examples/sample.json --format json --output report.jsonThe example documents the complete v1 input shape. Markdown is intended for immediate review; JSON preserves structured evidence for scripts and later comparison. An existing output file is never overwritten.
Current limitations
These boundaries are part of the product and prevent the page from implying unverified capability.
Locations and descriptions must be supplied explicitly. The ledger does not perform named-entity recognition or infer whether aliases identify the same place.
Privacy and licensing
Review the actual data boundary before using a tool with sensitive inputs.
Privacy and safety
All story data stays local.
Python 3.10 or newer is supported on Windows, macOS, and Linux. The package has no runtime dependencies, telemetry, account, or hosted service.
License and release
Fiction Location Ledger is published under MIT. The current cataloged release is v1.1.0, published 2026-10-15.
Related projects
Related projects are selected deterministically from shared catalog tags, category, and implementation technologies—not popularity or paid placement.
Fiction Location Ledger v1.1.0
Use the tagged release for downloads and release notes. Use the repository for source, issues, contribution guidance, security reporting, and complete documentation.
Page source: current Forge catalog plus README and CHANGELOG from the canonical GitHub release tag. Fingerprint: 5d8a72ce0eab5ba6.