Sr. Content Developer at Microsoft, working remotely in PA, TechBash conference organizer, former Microsoft MVP, Husband, Dad and Geek.
165050 stories
·
33 followers

Random.Code() - Adding Generics Support to SaferAccessors, Part 5

1 Share
From: Jason Bock
Duration: 1:15:12
Views: 49

In this stream, I hope to wrap up this feature by getting constraints into the extension definitions, and then maybe move on to other features.

https://github.com/JasonBock/SaferAccessors/issues/4

#dotnet #csharp

Read the whole story
alvinashcraft
9 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

Critter Stack Roadmap Update for November 2026

1 Share

I haven’t done one of these posts for awhile, and the year is winding down fast. I personally have the Thanksgiving week, a big trip down under for the Yow Conference in Brisbane and Melbourne, and a fervent wish to take a lot more time off during the holidays than I have for years this year.

The big ticket items are major version releases of the major Critter Stack tools to add .NET 11 and drop .NET 9:

  • Weasel 10.0 – a bit of modernization, some .NET 11 related optimizations, Npgsql 11 when it lands
  • Marten 10.0 – lots of optimizations, some tidying up of the public API that’s kind of bloated, and flipping some defaults for improved observability. A big, unexpected win is going to be significant performance optimizations to the DCB support
  • Fisher 2.0
  • Polecat 6.0 – really the same new things as Marten
  • Wolverine 7.0 – lots of optimizations, using the Dekaf library for Kafka, flipping some defaults for improved observability.
  • CritterWatch 2.0 – using the new major versions above
  • Bobcat 1.1 – enabling .NET 11 mostly, but there are some significant improvements that got missing in 1.0

I don’t have a perfect timeline for when this will all be done, but we have alpha releases out for everything. We’re waiting a bit on some upstream dependencies like Npgsql 11 before we finish the official releases. I’m also abusing my poor MBP doing a lot of performance testing and optimization work that will continue for awhile.

For all of the tools, we’re trying to take advantage of new features in .NET 11 like the runtime asynchronous compilation to save on memory usage (which we’ve proven to benefit Wolverine at least) and some improvements for serialization. We’re investing much more this time in performance testing as we go than we were able to in the last round of major releases. We’re also doing a lot of work to try to lift duplicated code from Marten, Fisher, and Polecat into shared libraries as a way of easing support over time.

My big initiative for JasperFx right now is writing a new version of our internal CRM portal application to try to automate much more of JasperFx’s business. This is partially because I despise paperwork of all kinds and JasperFx has fortunately gained enough business that spreadsheets are no longer enough. I am also using this work to do more dogfooding of our greater “Event Modeling” story across the Critter Stack. We’ll put most of this code and work into a public repository and use this to rebuild a new set of tutorials on Event Modeling, Spec Driven Development, and using AI agents to scaffold Critter Stack applications.

Now, some bigger themes for new work:

Improvements to Wolverine’s Saga support and really its ability to support long running workflows all the way around. To be blunt, I’m looking to make Wolverine the absolute best server side platform for long running workflows out there, so we’re planning some improvements to the Saga support for diagnostics, error handling, compensation action support, more visualization and user interface or MCP management in CritterWatch, and even finally dipping our toes into a routing slip capability. I’m experimenting a little bit with an alternative syntax to define sagas through something like the Azure Durable Functions syntax that still functions as a Wolverine Saga behind the scenes. We will absolutely have an event sourced Saga capability that I think will pair very well with CritterWatch. I’m also going to experiment with using Wolverine’s virtual actor capability for long running tasks like file imports that don’t necessarily fit well into the existing messaging.

For the event stores, I think there’s an opportunity to expand our support for “cold storage” of event data to formal ways to “un-thaw” archived data on demand. A pair of JasperFx clients have now expressed interest in that.

Adding 2nd level caching to our event sourced command handlers. See this issue that’s been in our backlog quite awhile (that I would heavily consider dogfooding in CritterWatch). This will have to pair up with our global partitioning feature in Wolverine. More or less, the general idea is in some cases, we’ll basically have a very highly optimized architecture for event streaming within a cluster where operations are emitting events to persist in Marten or Polecat.

I guess I need to just come out and say that I’m somewhat interested in extending Wolverine into actor-based architectures. I think we have the foundation to do that already, especially after we had to harden our leadership election and agent assignment subsystem this year.

We need to break down and have an easy recipe for people to designate roles to different nodes in what’s otherwise the same Wolverine application. The need here is people who want only some nodes to run the transactional inbox/outbox agents or only some nodes to run messaging while maybe some nodes only handle HTTP traffic. Today you really need to do that with two logical Wolverine applications with isolated Wolverine node tracking storage.

