# VerseVDI Data Plane

This private-Gitea repository is the GPLv3 implementation boundary for the
separately deployed VerseVDI data plane. Phase 3C will add the pure-Go gateway
and Apollo adapter here; later phases add the Rust streaming core and native
clients. The proprietary Connection Server remains a separate process and
repository.

## Current status

The repository is prepared for **Phase 3C-A preflight and Apollo
feasibility**. It does not yet contain a production gateway or a qualified
Apollo path. A failed feasibility decision blocks Phase 3C-B; it does not
authorize direct client-to-Apollo routing, cgo, a native sidecar, or
decode/transcode behavior.

The existing Xcode project is retained for the later native-client phase. It
is not Phase 3C gateway evidence and must not be used to move provider or
Connection Server authority into a client.

## Repository boundaries

- `gateway/` owns the separately deployed pure-Go gateway and provider
  adapters.
- `core/` and `clients/` are reserved for later approved Rust/native-client
  work.
- `integration/`, `packaging/`, and `docs/` may be added only by their
  corresponding approved OpenSpec tasks.
- The repository never owns PostgreSQL, commercial licensing, durable user or
  assignment authority, or general Connection Server administration.
- The Verse client never receives or connects to an Apollo/provider endpoint.
- The Protocol repository is the sole wire-contract authority; consumers pin
  an immutable release without a filesystem `replace`.

## Verification

The baseline uses Go 1.26.5 and OpenSpec 1.5.0:

```bash
make verify
```

The command checks formatting, module integrity, compilation, vet, tests, and
strict OpenSpec validation. Verification is change-driven: rerun affected
checks after a change and the complete repository gate once after a candidate
is frozen. Do not run time-based verification loops.

## Licensing and publication

The repository currently uses the GNU GPL version 3 engineering baseline and
is private in Gitea. Public distribution, final SPDX/legal review, release
artifacts, and Corresponding Source promotion evidence require separate
authorization. See `LICENSE`, `THIRD_PARTY_NOTICES.md`, and `CONTRIBUTING.md`.