IanFrelinger 

Ashlar's agent-execution ports: IAgent, ITool, IToolbox, IAgentMemory, IModel, IPolicy, plus barrier-level context, IAgentTransport, and endpoint-routing contracts shared across hosts and transports.

Stable wire DTOs and code-brick authoring contracts for Ashlar bricks.

Core Ashlar domain model including brick authoring base types and execution contracts.

Content-bound certification record verification for external brick consumers.

Ashlar's application layer: the port interfaces infrastructure implements - ICertificationGate, ICertifiedBrickAdmission, IRollbackManager, IAgenticBrickEngine - with their request/result records, MediatR... More information

Client side of Ashlar's agent transport: a gRPC IAgentTransport invoking agents on remote hosts, with per-endpoint channel caching, mTLS/custom-CA options, and barrier-context headers.

Roslyn rules for Ashlar brick code: contract drift, constructor purity, determinism, and the certification analyzer-gate catalog.

Concrete agent-execution services for an Ashlar host: a step loop that approves an entire tool-call chain before executing it, barrier-level identity resolution with audit sinks, and endpoint/transport... More information

Shared HTTP DTOs and distributed execution contracts (envelopes, evidence, native host ports) for Ashlar API, client, and product hosts.

Three ready-made IPolicy implementations that approve or deny agent tool calls: AllowAllPolicy, OutputPathSandboxed (rejects a call whose 'output' argument resolves outside the snapshot's OutputRoot), and... More information

Default implementations behind Ashlar's application ports: CertificationGate with its mutation and witness runners, signed certification record stores, LLM provider factories, and their DI extensions. The... More information

Microsoft.Extensions.AI governed chat pipeline for Ashlar (local Ollama, local LLamaSharp/ONNX-key target, and future cloud targets).

Provider-agnostic LEGO-style feature factory CLI

ITool implementations for repository work in an Ashlar agent host: file read/write/list/search-replace resolved against the host-supplied repo root, Roslyn source-consistency rules, and dotnet build/test/run,... More information

Three ITool implementations for an Ashlar kernel that inspect .NET assemblies: assembly.analyze reads metadata, assembly.decompile emits C# source, assembly.security_scan flags dangerous API calls.

Multi-agent orchestration for Ashlar: IArchitectAgent decomposes a request into AgentSpawnSpecs, Orchestrator spawns and sequences the agents and reconciles their outputs, IDomainAgentProvider adds your own... More information

Hosts Ashlar's unattended agents: JSON agent configs, cron/interval scheduling, and a registry that gates registration on an approval gate and on per-agent policy narrowing. Ships the opt-in trust layer too -... More information

Hosting extensions for embedding the Ashlar kernel in applications. Call AddAshlar() to register orchestration, adaptation, persistence, trust, and agent services.

HTTP client for Ashlar API. Used by CLI, demos, and other remote clients.

Minimal package for code-authored Ashlar bricks: Brick base types, execution contracts, and host registration helpers. It does not bring the host: a host that calls AddAshlar() references... More information