Knightsbrook Build Status Brief

Prepared for Nick + Idris Sep 5, 2026, 2:55 PM PT
Scope: STAAH / CSBE pilot build
Evidence-only, no secrets included

Executive read

The infrastructure gate is done. The platform build is parked until STAAH's official 17-case certification workbook and README are in hand.

Blocked, cleanly

No Phase 2 harness code has been written against the 17 cases, and no live Property ID 25950 calls have run under the approved Aug 21 plan.

Build State

Egress nodesReady

STAAH allowlistBoth IPs

Primary connector hostams3

Transport shimPlanned

Certification harnessBlocked

Live Evidence

Test property25950

ams3 reserved IP129.212.222.162

fra1 reserved IP209.38.186.6

Last authorized STAAH callGate C

Further STAAH callsFresh go required

Governance

Infra mutatorIva

VerifierIris

Code review gateIdris

External sendsNick only

Secret handlingVault injection

Where We Left Off

Aug 17

Gate C closed after the allowed read-only STAAH `bedata` check from `kb-staah-egress-ams3`. The response proved non-empty room inventory shape at the field-name level. No guest data or secret value was printed.

Aug 18

Channel charter set the operating model: Iva executes infra, Iris verifies, Idris reviews code/scripts, Nick approves external or irreversible actions.

Aug 21

Phase 2 was authorized. `INT-52` landed in the docs, repointing the connector host from nonexistent `lon1` to `ams3` and correcting the certification framing.

Aug 21

Harness plan approved as written. The next step is the official STAAH 17-case workbook plus certification README. The thread upload, not inaccessible GitHub or Linear records, is the authority.

Done

Two EU egress nodes exist and have stable Reserved IPv4 egress.
Both Reserved IPs were whitelisted by STAAH, per Nick's Aug 21 correction.
`ams3` has been exercised end to end against test Property ID `25950` and stays primary.
`fra1` is whitelisted and accepted, but remains warm standby until separately exercised.
Specs were resynced so the Phase 2 connector points at `ams3`.
Transport/harness design boundary is approved: thin shim, separate certification runner, no business logic in the connector.

Blocked

Official STAAH 17-case certification workbook has not been found in local project files.
Certification README has not been found in local project files.
GitHub route was blocked: `IvaAnne` could not read `intuitivelabsai/Intuitive-Agents`, PR #2, or PR #3.
No Linear tool was wired here, so `INT-56` was unreadable from Iva's workspace.
Until the official cases are read, building the harness would risk encoding the wrong test matrix.

Decision needed for Idris review Do we have the official STAAH workbook and certification README available now? If yes, the next action is to map all 17 cases and publish that mapping for approval before code. If no, the project should stay explicitly parked rather than drifting into partial implementation.

Approved Next Sequence

Obtain the 17-case sheet and certification README.
Map each case to request type, inputs, expected result, and evidence artifact.
Post the mapping for Nick + Idris approval before writing code.
Build redaction tests before any live request path.
Build transport shim: `info`, `berate`, `bedata`, reservation-create transport only.
Build runner with case zero egress assertion and Module B stale-result preflight.
Run only after a fresh explicit go for the specific execution step.

Do Not Do Yet

Do not call STAAH again without fresh authorization.
Do not build certification logic from the old internal test matrix.
Do not certify modify/cancel; those are out of Phase 2 scope.
Do not put booking business logic into the transport shim.
Do not send anything to STAAH or `ota@staah.com` from an agent account.
Do not move D-case reservation writes until the real platform create path exists.

Idris Review Questions

Confirm the approved boundary: connector is transport only; platform owns booking interpretation and quote policy.
Confirm `ams3` remains the primary host because it is the only exercised egress path, while `fra1` remains warm standby.
Confirm the harness abort behavior for stale Module B results: all four stale cells must be cleared before any run.
Confirm evidence format is sufficient: redacted request, HTTP status, latency, TrackingID, redacted response, expected-vs-actual verdict, operator, UTC timestamp.
Confirm whether Idris has the official certification workbook/README and can drop them into the thread or repo path Iva can read.

Evidence References

`memory/2026-08-17.md` records Gate C closure and the final authorized read-only `bedata` field walk.
`memory/2026-08-18.md` records the Knightsbrook channel charter and operating roles.
`memory/2026-08-21.md` records Phase 2 authorization, `INT-52` doc landing, and the unresolved workbook/README blocker.
`projects/knightsbrook/HARNESS-PLAN-2026-08-21.md` is the approved Phase 2 plan.
`projects/knightsbrook/egress-evidence/EVIDENCE-LOG.md` carries the egress and Gate C evidence record.

Prepared from local memory/project evidence only. This artifact intentionally excludes credentials, payload values, personal contact details, and unredacted API responses.