Code Nexus
CurriculumHow we teachPricingBlogAboutContact
Start learning
  1. Curriculum
  2. /
  3. Season 6
  4. /
  5. Episode 1

Season 6: Build Code Nexus Assist · Episode 1 of 8

Code Nexus Assist Gets a Real Brief

You play: Junior AI Developer

Included with Core programme and Certification prep
See plans

The situation

Leo has finally written a brief with numbers in it. Code Nexus Assist v1 is a creator-support assistant: it answers account, verification and payout questions for creators. The limits are explicit — answers within 3 seconds at the 95th percentile, nine in ten answers grounded in a real support document, only support staff able to call it, creator data staying in Europe, and a budget of R12,000 a month. Today's deployment meets almost none of that: it sits in a US region, everyone reaches it with one shared key, and its quota is a fraction of launch traffic.

What you'll learn

  • AI-103 planning and generation: choosing services and regions against a brief, deployments and quotas, project connections, managed identity instead of shared keys, bounded retries, and turning requirements into measurable acceptance criteria.
  • Choosing between LLMs, small models, multimodal models and Foundry Tools; the Standard, Global Standard, Data Zone and Provisioned deployment types; Foundry projects in CI/CD; keyless Entra authentication and managed identities; private endpoints; and quota and rate-limit handling.

Who you work with

  • Maya Chen

    Senior AI Engineer · Your mentor

  • Priya Naidoo

    Cloud Architect

  • Leo Martins

    Product Manager

Scenes

  1. 1.A brief with numbers in it
  2. 2.Brief against inventory
  3. 3.Which Foundry service?
  4. 4.A client that behaves under failure
  5. 5.The identity that got left behind
  6. 6.Strategy and acceptance criteria
  7. 7.Planning check

What you leave with

Code Nexus Assist has a brief it can be held to. The inventory showed four visible gaps — region, credential, quota, connection — and one unmeasured line. The client authenticates as a managed identity, reaches the index through a project connection, and retries only transient failures, with a ceiling. The 403 after the resource move was a role pointing at the wrong scope, repaired with the smallest role at the smallest scope and proved with both an allowed and a denied read. The recommendation put westeu, requested quota with a fallback, and four measurable criteria in front of the board.

Previous episode

The Fairness Review

Next episode

The Assistant Invented a Refund

Code Nexus

Practice first. Improvise less later.

We post practical tech tips and the odd 8-BIT opinion. Mostly the tips.

The CPD Group Approved Provider #791172

Learn

  • Curriculum
  • Pricing
  • Create account
  • Sign in

Support

  • Blog
  • Certification guides
  • About Code Nexus
  • How we teach
  • Human help

Legal

  • Terms and Conditions
  • Privacy Policy
  • Cookie Policy
  • Refund and Cancellation
  • Contact: contact@codenexus.co.za

© 2026 Code Nexus. All rights reserved.

Payments secured by Payfast · Billed in ZAR · South Africa