# Forge 4.0.7 RC.1

Matched, signed Windows setup packages for Forge Anvil, Hammer and Connect. This release candidate passed controlled acceptance; customer-environment acceptance remains separate.

## Changes

- Required operating rules and protected knowledge must be verified and resolved before engineering starts. Placeholder content and legacy records without an approval state cannot grant readiness.
- Permanent product ownership is separate from executable work. With no current assignment, the engineer explicitly waits for an assignment.
- Current authoritative restrictions participate in Working Memory with references to their original evidence. Historical-only reconciliation and revocation remove current authority without deleting history.
- Unclassified legacy promoted assertions require applicability review rather than being silently assumed historical. Administration remains available for reviewing blocked records.
- Bounded startup, refresh and lease operations remain intact. Historical evidence is retrieved explicitly. Existing native connections remain supported; Spark and managed discovery are not prerequisites.

## Upgrade and migration

Back up Anvil data before upgrading. Update Anvil first, then the matching Hammer and Connect packages. Start a new Codex chat after updating Connect.

Review unresolved operating-rule approvals, protected knowledge and legacy restriction applicability through the existing authorized Anvil workflow. Do not approve all legacy records automatically. Record a bounded current assignment where none exists. Engineering remains blocked until required authority is resolved.

This download does not install or alter any customer environment automatically. Spark is not repackaged; existing Spark downloads remain at 2.9.0.

## Verification

All three installers are Authenticode-signed and report file version 4.0.7.0. Verify the downloaded files against the accompanying SHA256SUMS.txt.

Controlled validation passed: 121 architecture/migration tests, 45 Connect tests, 8 installer tests, 126 integration checks and three fresh Hammer memory reconstructions. All 13,537 original historical fixture rows remained unchanged. The largest model-facing response was 15,047 characters against the 16,000-character limit. Interactive installer and Hammer GUI flows were not exercised in this acceptance run.