AegisPay

@7bryan7·Bryan Roger B·6 followers·added 2026-10-24

AegisPay runs accounts payable as a bounded pipeline. An invoice image enters through apps/server/src/extraction, becomes a typed obligation validated by Zod schemas in packages/core/src/schemas.ts, and is matched against vendor and purchase-order registries. apps/server/src/treasury/evaluate.ts computes reserve floors, budget limits and outstanding commitments, and apps/server/src/agent/planner.ts (planPayable, createGeminiPayablePlanner) hands the model only the permitted candidates such as PAY_NOW, SCHEDULE or HOLD; the proposal must cite evidence and is re-validated. payments/authorization.ts binds exact terms to invoice, policy, vendor-address and PO versions, so any change invalidates them. Settlement goes through apps/server/src/payments/circle.ts with @circle-fin/developer-controlled-wallets, PostgreSQL reservations from migrations/004_payables.sql, stable idempotency keys and a leased worker loop in payments/dispatch.ts; reconciliation.ts and arc-receipt.ts independently verify the Arc receipt before the ledger closes.