LearnTeachMaster.org Presents Sponsored by LearnTeachMaster.org — $500 Prize The AgentCore Conversion Challenge

LearnTeachMaster.org Presents:

The AgentCore Conversion Challenge

Sponsored by LearnTeachMaster.org — $500 Prize

:::writing{variant=“standard” id=“48372”}

The AgentCore Conversion Challenge

Sponsored by LearnTeachMaster.org

Prize:

$500 USD — Paid Immediately

The first engineer to submit a Pull Request (PR) that is:

• Accepted by the original repository owner

• Properly reviewed

• Merged into the repository

• Uses Amazon Bedrock AgentCore meaningfully

• Preserves or improves the current architecture

…will receive $500 USD immediately from LearnTeachMaster.org.

No gimmicks. No vague judging.

A real merged PR wins.

The Repository

We are using the following open-source multi-agent system as the foundation:

MultiAgentSupplyChainSystem

GitHub Repository:

MultiAgentSupplyChainSystem GitHub Repository

Created by:

Shabbeer Syed

This project is already a strong example of a modern enterprise AI workflow system involving:

• Multi-agent orchestration

• Vision/image processing

• Inventory reasoning

• Supplier matching

• Logistics workflows

• MCP integrations

• Governance concepts

• Observability

• FastAPI services

• AI-assisted workflows

This is NOT a toy project.

It already demonstrates many of the patterns enterprises are beginning to adopt.

Why We’re Converting It to AgentCore

The current system works.

But the next evolution of enterprise AI is not:

“more prompts”

The next evolution is:

governed runtime systems

That means:

• Controlled reasoning

• Tool governance

• Policy enforcement

• Typed outputs

• Runtime observability

• Validation layers

• Enterprise-safe orchestration

• Hallucination reduction

• Auditability

• Operational safety

This is where Amazon Bedrock AgentCore becomes important.

AgentCore gives us a stronger production runtime for enterprise-grade multi-agent systems.

The Goal

Convert the existing architecture into a governed AgentCore-based runtime while preserving the existing business workflow.

The architecture should evolve toward:

Intent

→ Orchestration

→ Specialized Agents

→ Validation

→ Governance

→ Runtime Observability

→ Enterprise-Safe Actions

What We Want to See

Strong PRs Will Include:

1. AgentCore Runtime Integration

Use AgentCore as the runtime/orchestration foundation.

2. Structured Multi-Agent Design

Examples:

• Orchestrator Agent

• Vision Agent

• Supplier Agent

• Logistics Agent

• Validation/Risk Agent

• Synthesis Agent

3. Typed Contracts

Agents should return structured outputs instead of uncontrolled text blobs.

Examples:

• Pydantic models

• Typed schemas

• Confidence scoring

• Validation outputs

4. Governance

We want to see:

• Guardrails

• Validation

• Confidence thresholds

• Tool restrictions

• Retry handling

• Safe failure behavior

5. Observability

Real enterprise systems require:

• Tracing

• Logging

• Workflow IDs

• Runtime visibility

• Failure analysis

6. Reasoning With Constraints

We are NOT looking for “agent swarms.”

We are looking for:

• disciplined orchestration

• bounded reasoning

• predictable behavior

• operational safety

Suggested Architecture

The target direction is something like:

Upload Image

    ↓

Orchestrator Agent

    ↓

Vision Inventory Agent

    ↓

Supplier Match Agent

    ↓

Logistics Agent

    ↓

Validation / Risk Agent

    ↓

Final Synthesized Output

With:

• AgentCore runtime

• Tool governance

• Typed outputs

• Observability

• Validation gates

• Enterprise-safe execution

The Bigger Goal

This is NOT just about one repository.

This is the foundation for many future LearnTeachMaster.org projects involving:

• Intent-Driven Engineering

• Multi-agent orchestration

• Enterprise AI systems

• Runtime governance

• AI observability

• Shared services

• Platform engineering

• Agentic workflows

This challenge is intentionally designed to reward engineers who understand:

AI does not reduce the need for engineering.

It increases the importance of good engineering.

Recommended Playlist / Workflow

Step 1 — Fork the Repository

Fork the GitHub repository.

Step 2 — Understand the Existing Architecture

Read the README carefully.

Understand:

• current orchestration

• services

• workflows

• integrations

• governance ideas

Step 3 — Learn AgentCore

Study:

• AgentCore runtime

• Gateway tools

• policies

• observability

• orchestration patterns

Step 4 — Design Before Coding

Think architecturally first.

Do NOT just wire AI calls together.

Focus on:

• governance

• validation

• runtime safety

• orchestration

• observability

• typed outputs

Step 5 — Build a Clean PR

We value:

• clarity

• architecture

• safety

• maintainability

• runtime reasoning

• operational maturity

Over hype.

Step 6 — Submit the PR

Submit the PR to the original repository owner.

The PR must be:

• accepted

• reviewed

• merged

to qualify.

Contacting the Original Owner

Repository owner:

Shabbeer Syed

Please use professional communication and respect the maintainer’s time.

You may contact the maintainer through GitHub and repository channels.

Judging Criteria

The winner is simply:

First meaningful AgentCore PR

accepted and merged by the repository owner.

That’s it.

Why This Matters

The future enterprise AI engineer is no longer just:

a programmer using prompts

The future engineer becomes:

• architect

• operator

• reviewer

• governor

• runtime thinker

• systems integrator

• business translator

The engineers who understand this shift early will lead the next generation of enterprise systems.

Final Thought

Most AI discussions today focus on:

“How fast can AI generate code?”

We care about something different:

“How do we build systems that actually survive production?”

That is what this challenge is about.

Move beyond prompts.

Build the future.

— LearnTeachMaster.org

:::