Skip to main content

FTNT💥

Six command-line tools for FTN message bases, JSON fixtures and text pipes. Python 3.12+. MIT licensed.

Status: implemented locally, not released. Development uses five sibling Python repositories. Opus writing requires the local golded-ftn-msg 1.3.0 extension; a public installation must wait for that dependency release.

uv sync --locked
uv run ftnt create ./fixtures/general --format jam
uv run ftnt write ./fixtures/general --format jam < examples/message.json
uv run ftnt export ./fixtures/general --format jam |
  jq -c 'select(.message.subject | contains("fixture"))'

create, write, read and export use an explicit --format: msg (FTSC), opus, jam, squish or hudson. Hudson write/read requires --board 1..200. Bases must be offline: close GoldED and other users first. The format packages own validation, encoding, locks and rollback.

write accepts one JSON object or a JSONL batch with --jsonl. Structural validation finishes before opening a writer. Each append commits separately; a later failure keeps earlier appends. A broken pipe can hide the receipt of an already committed message. Rerunning may create duplicates.

read --body emits the reader's body_text exactly, including any controls present there, without adding a newline. read --revision adds the writer's identity and revision. export --archive reports reader issues as JSONL on stderr and exits 7 if any occur. Export is not a byte-identical backup.

uv run ftnt decode --charset IBMPC < old-text.txt
uv run ftnt repair --json < utf8-text.txt

Both filters read the whole input into memory. Decode uses the core charset aliases, strict decoding and preserves line endings and trailing nulls. Repair uses the core heuristic explicitly; import/export never repair text.

The public manual is the front page and one page per command: create, write, read, export, decode, repair, heads and catalog. Examples are in examples/. Maintainer notes stay in docs/. The pages share DESIGN.md.

Checks:

uv run pytest -q
uv run ruff check .
uv run ruff format --check .
uv run mypy
uv build
uv run twine check dist/*
uv run python scripts/verify_distribution.py
uv run scripts/build_reading_pages.py

Distribution checks build dependency wheels from sibling checkouts and run both CLI wheels in fresh environments outside the checkout. They do not establish public-index dependency resolution. The sdist strips checkout-only uv sources. The CI matrix targets Linux and macOS with Python 3.12 and 3.14. Windows is unsupported for now. GoldED Opus runtime interoperability remains unverified. There is no configured remote, published CLI package or Pages deployment.

Metadata

Release files for golded-ftn-tools 1.0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for golded-ftn-tools 1.0.1
File Size Uploaded
golded_ftn_tools-1.0.1.tar.gz 42.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for golded-ftn-tools 1.0.1
File Interpreter ABI Platform
golded_ftn_tools-1.0.1-py3-none-any.whl Python 3 none any Details

Total release size: 57.8 kB

Release files / golded_ftn_tools-1.0.1.tar.gz

Download URL golded_ftn_tools-1.0.1.tar.gz
Size 42.3 kB
Tags Source
SHA-256 checksum
How to use checksums
abb8c8d02da9fd8848c2c993a4e42a016eb479830c5535f42bbbcd3a0cf444f8
BLAKE2b-256 checksum
How to use checksums
436bde6ed57d2340baae1da02186d9ceff0d5a5c9235e4ced3bd38d743d34301
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 7, 2026.

Transparency log

Release files / golded_ftn_tools-1.0.1-py3-none-any.whl

Download URL golded_ftn_tools-1.0.1-py3-none-any.whl
Size 15.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2a2ba9bffac6d37936b761f530d7e91665f876cba1ba675fde1a0d63c92508fc
BLAKE2b-256 checksum
How to use checksums
47a52aa963fdb11114d7a1540bf67d8cef83bdc04aa16f82dd8ba7f3c9cb36d9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 7, 2026.

Transparency log

Release history Release notifications | RSS feed

1.0.2

2 release files

This release

1.0.1 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page