Core Quickstart
This guide gets a developer from a clean machine to a working DigiEmu Core CLI.
1. Clone Core
Section titled “1. Clone Core”git clone https://github.com/DigiEmu/core.gitSet-Location .\core2. Check Go
Section titled “2. Check Go”go version3. Run the tests
Section titled “3. Run the tests”go test ./...Do not continue with a local build if the test suite fails.
4. Build the CLI
Section titled “4. Build the CLI”go build -o digiemu.exe ./cmd/digiemuConfirm that the executable exists:
Get-Item .\digiemu.exe5. Inspect the CLI
Section titled “5. Inspect the CLI”.\digiemu.exe --help6. Verify a known bundle
Section titled “6. Verify a known bundle”The stable v1 verification interface accepts an explicit bundle path:
.\digiemu.exe verify ` --bundle "<bundle-path>" ` --jsonA verification JSON result exposes fields including:
okrefexpectedgothash_algcanonical_scopetracemessage7. Replay the same bundle
Section titled “7. Replay the same bundle”.\digiemu.exe replay ` --bundle "<bundle-path>" ` --jsonFor the same fixed bundle, replay is intended to preserve deterministic state reconstruction and deterministic trace ordering.
8. Evaluate Core 2.0 draft conformance
Section titled “8. Evaluate Core 2.0 draft conformance”This step is optional and uses experimental functionality.
go run ./cmd/digiemu ` experimental conformance run ` testdata/core_2_conformanceExpected summary:
Conformance run summary: total=11 passed=11 failed=0JSON:
go run ./cmd/digiemu ` experimental conformance run ` testdata/core_2_conformance ` --jsonWhat you have verified
Section titled “What you have verified”At this point you have:
- cloned the public Core source
- executed its test suite
- built the CLI locally
- exercised the deterministic verification interface
- exercised replay
- optionally checked the Core 2.0 draft conformance suite