sechmachine/VerseVDI-Data-Plane
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: adopt fixture-backed gateway gate

Browse Source
This commit is contained in:
sechmachine
2026-07-29 05:05:54 +07:00
parent 6c630a1398
commit 8379c134ca
3 changed files with 12 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+4 -2
View File
@@ -38,8 +38,10 @@ change the repository's GPL boundary.
silent capability fallback.
- Bound every parser, queue, fragment, stream, datagram, timer, goroutine,
allocation, and metric label.
- A failed Apollo feasibility spike is a terminal `NO-GO`; preserve evidence
and reopen the architecture decision rather than implementing around it.
- Deterministic Apollo fixtures and a bounded fake provider are the
implementation gate. Record live Apollo/macOS interoperability as
`deferred-owner-e2e`; never treat the deferral as permission to implement
around a later real failure.
## Source and verification rules
README.md
+6 -5
View File
@@ -8,11 +8,12 @@ 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 repository is prepared for **Phase 3C-G gateway implementation**. It does
not yet contain a gateway or Apollo adapter. Implementation uses deterministic
pinned-source fixtures and a bounded fake provider; the owner will perform
live Apollo/macOS acceptance after both candidates exist. Deferring that live
row 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
openspec/config.yaml
+2 -1
View File
@@ -19,5 +19,6 @@ rules:
- Keep transport, framing, media, source-control, and client-decode domains separate.
- Define bounds, failure behavior, authority loss, and redaction before success behavior.
tasks:
- Put the Apollo feasibility go/no-go before production gateway implementation.
- Build deterministic Apollo fixtures and the fake-provider gate before completing the adapter.
- Keep live Apollo/macOS interoperability explicitly deferred to owner E2E.
- Name focused checks, evidence invalidation inputs, and the single final verification gate.