Publication Provenance

Canonical source: PUBLICATION.md · Snapshot commit: b9f2813f22e4

Publication provenance

The public GitHub repository begins with a clean snapshot of the current project rather than the full local development history.

Included

• Every current Git-tracked project document, prototype source file, screenshot, and support artifact.
• The original directory structure so repository links and evidence relationships remain intact.
• Existing status, decision, and QA language, including explicit boundaries on what has not been implemented or verified.
• A generated GitHub Wiki page for every Markdown artifact and a catalog of every non-Markdown artifact.

Intentionally excluded or sanitized

• Git internals and pre-publication commit/author metadata.
• Corporate email addresses from historical commit authorship.
• Machine-specific absolute paths, temporary clipboard paths, and local tool-run identifiers.
• Credentials, secrets, real journals, real photos, private identifiers, and provider responses. None were identified in the publication snapshot, and they remain prohibited.

The local repository retains its earlier history. Commit identifiers embedded in historical trackers and QA records are preserved as evidence labels, but commits from before the public snapshot may not exist on GitHub.

Public status boundary

Publication makes the source and planning artifacts publicly readable. It does not make the planned Life in Days archive public, and it does not imply that the application, integrations, infrastructure, privacy controls, backup, recovery, or deployment exist.