BLOCK 4 · AI GATEWAY (PRODUCTION) 4:40 – 5:00 · 20 min · 5L / 15Q · Closing

TOPIC 4.10 / 10 · CLOSING + Q&A FLOOR

Recap + Q&A

Close the altitude arc. Name two concrete moves attendees can make this week. Then open the floor — 15 minutes minimum, absolute floor.

★ Q&A FLOOR (15 min) — DO NOT BREACH

4.10.1

Recap

4 min Lecture 4:40 – 4:44

Slide 1 / 3 · What you configured today

In Block 4 you…

Set up two providers (Anthropic + OpenAI) inside one gateway
Configured models with an alias
Created a Virtual Key as your app's identity
Attached a budget — policy-layer cost control
Built a weighted routing rule with fallback
Versioned a prompt — decoupled from app deploys
Toured the enterprise-tier concerns and named why each matters
Walked semantic cache: OSS mechanism + your-choice storage layer
Wired the gateway into a Vue/Nuxt app — Vue knows nothing about providers

Slide 2 / 3 · Four altitudes

Four altitudes, one discipline

Morning: PROMPT — engineer it
Morning: SKILL — promote + benchmark it
Afternoon (Sam): WORKFLOW — compose them daily
This block: INFRASTRUCTURE — the gateway

Same discipline at every altitude. Different tools.

Slide 3 / 3 · The closing principle

Don't put concerns in the wrong place

"Vue doesn't hold API keys. Prompts don't hold deploy cycles. Skills don't hold provider state. The gateway is where the infrastructure concerns live."

Speaker notes

Slide 1 — name the wins: "In Block 4 you configured a real production AI gateway. Two providers in one gateway. Model alias for swap-without-deploy. A Virtual Key as your app's identity. A budget that enforces at the policy layer. A weighted routing rule with fallback — that 3+3 split landing in your terminal was the OSS-earning-its-keep moment. A versioned prompt in the repository. A tour of the enterprise concerns with their production importance named. We walked semantic cache as an OSS mechanism that needs your team's storage choice. And you wired the whole thing into a Vue/Nuxt app where Vue knows nothing about providers."

Slide 2 — close the altitude arc: "This morning, Martin gave you prompts and skills. After lunch, Sam gave you the developer workflow altitude. This block was infrastructure. Same discipline — constraint engineering — at every altitude. Different tools. Same principle: don't put concerns in the wrong place."

Slide 3 — the closing line: "Vue doesn't hold API keys. Prompts don't hold deploy cycles. Skills don't hold provider state. The gateway is where the infrastructure concerns live."

4.10.2

Take-home actions

1 min Lecture 4:44 – 4:45

Slide 1 / 1 · Two moves this week

Two concrete moves

Stand up a gateway in front of one production AI call. Move one provider key out of your app and into the gateway. Even one. That's the wedge.
Version one prompt in the Prompt Repository. Pick a system prompt that changes more than monthly. Make it a versioned asset.

Two moves. Five hours each, max. Compounding from there.

4.10.3

Q&A floor

15 min Q 4:45 – 5:00 ★ ABSOLUTE FLOOR — DO NOT BREACH

Slide 1 / 1 · Q&A

Questions?

15 min · the floor

Martin Rojas + Samuel Obukwelu · workshop materials at github.com/<repo-url> · feedback welcome

Speaker notes

Open the floor. "Fifteen minutes. Any question — Block 1, 2, 3, or 4. Bring your own use case if you want to apply this to something specific."

Field questions in priority order:

Tactical "how do I do X with our stack?" — most actionable, most useful to room
Strategic "should we adopt this pattern?" — invite the room into the discussion
Conceptual "why this design over that?" — give your real opinion, with the trade-off

If the room is quiet — seed a question: "Common one: how do you decide between Bifrost OSS plus app-layer guardrails versus Bifrost enterprise tier with built-in guardrails? Answer is — if you're small, OSS plus app-layer. If you're regulated, enterprise. If you're somewhere in between, run OSS until the audit pressure forces enterprise. Don't over-buy on day one."

Final 30 seconds: thank the room. Point at the workshop repo. Invite follow-up over LinkedIn / Twitter / however you prefer.