# Functional - UnambitiousFx

> Result, Maybe, and railway-oriented error handling for .NET — zero-allocation and Native-AOT ready.

This file contains links to documentation sections following the llmstxt.org standard.

## Table of Contents

- [ASP.NET Core Integration](https://functional.unambitiousfx.com/docs/aspnetcore.md): Convert Result, Result<T>, and Maybe<T> into IResult and IActionResult HTTP responses with centralized failure-to-status mapping.
- [Functional](https://functional.unambitiousfx.com/docs.md): Lightweight, AOT-ready functional programming for .NET. Result and Maybe types, rich failure modeling, metadata, full async, and ASP.NET Core integ...
- [Maybe](https://functional.unambitiousfx.com/docs/maybe.md): A type-safe optional value (Some or None) that replaces null and composes cleanly across pipelines.
- [Result](https://functional.unambitiousfx.com/docs/result.md): Model success and failure as values with Result and Result<T> — railway-oriented programming for .NET, without exceptions for control flow.
- [Functional.xunit](https://functional.unambitiousfx.com/docs/xunit.md): Fluent, intention-revealing xUnit assertions for Result and Maybe from UnambitiousFx.Functional.
- [Getting Started](https://functional.unambitiousfx.com/docs/getting-started.md): Install UnambitiousFx.Functional, create your first Result, chain operations with Bind and Map, and handle failures.
- [Result API Reference](https://functional.unambitiousfx.com/docs/result/api-reference.md): Terse reference for Result and Result<T> — factories, inspection, matching, transformation, failure handling, side effects, extraction, metad...
- [Maybe API Reference](https://functional.unambitiousfx.com/docs/maybe/api-reference.md): Complete method surface for Maybe<T>, grouped by category, with signatures and descriptions.
- [Failures and Metadata](https://functional.unambitiousfx.com/docs/failures-and-metadata.md): Typed failure objects with stable codes plus an immutable metadata bag for attaching contextual diagnostics.
- [Custom Mappers](https://functional.unambitiousfx.com/docs/aspnetcore/custom-mappers.md): Customize how failures map to HTTP status codes — register typed mappers, write IFailureHttpMapper implementations, and tune adapter policy.
- [HTTP Mapping (Minimal API)](https://functional.unambitiousfx.com/docs/aspnetcore/http-mapping.md): Convert Result and Maybe into IResult for Minimal APIs — builders, status codes, headers, Problem Details, and endpoint patterns.
- [MVC Patterns](https://functional.unambitiousfx.com/docs/aspnetcore/mvc-patterns.md): Convert Result and Maybe into IActionResult for MVC controllers using the AsActionResultBuilder fluent builders.
- [Migration from v1](https://functional.unambitiousfx.com/docs/migration-from-v1.md): Upgrade existing UnambitiousFx.Functional code from v1 to v2 — packages, namespaces, types, and pipeline APIs.
- [Using with AI](https://functional.unambitiousfx.com/docs/using-with-ai.md): Feed the UnambitiousFx.Functional docs to Claude, Cursor, Copilot, and other AI assistants via llms.txt bundles.
- [Async Assertions](https://functional.unambitiousfx.com/docs/xunit/async-assertions.md): Assert directly on Task<Result<T>>, ValueTask<Result<T>>, and async Maybe without awaiting first.
- [Maybe Assertions](https://functional.unambitiousfx.com/docs/xunit/maybe-assertions.md): Assert the Some and None branches of Maybe<T> and chain focused checks onto the contained value.
- [Result Assertions](https://functional.unambitiousfx.com/docs/xunit/result-assertions.md): Assert success and failure branches of Result and Result<T>, chain value checks, and narrow to typed failures.
- [Test Organization](https://functional.unambitiousfx.com/docs/xunit/test-organization.md): Structure functional tests with the AAA/Gherkin pattern, descriptive names, theories, and an edge-case checklist.