I’m interested in adding formal support for the latest version of Quartz.Net in Wolverine and CritterWatch. Especially after Quartz.Net adopted Weasel for their own database schema management.

I don’t really know what to say about Stoat. I think the “AI Agent Wrangler” tool market is already way too crowded and it’s probably a fool’s game to play too much in that pool. The one thing that Stoat probably does earn its keep is managing and scheduling agent behavior and quality gates on a single box. Stoat might settle into just being a JasperFx internal tool, or it might grow into something that sits between the local work and newer AI planning tools like Linear.

Anyway, I’m thinking out loud here. I’m always interested in any feedback!



Read the whole story
alvinashcraft
10 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

AIStoryBuilders 4.0 is in the Microsoft Store: everything that's new for Windows

1 Share
AIStoryBuilders 4.0 for Windows is a free update in the Microsoft Store. It brings a Knowledgebase for every story, a writing voice the AI follows, Story Chat changes you approve before they happen, local models with Ollama, and a redesigned workspace. Your stories carry over unchanged.
Read the whole story
alvinashcraft
10 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

v2026.11.4

1 Share

OpenClaw 2026.11.4

Read the whole story
alvinashcraft
10 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

XBOX 25th Anniversary Magazine: Explore 25 Years of Games, Stories, and Memories

1 Share

The 25th Anniversary of XBOX has given fans much to celebrate: the milestones, the memories, and a whole slate of fun news for our players.  

We know that many of our longtime fans first learned about the original XBOX by reading about it in a magazine back in the day. For you, we created XBOX – The 25th Anniversary Magazine, a special publication designed not only to look back at 25 years of play, but also to celebrate the present and future of XBOX. We printed copies to share with community members at XBOX FanFest in Seattle this past week, and today, it’s available for all to read right here: 

Protip: you can go full screen for easier reading by clicking the arrows in the lower right of the player.

The magazine explores games, hardware, and moments, past and present, told through the teams who are building them. You’ll revisit memories from your favorite franchises, learn some lore about XBOX’s storied history, and read new details about games that haven’t yet released; want to know more about Fable’s capital city of Bowerstone? Turn to page 38! 

We hope you enjoy this decidedly analog celebration of the last quarter century and a first look at what’s ahead.  XBOX’s story has always been written alongside our players. Thanks for reading, and for being part of what comes next. 

The post XBOX 25th Anniversary Magazine: Explore 25 Years of Games, Stories, and Memories appeared first on XBOX Wire.

Read the whole story
alvinashcraft
11 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

Learn Microsoft AI Citadel for Foundry Today

1 Share

Your first AI agent is in a Microsoft Foundry project, and it works. Then Finance wants one. Procurement wants one. Customer Support wants three. Before long, someone asks which agents can send customer data to an external model, why one team used half the available token capacity, and who can disable an agent that’s making the wrong changes in a business system.

Those questions are hard to answer if every team picks its own model endpoints, credentials, and monitoring. They’re also hard to answer if every change has to go through one central team. Microsoft’s AI Citadel Blueprint gives architects a way to set common rules while letting business teams build and operate their own agents.

What is Microsoft AI Citadel?

Citadel is Microsoft’s reference architecture for governing AI across an enterprise. It builds on Azure AI Landing Zones and brings together Microsoft Foundry, Azure API Management, Microsoft Agent 365, and the Microsoft security stack. The blueprint describes where to enforce policy, where to run and monitor agents, and who should own each responsibility. Its Gateway Landing Zone includes a deployable accelerator for the shared gateway. Microsoft’s Citadel Blueprint · Azure AI Landing Zones

The architecture has four layers. Each answers a different question an enterprise has to settle before it scales.

LayerWhat it doesQuestion it answers
Governance HubUses Azure API Management to route AI requests and enforce policies such as model access, token limits, and content safety on traffic it handles.Which models can this workload call, and under what limits?
Agent OperationsUses Foundry Agent Service and Foundry Control Plane to run and oversee agents, with traces and evaluations to investigate behavior and quality.What did the agent do, and how well did it do it?
Agent ManagementUses Agent 365 for enterprise inventory and lifecycle oversight, with Microsoft Entra providing identities and access controls for supported agents.Who owns this agent, what identity does it use, and how do we retire it?
Security FoundationBrings together Entra for access, Defender for threat detection and response, and Purview for data protection and governance.How do our security and data policies apply across the AI estate?

