Team

The Agentic AI Partner Library is curated by the vTeam. This page covers who we are, how the curation workflow works, and how team members can add and edit content directly.

Who We Are

Cross-Solution

Member	Role	Focus Areas
Johan Wallquist · @jwallquist_microsoft	vTeam Lead	Architecture, delivery, governance
Peter Rhodin · @peterrhodin	Sr Partner Solution Architect	Dynamics 365, Power Platform, Copilot, Modern Work

AIBS — AI Business Solutions

Copilot, Copilot Studio, Power Platform, Dynamics 365, M365

Member	Role	Focus Areas
Lorette Roos · @loretteroos4	Sr Partner Solution Architect	Copilot, Copilot Studio, Power Platform

CAIP — Cloud and AI Platform

Microsoft Foundry, Agent Framework, Semantic Kernel, Azure AI, Fabric

Member	Role	Focus Areas
Kiko de Angel Gimeno · @frdeange	Sr Partner Solution Architect	Azure AI Foundry, Semantic Kernel, custom agents

Security

Entra ID, Defender, Zero Trust, Responsible AI, Compliance

Member	Role	Focus Areas
TBD	—	—

---

How Curation Works

The Flow

Partner or team member suggests a link (via the site form or GitHub Issue)
  ↓
Auto-triage detects solution area → labels the Issue → @pings the right reviewer
  ↓
Reviewer verifies the link, assesses quality, categorizes it
  ↓
Reviewer creates a PR with the link in the correct Markdown format
  ↓
Another team member reviews the PR (or self-merge if minor)
  ↓
Merge to main → CI auto-deploys to the live site

Auto-Triage

When a new Issue with the link-suggestion label is created:

1. A GitHub Action reads the Issue body and detects solution areas (AIBS/CAIP/Security)
2. It adds the appropriate label(s) to the Issue
3. It looks up team.yml in the repo to find the right reviewer
4. It posts a triage comment and assigns the reviewer

If no specific reviewer is found, the suggestion goes to the vTeam Lead.

The Team Roster (team.yml)

The file team.yml in the repo root maps team members to solution areas. Update it when people join or leave:

team:
  - github: username_microsoft
    name: First Last
    role: Solution Architect
    areas: [AIBS, Cross-solution]
    focus: [Copilot Studio, Power Platform]
    active: true

---

Adding & Editing Links Directly

Team members with repo access can skip the suggestion form and edit content directly.

Quick Start

# Clone (first time only)
git clone https://github.com/JW-Sthlm/agentic-ai-partner-library.git
cd agentic-ai-partner-library
npm install

# Create a branch and edit
git checkout -b add/my-new-link
# Edit the appropriate docs/*.md file
git add -A && git commit -m "Add: Title of Resource"
git push -u origin add/my-new-link
# Open a PR on GitHub

Link Format

Each link is an H3 heading with emoji, URL, description, and tags. Follow this format:

• Heading: H3 with emoji and link title: ### 📖 [Title](URL)
• Description: 1-3 sentences explaining what the resource covers and why it's valuable
• Tags: 9-tag line with solution, contentType, audience, shareability, maturity, product, pattern, owner, lastReviewed

Content Type Emojis

Type	Emoji	Type	Emoji
Documentation	📖	Course / Training	🎓
Blog post	📝	Webinar / Recording	🎥
Repo / Sample	💻	Whitepaper	📄
Architecture	📐	Tool	🔧

Tag Order (all 9, always)

solution · contentType · audience · shareability · maturity · product · pattern · owner · lastReviewed

Use — for optional tags (product, pattern) that don't apply.

Valid Tag Values

Tag	Allowed values
solution	AIBS · CAIP · Security · Cross-solution
contentType	documentation · blog · repo · webinar · course · recording · sample · architecture · tool · whitepaper
audience	architect · developer · seller · partner · security · delivery-lead
shareability	partner-NDA · internal-only · public
maturity	foundational · recommended · advanced · experimental

Category Files

Category	File
Start Here	docs/start-here.md
Agentic AI Fundamentals	docs/agentic-ai-fundamentals.md
AIBS Foundations	docs/solution-foundations/aibs.md
CAIP Foundations	docs/solution-foundations/caip.md
Security Foundations	docs/solution-foundations/security.md
Architecture & Patterns	docs/architecture-and-patterns.md
Security & Governance	docs/security-governance-responsible-ai.md
Build: APIs & SDKs	docs/build-extend-integrate/apis-and-sdks.md
Build: Tools & Utilities	docs/build-extend-integrate/tools-and-utilities.md
Build: Tutorials	docs/build-extend-integrate/tutorials-and-walkthroughs.md
Build: Sample Code	docs/build-extend-integrate/sample-code-and-repos.md
Ways of Working	docs/ways-of-working-and-delivery.md
Scenario Blueprints	docs/scenario-blueprints-and-playbooks.md
Learning & Community	docs/learning-events-community.md
News & Updates	docs/news-and-updates.md

Using Copilot

In VS Code or Codespace, Copilot understands the repo format. Try:

• "Add a link for the Azure AI Foundry evaluation guide" — generates the full entry
• "Suggest 5 links about multi-agent orchestration" — researches and drafts entries
• "Review the links in this file for duplicates" — checks quality

Deploying

After merging to main, CI auto-deploys. For manual deploy:

npm run deploy

Validating

npm run validate-metadata   # Check all links have valid tags
npm run check-links          # Check for broken URLs (requires lychee)

---

Join the Team

Want to help curate? Reach out to @jwallquist_microsoft — we'll add you to the repo and the team roster.