Define system semantics once, then attach multiple interpretations.
## What it looks like. Ordinary C# records supply data contracts. A domain declares an entity and its transition, a process invokes that transition, and an infrastructure model declares logical resources and readiness requirements. Namespace imports and runtime bindings are omitted.public sealed record Order(string Id, bool Submitted);
public sealed record SubmitOrder(string OrderId);
public sealed class OrdersDomain : DomainModel
{
public DomainEntity<Order> Orders { get; }
public Transition<Order, Unit, bool> Submit { get; }
public OrdersDomain() : base(revision: "1")
{
Orders = Entity<Order>("orders");
Submit = Orders.Transition<bool>(
id: new("orders/submit"), revision: new("1"),
transition => transition
.Requires(order => !order.Submitted, order => false)
.Set(order => order.Submitted, true)
.Return(true));
}
}
[Process(id: "orders/submit-process", revision: "1")]
public sealed partial class SubmitOrderProcess(OrdersDomain domain)
: ProcessModel<SubmitOrder, bool>
{
protected override async ProcessTask<bool> Execute(
ProcessContext process, SubmitOrder input)
{
return await process.Transition(domain.Submit, input.OrderId);
}
}
public sealed class OrdersInfrastructure : InfrastructureModel
{
public OrdersInfrastructure()
{
Define(
id: new("orders"), revision: new("1"),
bindingProfileId: new("orders/bindings"),
infra =>
{
var state = infra.Resource(new("orders/state")).Persistent();
infra.Workload(new("orders/worker")).RequiresReady(state);
});
}
}
A guarded transition, a process referencing that exact transition, and logical infrastructure requirements. The process method is compiler input rather than an application callback. Storage and process-runtime bindings are supplied separately; the readiness edge alone does not establish them.