Software, data, and publication status#

Availability is part of scientific honesty. A public interface, a private source tree, a package build, and a scholarly publication are different objects.

Current distribution posture#

Surface

Status and boundary

Web application

A public preview exists; the deployed revision must be checked independently of branch source

Scientific manual

Built with the web application under /manual/

Python package

Repository package lunartrace, version 0.1.0, Python 3.11+

Source repository

Private KritP/lunartrace; authorized access required

PyPI

Public lunartrace 0.1.0 release: https://pypi.org/project/lunartrace/0.1.0/

Hosted Python compiler

Not provided by the Worker preview

Methods paper / DOI / arXiv

No scholarly publication is claimed

Public software license

BSD-3-Clause; this does not imply scholarly endorsement

The software release is available from PyPI. A methods manuscript or scholarly publication may be considered later; the current product must not display a fake citation, DOI, paper download, or unavailable installation instruction.

Install the public Python release with:

python -m pip install lunartrace==0.1.0

Data custody#

The historical Study retains its own fixed source basis and two reference browse assets. New Lab discovery retains bounded metadata responses and source locators. Remote browse pixels are not automatically included in a Lab export.

NASA/PDS/LROC and other upstream data sources have their own attribution and distribution requirements. A publicly accessible source is not, by itself, an unlimited redistribution or endorsement grant.

Citing work during development#

For an internal or externally shared development result, record the exact software commit, artifact identity, source/query scope, capture time, and proof ceiling. Do not label a mutable preview URL as a permanent scholarly archive.

The software citation is maintained in CITATION.cff. No DOI or scholarly-paper citation is supplied here.

Requesting reproducibility#

A reader should be able to determine whether the necessary source, data, and execution environment are actually available. Where private repository access prevents independent execution, say so. The public Python package can be installed from PyPI; the manual’s examples explain the current mechanisms without implying that a software release is a scholarly publication or that historical scientific evidence is complete.