ForgeCare v1.1.0-beta.1 — External Beta

ForgeCare v1.1.0-beta.1 — External Beta

ForgeCare v1.1.0-beta.1 is an external prerelease for Windows technicians and early beta testers.

This release advances ForgeCare from a collection of diagnostic and optimization tools into an evidence-driven technician workflow built around observation, traceability, controlled action, and factual verification.

Highlights

Evidence-driven diagnostics

ForgeCare records schema-versioned diagnostic Evidence for the active Forge Report session. System Scan, Deep Analysis, Startup Intelligence, and Process Intelligence observations can be inspected together in the Evidence Explorer.

Evidence-derived Technician Attention Items identify deterministic relationships that deserve technician review. Attention remains advisory and read-only—it does not execute changes.

Forge Plan 2.0

Forge Plan now presents two deliberately separate layers:

• Attention — evidence-derived findings that warrant technician review.
• Plan Actions — existing technician-controlled review and execution workflows.

Supporting Evidence can be opened directly from Attention Items for transparent drill-down.

Action receipts and factual verification

Startup actions create persistent receipts linking technician-approved changes to later verification.

Verification 2.0 distinguishes between:

• an action being executed successfully;
• the intended state actually being observed afterward;
• inconclusive or unavailable re-observation.

ForgeCare does not claim causality where the available measurements cannot prove it.

Professional Service Report

Reporting 2.0 produces a privacy-bounded professional HTML service report containing:

• recorded diagnostics;
• technician actions;
• action and verification traceability;
• checkpoints and unresolved items;
• compact Evidence references;
• explicit partial-data semantics.

The existing legacy report remains available.

Privacy-safe support artifacts

Debug Bundles and Beta Issue Packages project historical crash diagnostics through a bounded privacy filter before inclusion.

Raw historical crash logs are not copied into shareable support ZIPs. ForgeCare does not automatically upload reports, Evidence, logs, or support packages. Review every support artifact before sharing it.

Installer and portable editions

This beta includes:

• a per-user Windows installer;
• a self-contained portable Windows x64 ZIP.

The installer uses ForgeCare’s stable application identity and supports in-place upgrade from the accepted v1.0 installation while preserving supported application data.

Technician-controlled updates

ForgeCare includes HTTPS update discovery, secure installer download, SHA-256 verification, and an explicit technician-confirmed installer handoff.

Updates are not automatic. ForgeCare does not silently install or execute updates.

Known beta limitations

• This is a prerelease and should initially be evaluated on non-critical Windows 11 x64 systems.
• The binaries are unsigned. Windows reputation or SmartScreen warnings may appear on some machines.
• No production public update-manifest endpoint is currently configured.
• Evidence and related diagnostic state are append-oriented and may grow across repeated diagnostic runs.
• Some protected processes, inaccessible files, signatures, or system state may produce incomplete or inconclusive diagnostic results.
• Offline Authenticode validation does not provide current online revocation or reputation guarantees.
• Correlation is deterministic and rule-based; it is not malware detection or AI reasoning.
• Technician Attention remains transient and is rebuilt from persisted Evidence.
• Full live workflow behavior is not covered by end-to-end WPF automation.

Feedback and issue reporting

When reporting a beta issue:

1. Record the exact operation and visible result.
2. Export a Beta Issue Package or Debug Bundle where appropriate.
3. Review the package before sharing it.
4. Include reproducible steps, expected behavior, and actual behavior.

ForgeCare does not use telemetry and does not automatically upload diagnostic artifacts.