IntentSharp.Catalog
1.1.0
Prefix Reserved
dotnet add package IntentSharp.Catalog --version 1.1.0
NuGet\Install-Package IntentSharp.Catalog -Version 1.1.0
<PackageReference Include="IntentSharp.Catalog" Version="1.1.0" />
<PackageVersion Include="IntentSharp.Catalog" Version="1.1.0" />
<PackageReference Include="IntentSharp.Catalog" />
paket add IntentSharp.Catalog --version 1.1.0
#r "nuget: IntentSharp.Catalog, 1.1.0"
#:package IntentSharp.Catalog@1.1.0
#addin nuget:?package=IntentSharp.Catalog&version=1.1.0
#tool nuget:?package=IntentSharp.Catalog&version=1.1.0
IntentSharp.Catalog: reloadable YAML and JSON intent files
Keep an LLM call's instructions, result shape, validation rules and examples in a versioned intent file. Your C# code runs the intent by name. Supported edits reload while the application runs, so changing a rule or instruction does not require rebuilding the application.
Use this package for prompt management and runtime configuration of named intents. It adds a file-backed catalog and an in-memory catalog to IntentSharp. It targets .NET 8, .NET 9 and .NET 10 and installs the matching core version.
Quick start: check an urgency score without a model
This complete example uses scripted replies, not AI inference. The first reply is 9, which breaks the file's range; the second is 4, which passes. No API key or model service is used.
dotnet new console -n IntentFiles --framework net8.0
cd IntentFiles
dotnet add package IntentSharp.Catalog --version 1.1.0
Create intents/Orders.ClassifyUrgency.intent.yaml:
name: Orders.ClassifyUrgency
version: 1
owner: order-desk
intent: Rate the urgency of this order email from 1 (routine) to 5 (critical).
shape:
kind: primitive
primitive: int
rules:
minimum: 1
maximum: 5
examples:
- input: "Line 3 is down until the bearings arrive. Ship today."
output: '{"value": 5}'
Add this item group inside the application project file:
<ItemGroup>
<None Update="intents/**/*" CopyToOutputDirectory="PreserveNewest" />
</ItemGroup>
Replace Program.cs with:
using IntentSharp;
using IntentSharp.Catalog;
using IntentSharp.Testing;
var provider = new ScriptedProvider("{\"value\":9}", "{\"value\":4}");
using var client = new IntentClientBuilder()
.UseProvider(provider)
.Configure(options => { options.MaxAttempts = 2; options.MaxModelCalls = 2; })
.Build();
using var catalog = new FileIntentCatalog(Path.Combine(AppContext.BaseDirectory, "intents"));
var runtime = new IntentRuntime(client, catalog);
var result = await runtime.RunAsync<int>("Orders.ClassifyUrgency",
"Our packaging line stops on Thursday unless the replacement belts arrive.");
Console.WriteLine($"Success: {result.Success}");
if (result.Success) Console.WriteLine($"Urgency: {result.Value}");
else foreach (var issue in result.Issues) Console.WriteLine(issue);
Console.WriteLine($"Provider calls: {provider.CallCount}");
Run dotnet run. The output is:
Success: True
Urgency: 4
Provider calls: 2
This demonstrates enforcement of the numeric rule and a retry. It does not measure the quality of an AI urgency classification. For real inference, replace the scripted provider with the provider-file setup in the core package quick start.
What belongs in an intent file?
| Part | Purpose |
|---|---|
| Name and version | Identify the behavior your code requests and the definition in use |
| Instruction | Describe the model's task |
| Result shape | Text, primitives, a registered .NET type or JSON checked against a JSON Schema |
| Rules | Check the returned value in your process |
| Examples | Show the model sample inputs and outputs; examples do not replace validation |
Reloads and their boundaries
In a running application, edit the file in the folder the catalog watches, increment its version and save it. After the reload is processed, subsequent calls use the new definition; calls already running keep their current definition. A malformed edit keeps the last good definition and reports the load problems.
The example watches the files copied to the build output. Editing the project copy reaches that output only on a later build. For live edits, edit the watched output copy or configure an absolute path to your managed intent folder. Reload is tested on local folders.
Versioned documents support reverting an earlier definition. New compiled result types, shapes the caller's type cannot read, new named code checks and new call sites still need an application release. A passed check establishes that the configured rules passed, not factual correctness.
Which package do I need?
| Need | Package |
|---|---|
| Inline calls and checks defined in C# | IntentSharp |
| Named intents in YAML, JSON or an in-memory catalog | IntentSharp.Catalog |
| Rule files for model, tool and data-operation checkpoints | IntentSharp.Guardrails |
An IChatClient backend or intents exposed as agent tools |
IntentSharp.Extensions.AI, which includes Catalog |
| Models defined per intent, obtained from a specialist service you wire in | IntentSharp.Specialist, which includes Catalog |
Keep all installed IntentSharp packages at the same version.
Documentation, evaluation and support
Commercial software, not open source. Evaluate free for 30 days on development and test systems; after that, business use needs a paid license. Production use needs a paid license from the first day. For help, use the website's support information or NuGet's Contact owners link.
The wider direction
External intent files are one building block of Unified Intent Architecture: explicit instructions, contracts and rules alongside application logic. Catalog handles these definitions; your application supplies its integrations and approval process.
Built and sold by C2Consultants LLC. C2Empowered, the company's self-hosted operations platform, is built on IntentSharp; how the two fit together.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 is compatible. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- IntentSharp (= 1.1.0)
- JsonSchema.Net (>= 9.4.1)
- YamlDotNet (>= 18.1.0)
-
net8.0
- IntentSharp (= 1.1.0)
- JsonSchema.Net (>= 9.4.1)
- YamlDotNet (>= 18.1.0)
-
net9.0
- IntentSharp (= 1.1.0)
- JsonSchema.Net (>= 9.4.1)
- YamlDotNet (>= 18.1.0)
NuGet packages (2)
Showing the top 2 NuGet packages that depend on IntentSharp.Catalog:
| Package | Downloads |
|---|---|
|
IntentSharp.Extensions.AI
Typed, checked LLM results and agent tools for Microsoft.Extensions.AI IChatClient in C# and .NET. Use your configured chat client, such as Ollama or Azure OpenAI, with IntentSharp validation and bounded retries for invalid output. The backend and its configured adapters determine available models. UseChatClient and UseChatClientAsFallback select providers in code; the chat-client kind in a provider file selects a registered client. AsAIFunctions exposes catalog intents as AIFunction tools for Microsoft Agent Framework or another function-calling host: return a value after the intent checks pass, or an error result describing failure. The host executes function calls. Transport failures are not retried by IntentSharp; configure those retries in the chat-client pipeline or use a fallback. Installs the matching IntentSharp and IntentSharp.Catalog packages. Native OpenAI GPT or Anthropic Claude calls without IChatClient need only the core package. Commercial software, not open source: evaluate free for 30 days on development and test systems; after that, business use needs a paid license, and production use needs one from the first day (intentsharp.com/pricing). |
|
|
IntentSharp.Specialist
Models defined per intent for C# and .NET, so one application can use several models easily, within one context or across several. For an IntentSharp catalog intent it sends the definition and the context you choose to a specialist service you wire in, waits until a specialist is provided, checks that the returned definition and specialist fit (a comparison in code by default; probe cases and an AI judge are opt-in), keeps the specialist's name and the returned intent for reuse, and runs the intent on that model through the normal IntentSharp pipeline, so every answer is still checked against your type and your rules. It never trains, tunes or changes a model and names no specialist provider: the service adapter, the store, the context sources, the fit checks and what happens after an offer does not fit are seams, and every setting is an option with a default. An offer names a provider configured on the client or brings its own, which the client reaches through a router by name only. A changed definition requests again, and keep-previous lets the specialist in use serve meanwhile. A document store keeps requests, tickets, fit reports and held specialists across restarts and processes; wait windows and an hourly request limit bound the exchange, and a guardrail checkpoint can refuse a request before anything is sent. A scripted specialist service and a contract kit test applications and adapters offline. Installs the matching IntentSharp and IntentSharp.Catalog packages. Commercial software, not open source: evaluate free for 30 days on development and test systems; after that, business use needs a paid license, and production use needs one from the first day (intentsharp.com/pricing). |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 1.1.0 | 55 | 11/13/2026 |
| 1.0.1 | 258 | 11/6/2026 |
| 1.0.0 | 175 | 10/28/2026 |
| 1.0.0-rc.3 | 90 | 10/20/2026 |
IntentSharp 1.1.0: a fifth package, IntentSharp.Specialist, for models defined per intent, and additions to the four existing packages. Nothing is removed or changed in meaning, so an application on 1.0.x upgrades without code changes. Release notes: https://intentsharp.com/changelog