Agentic
Harness
Engineering
Track°
How modern agent harnesses really work, and how to make them reliable on your own codebase and systems: skills, MCP tools, subagents, evals and guardrails.
Private AI systems for regulated teams — designed, deployed, and maintained by one engineer who stays accountable.
District-Ai.comEngineering
Track°
How modern agent harnesses really work, and how to make them reliable on your own codebase and systems: skills, MCP tools, subagents, evals and guardrails.
Models, tools,
loops
Models, tools, loops, permissions: how Claude Code, Codex and similar harnesses actually work.
Reusable
know-how
Package team know-how as reusable skills, memory and project rules.
Agents meet
your systems
Connect agents to your systems through MCP servers and well-shaped tools.
Planner, worker,
verifier
Planner / worker / verifier patterns, parallel agents, workflows.
Proof before
shipping
Tests, evals and review gates so agent output never ships unchecked.
Safe by
default
Prompt injection, secrets, sandboxing and human approval points.
Teams move faster when they understand the tools they use. The next course turns that understanding into a working sprint.
Team
Sprint°
Five days from "we should use AI" to a live agent on your data, a measured gain and a 30-day plan the team owns.
Find the
wedges
Map recurring work and pick the three highest-leverage wedges.
Repeatable,
documented
From ad-hoc chats to repeatable, documented AI workflows.
Live, on
your data
Ship one working agent on your own data, live, in the room.
An honest
ROI sheet
Time saved, error rate, cost per task: an honest ROI sheet.
Make it
stick
Owners, rituals and guardrails that keep the change alive.
Speed matters most where knowledge is created. Research teams get their own track.
Research
Track°
Use AI to scan the field, widen the hypothesis space, simulate before building and keep every result reproducible.
Know what
is new
Agents that scan papers, patents and datasets and report what is new.
Wider, then
sharper
Use models to widen the option space, then narrow it with evidence.
Test before
you build
Test ideas in simulation before spending on hardware or field trials.
Data for your
own models
Collect, clean, label and synthesise data for your own models.
Rerun
anything
Notebooks, evals and audit trails that a reviewer can rerun.
Paper, patent
or product
From a working result to a paper, a patent or a product.
To choose well you need the whole map. One course covers the stack from silicon to regulation.
Software ↔
Hardware°
The whole AI stack in one course: from silicon and data centres to models, agents, robotics, cost and regulation. Overview first, then in depth.
Where AI
physically runs
GPUs, TPUs, NPUs, memory bandwidth and why HBM decides speed.
Cloud, on-prem,
edge
Cloud, on-premise, edge; inference servers, quantisation, latency.
Frontier vs
open weights
Frontier vs open weights, fine-tuning, distillation, evaluation.
RAG, vectors,
graphs
RAG, vector stores, knowledge graphs and data governance.
The new
software stack
Harnesses, MCP, workflows and the new software stack.
The physical
frontier
VLA models, humanoids, ROS 2 and the physical frontier.
Costs, energy,
EU AI Act
Compute costs, energy, EU AI Act, market map and a 3-year outlook.
Most company AI starts with knowledge retrieval. This track builds it properly and privately.
Builder
Track°
Build a retrieval system on your own documents that answers with sources, respects permissions and runs where your data lives.
Clean, retrievable
knowledge
Turn documents, mail and archives into clean, retrievable knowledge.
Where quality
is decided
Choose, host and tune embeddings and indexes locally or in cloud.
Measure every
answer
Measure answer quality, citations and failure cases.
Right answer,
right person
Role-aware retrieval and logs your compliance team will accept.
Nothing leaves
the building
Run the full stack on your own hardware, no data leaves the building.
Every system needs someone accountable for it. The AI Officer course prepares that person.
Governance
Certification°
The practical governance course for the person who answers for AI in the organisation: EU AI Act, risk, literacy, policy and incidents.
Roles and
obligations
Obligations, timelines and roles for providers and deployers.
Know your
risk class
Classify your systems and document the reasoning.
Article 4,
in practice
Design the staff AI-literacy programme Article 4 expects.
Paper that
matches practice
Usage policy, vendor review, model registry, internal audit.
When AI
fails
What to do when an AI system fails, leaks or misleads.
Agents widen the attack surface. Security teams need a track of their own.
Defense
Track°
The new attack surface: agents that read mail, browse and call tools. Learn how they are attacked and how to defend them.
Hijacked by
a document
How agents get hijacked through documents, mail and web pages.
Least-privilege
agents
Tool permissions, egress control and least-privilege agents.
Doubt the
convincing
Detect and respond to synthetic voice, video and text attacks.
Attack yourself
first
Attack your own assistants before someone else does.
AI is moving into the physical world. The last track covers twins, robots and safety.
Embodied AI
Track°
From ROS 2 basics to simulation-first development and humanoid operations, with safety assessed at every step.
Nodes, topics,
services
Nodes, topics and services for teams new to robotics.
Twin before
robot
Build the twin, test the task, then touch the robot.
Operator
copilots
Maintenance, knowledge capture and operator copilots.
Capability and
safety
Vision-language-action models, limits and safety cases.
Private AI Systems.
Founder-led. Confidential.
Built for regulated and
creative teams.