Entity / One domain declaration

One rule, three readers

This short example declares an Item entity with a stock invariant and a Hold write, then checks it with Entity.judge and Laws.check:

ts
import { Schema } from 'effect'
import { Entity, Expr, Laws } from 'foldkit-entity'
import { Mutation } from 'foldkit-remote'

const Item = Entity.define(
  'Item',
  Schema.Struct({ id: Schema.String, stock: Schema.Number, reserved: Schema.Number }),
).pipe(
  Entity.invariant('reservedWithinStock', ({ after }) => Expr.lte(after.reserved, after.stock), {
    message: 'Reserved stock cannot exceed the stock',
    path: ['reserved'],
  }),
)

const Hold = Mutation.update('Hold', Item, { set: { reserved: Schema.Number } })

// Reader 1: pure reference judge over an in-memory row.
Entity.judge(Item, { after: { id: 'i1', stock: 3, reserved: 5 } })._tag // 'Invalid'

// Reader 2: static analysis of every declared write against every invariant.
Laws.show(Laws.check({ writes: [Hold] }))
// Hold   x reservedWithinStock   refused: Reserved stock cannot exceed the stock
//     before   reserved: 0, stock: 0
//     input    reserved: 1
//     after    reserved: 1, stock: 0

Both Entity.judge and Laws.check run purely on declarations in memory. Laws.check immediately flags that Hold allows setting reserved past stock, meaning the third reader—the server writer—must enforce that invariant inside the SQL UPDATE where Hold commits. All three readers act on one rule written once.