---
version: 0.5.0
date: 2026-06-17
headline: "Wave A of the trust-floor roadmap lands on the served path — result-side stack + TraceID (#7), dev-agent shipgate floor + CICD pillars (#11), and the in-kernel model as a RegisterEngine backend (#14) — atop hardened release/git discipline and allocation-free Q8 batched decode."
themes: ["trust-floor-wiring", "gateway-serving", "in-kernel-model", "release-discipline", "fleet-tooling", "docs"]
highlights:
  - "Served path arms the result-side trust stack and threads a TraceID end-to-end (#7)."
  - "Dev-agent shipgate floor: git-corroborated ships are allowed, unwitnessed ones held (#11)."
  - "In-kernel model wired as a RegisterEngine backend behind the engine seam (#14)."
  - "Single-writer release lock + bump gate + sweep guard make concurrent /release safe."
  - "safe_ff_sync: a refuse-or-apply fast-forward that cannot skew the shared worktree."
  - "Q8 batched decode drops per-step allocation, bit-identical; honest llama.cpp head-to-head recorded."
  - "Gateway cross-agent tier-2 productionized with scoped invalidation + revocation through `fak serve`."
---

**TL;DR** — Wave A of the trust-floor epic (#16) wires the kernel's trust primitives onto the *served* path: the result-side stack is armed end-to-end with a threaded TraceID (#7), the dev-agent ship gate now allows git-corroborated ships and holds unwitnessed ones (#11), and the in-kernel model joins the engine seam as a `RegisterEngine` backend (#14). Underneath, releases on this live multi-session cluster got safer — a single-writer release lock + bump gate + sweep guard, plus `safe_ff_sync` for the shared worktree — and the Q8 batched-decode lane dropped its per-step allocation (bit-identical) with an honest llama.cpp head-to-head on record.

## Trust-floor wiring — Wave A (#7, #11, #14)

- **Result-side stack on the served path + TraceID (#7)** — `fak serve`'s served path arms the result-side trust stack and threads a `TraceID` through the gateway/kernel boundary.
  - *Why:* the trust primitives were proven in-kernel but not yet wired where requests are actually served.
  - *How:* `internal/gateway` + `internal/kernel` (commit `5d923cb`).
- **Dev-agent shipgate floor + CICD pillars (#11)** — a real dev-agent default path: a git-corroborated ship is *Allowed*, an unwitnessed one is held.
  - *How:* `internal/shipgate` + `internal/adjudicator` (commit `04e4b23`).
- **In-kernel model as a RegisterEngine backend (#14)** — the pure-Go in-kernel forward pass is exposed through the engine registration seam.
  - *How:* `internal/modelengine` (commit `606a1a8`).
- **Wave-A claims recorded** — the wiring for #7/#11/#14 is documented against the feature-space claims ledger (commit `bbc8a33`).

## Gateway serving

- **Cross-agent tier-2 productionized** — scoped invalidation + revocation are driven through `fak serve`.
  - *How:* `internal/gateway` (commit `1825388`).

## In-kernel model — serving performance

- **Q8 batched decode: per-step allocation eliminated** — bit-identical to the prior path, lower steady-state allocation per decode step (commit `44289bb`).
- **Honest fak-vs-llama.cpp head-to-head** — batched + cross-agent shared-prefix benchmark recorded, not curated (commit `96c4c7c`).

## Release & git discipline (live multi-session cluster)

- **Single-writer release lock + bump gate + sweep guard** — concurrent `/release` sessions no longer race `VERSION`/tag; `release_bump` refuses unless the lock is held; a staged-set guard catches an `-A` sweep before commit (commit `39b202a`, `docs/production-readiness.md` item 2).
- **`safe_ff_sync`** — the git-hygiene sibling of the release lock: it performs the one fast-forward that cannot skew the shared worktree (sync only when every ff-path is byte-identical to the remote, else refuse), and never runs pull/stash/reset/clean/add. 6 hermetic tests (commit `622a93c`).

## vDSO

- **Near-dup dedup key + temporal-cache negative-result guard** — opt-in dedup key plus a guard against caching negative results in the vDSO temporal cache (commit `12303f4`).

## Docs & roadmap

- **Trust-floor dispatch packet** — one witness-gated goal prompt per issue #7–#15 under epic #16 (commit `7d3194d`).
- **Prior-art re-score** — the Part B residue re-scored against the 7 named serving-frontier systems (commit `434ea2a`).
- **Feature-space-map roadmap PLAN** — the gap roadmap for epic #16 + issues #7–#15 (commit `95a2112`).
