GDP Desktop is the local execution, policy, and evidence surface for repositories you deliberately open. AI and hosted services can request bounded work, while material repository and terminal effects remain governed locally.
Use Desktop as the local control surface
GDP Desktop keeps open repository identity, Git state, incoming patch work, Auto-Terminal activity, Suggested Checks, policy profiles, rollback protection, and evidence close to the machine where material work happens.
Open repositories intentionally and target them by stable session-scoped repo_id.
Review patch intake and Patch Doctor diagnostics before treating a proposed change as safe.
Use check-run history and bounded command output to verify what actually ran.
Keep Active, AFK, Custom, or Run Everything inside the permission envelope you selected.
Follow the request-to-evidence loop
Confirm the exact open repository and current state.
Let the AI propose a patch or verification action.
GDP preflights and binds the work to the intended repository.
Local policy decides whether eligible work waits or continues.
Read fresh repository and check evidence before calling the work complete.
Keep execution authority local
The hosted gateway coordinates transport, identity, and bounded metadata; it is not the default source-code execution environment. Queueing a patch or check does not prove that Desktop applied or ran it.
Local-first describes the execution and privacy architecture. It does not establish a permanent source-license, pricing, or future commercial packaging promise.
