Repository navigation
Releases
FieldRook v0.6.0-rc.1 (pre-release)
FieldRook v0.6.0-rc.1 — Release Notes (pre-release)
Status: pre-release, development build. Not stable. This release includes the functional M028/M029 Field Kit, which is NOT in the v0.5.0 binaries.
What is new since v0.5.0
- Field Kit dock — modular right-hand instrument framework (pins, keyboard access, narrow-overlay support).
- Evidence Lens — deterministic before/after record compare over persisted evidence, contradiction citations, export linkage.
- Network Lab — read-only networking instrument (adapters, addresses, DNS config, resolution test) with consented re-checks and a remote-target guard.
- Network Lab success-notice fix — the re-check confirmation survives lab updates (no remount clearing).
- Reproducible demo scenario — "The FieldRook demo worker is down", documented step-by-step in
docs/demo/M028_THREE_MINUTE_DEMO.md.
Remaining Field Kit modules (Process Watch, Event Decoder, Command Deck, Field Notes) are still design-prototype concepts, not shipped features.
Provider and demo honesty
- Runtime model in the packaged demo is the deterministic simulated provider (
fieldrook-simulated-001), badged SIMULATED MODEL / FIXTURES ONLY in-app. - Meta provider runtime is NOT verified in this build (no API key at build/test time). Do not claim live hosted inference from this package. See
docs/demo/M029_META_PROOF_STATUS.md. - Demo readings are local fixtures; no live-cloud or operator data is bundled or contacted.
Requirements and limitations
- Windows 10/11 x64. WebView2 Runtime required (evergreen; the shell shows install guidance when missing). No .NET runtime needed (self-contained shell); no Python/Node on the target.
- Binaries are unsigned — expect a possible Windows SmartScreen warning. Verify SHA-256 checksums before running.
- Localhost-only server bind; per-user data under
%LOCALAPPDATA%\FieldRook; single-instance guard. - Not certified: second-machine trials, antivirus-vendor reputation, no-WebView2 machines, upgrade-over-existing installs. See README "Validation and known limits".
Package contents
FieldRook-0.6.0-rc.1/— portable app dir: runFieldRook.exe, keep the folder together.FieldRook-0.6.0-rc.1.zip— shippable archive (verify hash, then unzip).SHA256SUMS.txt— hashes of the archive and executables.BOM.txt— build provenance: exact source commit, toolchain pins, artifact hashes.
Distribute the entire directory together, not only FieldRook.exe. Do not commit the binary ZIP into the source repository.
Verification (build-time gates)
- Backend pytest, frontend tsc + Vite build, .NET suite, full Playwright E2E, frozen
--versionidentity check, headless lifecycle smoke, and the packaged fixture scenario all pass on the release-commit build. Exact numbers: backend pytest 715 passed / 4 skipped, .NET suite 66/66, Playwright E2E 98/98; artifact hashes are in the attached BOM and SHA256SUMS.
FieldRook v0.5.0 (pre-release)
FieldRook v0.5.0 — native Windows desktop (pre-release)
Pre-release. Binaries are unsigned and built from one validated machine;
second-PC field trials, AV-vendor acceptance, and upgrades are not yet validated.
Please verify checksums after download.
FieldRook 0.5.0 runs as a native Windows app: a WPF + WebView2 window (FieldRook.exe)
manages a packaged Python/FastAPI backend locally. No Python, Node, or admin rights needed
on the target. Localhost only.
What's new
- Native shell: windowed app with single-instance guard, native file dialogs,
drag-and-drop evidence import, controlled shutdown, first-run provider/consent tour. - SIGNALFORGE UI: redesigned Launchpad / Workbench / Evidence / Knowledge / Settings
with Alive / Quiet / Off motion profiles and reduced-motion support. - Evidence-driven investigations intact: case history, Collector import with consent,
hypotheses, technician observations, export, target-isolation protections. - Portable Collector (separate ZIP below): authorized read-only diagnostics into a
versioned, hash-verified package for validated import. - Windows liveness fix: process-existence checks no longer signal the console
(previouslyos.kill(pid, 0)could SIGINT the shared console).
Downloads
FieldRook-0.5.0.zip— portable app directory (unzip, runFieldRook.exe).
Distribute the whole directory, not just the exe.FieldRook-Collector-0.5.0.zip— portable collector directory (xcopy/USB friendly,
runs from its own folder, no install).SHA256SUMS-v0.5.0.txt— hashes of both ZIPs plus the executables inside them.FieldRook-0.5.0-BOM.txt,FieldRook-Collector-0.5.0-BUILD-BOM.txt— build provenance
(source commit, toolchain pins, artifact hashes, signing statement).
SHA-256
204fa2f44a9b1a9aff6ed648408c2c44fe081da3988dc9016ab2e1b17df21fc2 FieldRook-0.5.0.zip
c42c0ffb81d47a6a5cd9c368d5cb6f2b85cb12461b5bca12ebadfbd58bc44bc1 FieldRook-Collector-0.5.0.zip
Verify after download (PowerShell): compare (Get-FileHash .\FieldRook-0.5.0.zip).Hash
against the line above, or check every line of SHA256SUMS-v0.5.0.txt.
Requirements
- 64-bit Windows with the WebView2 Runtime (evergreen). If it is missing, the app
shows install guidance instead of starting. No .NET install needed (self-contained). - No Python/Node, no admin, no services, no registry. Data lives in
%LOCALAPPDATA%\FieldRook(delete the install dir + that folder to remove).
Known limitations (honest)
- Binaries are unsigned (hash-verified, not code-signed): expect a SmartScreen prompt
on first run from a download. AV-vendor acceptance has not been validated. - Collector packages are hash-verified, not cryptographically signed.
- Second-PC field trials, upgrades, some elevated Collector categories, and varied
hardware remain unvalidated. Local AI speed is hardware-dependent. - Field Kit Expansion is an interactive design prototype, not six functional
tool modules in v0.5.0. - The demo video shows the production React UI in Chromium, not a native-window
recording; native screenshots ship alongside it.
Validation behind this pre-release
Source dfae87e (tag v0.5.0); CI backend + frontend green on that SHA.
Backend 687 passed / E2E 47/47 / .NET 66/66 / gauntlet 38/38, plus frozen smoke
(lifecycle, refusal paths, collector import with provenance, persistence, export).
Native-window open/close on these exact binaries was not re-executed on the build
machine because the operator's instance holds the single-instance lock; the shipped
shell/UI code is byte-identical to the window-tested build.