The usual deployment is hub-and-spoke. The platform team runs the shared gateway, and workload teams run agents in their own environments. A workload can use a common gateway without sharing another team’s Foundry project, data, or release schedule. That gateway can route to approved backends across providers, including Azure OpenAI, Amazon Bedrock, and Google Gemini. Gateway policies apply to requests that pass through it, so architects still have to control direct access to backends and account for traffic that takes another path. Microsoft’s blueprint and enforcement boundaries · Gateway overview and supported backends · Foundry Control Plane

What’s available today?

As of November 15, 2026, Microsoft’s release notes list the Citadel Governance Hub v1 accelerator as generally available, following its October announcement. The documented hub release is 1.0.2. The GA capabilities include multi-provider model routing, Backend Contracts, Access Contracts, and usage ingestion for reporting and cost allocation. Citadel is the overall architecture, and the GA announcement applies to its Layer 1 accelerator. Microsoft’s October release notes and version table

Several capabilities in that release are still in preview. These include Publish Contracts for tools exposed via Model Context Protocol (MCP) and agents exposed via Agent2Agent (A2A), the Foundry-to-API Management connection and Foundry-hosted A2A publishing documented for Citadel, and the APIM Gateway Upgrade path for existing deployments. Agent 365 separately reached general availability in May 2026, and individual Foundry and Agent 365 capabilities have their own release status. If a production design depends on one of those integrations, verify the status of that specific feature before committing to it. Citadel release notes · Foundry integration guide · Agent 365 availability announcement

Why architects would use it

The part I’d start with is the distinction between a Backend Contract and an Access Contract. The backend contract defines where model requests go, how the gateway authenticates to the provider, and how it routes requests or handles a backend failure. The access contract defines what a consuming application or agent is allowed to use, along with the limits and policies that apply to it. Both can live in version control, where a team can review a new model or access change before deploying it. Microsoft’s Governance Hub architecture

Say Procurement and Customer Support both use a model for summarization. The platform team can onboard approved backends once and expose a model alias. Procurement can have its own model allowlist, token quota, and sensitive-data policy. Support can get a different quota and a backend pool configured for its availability needs. The application teams can keep using the alias when the platform team changes the underlying deployment, provided it preserves the API and behavior those workloads depend on. I’d test failover with each workload’s evaluation set, especially when the fallback changes the model or the region that processes the request. Microsoft’s gateway release notes · Gateway resiliency guidance

What enterprises need before agents can act

Imagine Procurement extends its agent from summarizing supplier quotes to drafting purchase orders. Now four controls matter on the same workflow.

  • Least privilege and a named owner. Give the agent an identity scoped to the supplier data and draft-order operation it needs. Assign an owner who can review access and disable the agent when necessary. The purchasing system should enforce the buyer’s approval before an order can be submitted. Gateway access to the model and authorization to commit a purchase are two separate decisions. Microsoft’s Citadel Blueprint · Agent 365 overview
  • Data protection at each boundary. Decide what supplier information can leave the workload, which providers and regions can process it, and what goes into logs. The gateway can apply configured content-safety and personally identifiable information (PII) controls to supported traffic. The application and data services still need their own access and retention policies. Citadel Governance Hub architecture
  • Evidence you can use in an incident. Use gateway telemetry to see which backend handled a request and whether it was throttled. Use Foundry traces to inspect the agent’s steps, and application audit records to verify who approved the order and what was submitted. An enterprise needs enough evidence to reconstruct the action without routinely storing sensitive prompts and responses. Foundry Control Plane · Citadel observability and governance
  • Capacity and cost accountability. Give Procurement its own quota and usage reporting so a sudden spike is visible and one workload is less likely to consume capacity another team needs. Model failover can help with backend outages. The shared gateway also needs capacity planning, monitoring, and a recovery plan of its own. Gateway release notes · Gateway business continuity guidance

Lino’s take

I’d start with one Foundry-backed workload, one approved model backend, and one access contract in a non-production environment. Prove that the gateway denies access to an unapproved model, that the team can trace a failed run, and that Finance can attribute the usage. Then onboard a second team and see whether it can use the same onboarding process with a different identity, quota, and release schedule. Azure Samples Governance Hub accelerator

If you’re planning how to run Foundry agents across several teams, we can help you design the landing zone, define platform ownership, and train the people who will operate it. Contact The Training Boss

The post Learn Microsoft AI Citadel for Foundry Today appeared first on The Training Boss.

Read the whole story
alvinashcraft
11 minutes ago
reply
Pennsylvania, USA
Share this story
Delete
Next Page of Stories