# Universal Body GPTHAND Release Reference Review

Status: Public documentation review complete  
Observation date: 2026-08-14  
Scope: Clean-room UX and architecture reference only

## Review boundary

This review used only the repository's public documentation and GitHub metadata.
No release binary was downloaded or executed, and no implementation detail was
copied into AiMe.

Primary sources:

- [Repository README](https://github.com/noeystyle/Universal-Body-GPTHAND-Release)
- [Thai installation and usage guide](https://github.com/noeystyle/Universal-Body-GPTHAND-Release/blob/main/docs/%E0%B8%84%E0%B8%B9%E0%B9%88%E0%B8%A1%E0%B8%B7%E0%B8%AD%E0%B8%81%E0%B8%B2%E0%B8%A3%E0%B8%95%E0%B8%B4%E0%B8%94%E0%B8%95%E0%B8%B1%E0%B9%89%E0%B8%87%E0%B9%81%E0%B8%A5%E0%B8%B0%E0%B9%83%E0%B8%8A%E0%B9%89%E0%B8%87%E0%B8%B2%E0%B8%99.md)
- [Release notes](https://github.com/noeystyle/Universal-Body-GPTHAND-Release/blob/main/RELEASE_NOTES_v0.8.0.md)
- [Security notes](https://github.com/noeystyle/Universal-Body-GPTHAND-Release/blob/main/SECURITY.md)
- [Custom binary license](https://github.com/noeystyle/Universal-Body-GPTHAND-Release/blob/main/LICENSE.md)

## Observed facts

- The documented flow uses ChatGPT as planner and a local execution layer over
  a tunnel, with filesystem and shell access constrained to a selected
  workspace.
- Setup remains a Personal/Developer workflow: the user supplies a Tunnel ID
  and API key and configures GPTHAND to use that tunnel. It is not evidence of a
  consumer pairing flow that removes per-user OpenAI Platform setup.
- The repository contains documentation rather than auditable application
  source, tests, protocol definitions, CI, an SBOM, or a reproducible build.
- The published application is described as a macOS arm64 binary with ad-hoc
  signing and no notarization.
- The release notes claim controls for destructive SQL, global package changes,
  SSRF, audit, and unclean-shutdown recovery. The repository does not provide
  source or tests with which to validate those controls.
- The license permits use and redistribution of the unmodified binary archive
  under its stated conditions; it is not an open-source license for code reuse.

## Useful independent product ideas

AiMe may independently implement these general UX patterns:

1. A visible connection state machine: Stopped, Starting, Connected, and
   Failed, with a specific next action for each state.
2. A workspace picker that warns against selecting a home directory or an
   entire drive.
3. Verification that escalates from Read, to creating a new file, to modifying
   or deleting only after the corresponding capability is enabled.
4. Explicit policy categories for destructive SQL, global package installation,
   and SSRF-sensitive network access.
5. Privacy-preserving audit plus recovery guidance after an unclean shutdown.
6. Diagnostics that distinguish account, network, workspace, and control-plane
   failures.
7. Document and media adapters as separately gated capability modules rather
   than implicit shell authority.

## AiMe decision

Universal Body is useful as a UX reference, not as an implementation or
security dependency. Its per-user Tunnel ID/API-key setup remains appropriate
only as a Personal/Developer comparison. AiMe Managed consumer mode continues
to require its own OAuth gateway, outbound authenticated device session,
locally enforced profile policy, non-exportable device identity, short-lived
route leases, and explicit revocation. No Universal Body binary, branding,
asset, credential, or source is included in this repository.

AiMe's subsequent Modify and Personal Connect work is an independently
implemented local Windows proof, not a derivative of Universal Body. It covers
create, exact structured single-file apply-patch, expected-content replace, and
bound rollback behind a native default-Deny confirmation boundary, plus a
separate four-field Personal setup dialog
that never receives the raw runtime key. Stdio rejects Modify profiles and
Managed OAuth/tool security remains globally `aime.read`, so no Managed Modify
tool is exposed. The native boundary provides best-effort ordered NTFS recovery,
not a filesystem transaction or hostile same-user compare-and-swap;
`repair_required` still needs a local operator workflow. The connection-state
and short-onboarding ideas are general UX references only; no Universal Body
code, protocol, asset, binary, or branding was used.
