Files
Ebitor/docs/PROVENANCE.md
T

2.4 KiB
Raw Blame History

Source provenance

Upstream snapshot

The first Git commit is the regular-file contents of the original release archive, with its single enclosing package directory removed and executable modes retained. It is an archive snapshot, not a reconstruction of upstream Git history. The following integration commit records the VCC Plus adaptations separately. The original README is preserved byte-for-byte in UPSTREAM_README.md.

The author’s project index linked the matching archive during provenance review. No historical HTTP receipt establishes the date of the original download; the SHA-256 identifies the observed archive bytes, not authenticity or a license grant.

VCC Plus integration

  • The original C/header sources and Makefile are byte-identical to the archive.
  • VCCPlus.mk includes the original Makefile and adds target vccplus-disk to package ebitdemo.bin into Ebitor.DSK.
  • vccplus-project.json selects that disk target and launches the demo with LOADM"EBITDEMO":EXEC.
  • Public documentation, build-output exclusions and actual guest screenshots accompany the verified disk. Source notices and authored runtime data remain intact. Generated intermediate build files are excluded from Git.

License scope

The upstream README and source explicitly grant GPL-3.0-or-later permissions. The archive omits the COPYING file referenced by its README. This integration adds unmodified GPLv3 license text from VCC Plus’s COPYING, accompanying the existing notices without changing their “or later” permission.

The upstream version history says “2027-07-27” for version 0.1.0, while the author’s project index observed during provenance review identifies version 0.1.1 in 2025. The original README is preserved without correcting that inconsistent historical date; the archive version and hash identify this import.

Verification

The Release disk build and guest execution were verified through the public MCP interface of installed VCC Plus 3.5.0 build 43. The checked-in disk and screenshots are identified in VALIDATION.md, including the limits of that check.