# Project Map: Remote setpoint Work3 release integration

Status: completed
Type: project-map
Updated: 2026-09-08
Requested Endpoint: work3
Next Action: include this frozen candidate with every other eligible awaiting candidate when the owner starts Work5
Campaign: standalone

## Desired outcome

Retain the J-Link mailbox setpoint control as an engineering automation surface in the production
firmware image, document its production risk boundary, validate it together with the normal
touchscreen setpoint path, produce managed Debug and Release artifacts, and freeze a local Work3
candidate. Normal deployed controllers are expected to have no J-Link connected.

This extends the completed MAP-0006 Work2 outcome; it does not rewrite or merge that historical
cycle with MAP-0003.

## Production risk decision

The mailbox is inert when no debugger writes a new coherent request sequence. It validates ABI,
size, magic, command kind, finite range, sequence coherence, and request checksum, then calls the
same canonical setpoint application path used by the touchscreen. The remaining production risk
is physical/debug access: the checksum is an integrity check, not authentication, so anyone with
J-Link access can command a setpoint. Acceptance therefore depends on the stated production
condition that J-Link is not connected and debug access is controlled. This is an engineering
service, not a network or authenticated customer interface.

## Work3 gates

| Gate | Completion evidence |
| --- | --- |
| Scope | Engineering-only production retention and access boundary are documented. |
| Focused behavior | Parser, validation, acknowledgement, range, and shared-setter tests pass. |
| Integration | All applicable repository checks pass with the retained mailbox code. |
| Managed builds | Canonical managed Debug and Release rebuilds pass and hashes are recorded. |
| Freeze | Exact source, documentation, tests, and build artifacts are frozen in one local commit. |

## Completion evidence

Focused remote-setpoint automation tests passed `8/8`; all 29 applicable repository check suites
passed before and after canonical managed Debug and Release rebuilds. Debug S-record SHA-256 is
`255BB3B3230CCE6651E263CC3EAC0DAE5A71F1000568630BACA95D5866097EB8`; Release S-record
SHA-256 is `C33CDA33C79A760BFE839503C18F5CFD4C614ADF0A00F41AF92360CF90EDB024`.
The production-retention boundary and risk acceptance are recorded in
`docs/remote-setpoint-automation.md` and `docs/work3-evidence-20260908.md`.

## Transfer after Work3

Work5 will batch all eligible awaiting candidates, including this remote-setpoint candidate and
the MAP-0003 stabilization candidate, into the production release/verification cycle. Work3 does
not program a controller, push, publish a release, complete an ECO, or perform rollout.
