1290 posts · Page 78 of 108. ← Blog
A clear-eyed look at trust models, who signs what, rails, credential handling, and settlement — and why these four overlap more than they compete.
A clear-eyed comparison across trust model, who signs what, payment rails supported, credential handling, settlement, and best-fit use cases.
How to combine a deterministic rules engine with an ML risk model in a single decision: rule precedence, score bands, shadow mode, and champion/challenger evaluation with feedback labels.
Teaches how to combine a deterministic rules engine with an ML risk model in one decision path: rule-precedence and overrides, model score bands, shadow mode, and champion/challenger evaluation with feedback labels.
How a risk-driven layer escalates from silent approval to OTP, biometric, or 3DS challenge — holding a pending-challenge state and resuming the original transaction once the customer clears it.
Teaches how to build risk-based step-up auth: an orchestration layer that escalates from silent to OTP/biometric/3DS challenge based on risk signals, with pending-challenge state and resumable transaction context.
How to ingest many rate feeds, derive a trustworthy mid, defend against stale prices, and quote a locked customer rate that survives a settlement failure.
Teaches how to build an FX pricing service: ingesting multiple rate feeds, mid-rate derivation, staleness/circuit-breaker handling, per-segment spread/markup, and rate-lock quotes with expiry for customer conversions.
A `Session` is the conversation; `state` is the key-value bag agents and tools read and write — and the prefix on a key decides how long it lives.
A Session holds a conversation; state is a scoped key-value store (session/user/app/temp) read and written by tools, injected into instructions via {state} templating, and persisted by SessionService.
How to broadcast one input to several executors in parallel and join their answers with a barrier — the core workflow graph primitives, with no LLM in the way.
A start executor broadcasts a question to two experts via a fan-out edge; a fan-in barrier edge joins both answers before the aggregator yields output.
Agents as graph nodes: switch-case routing, fan-out/fan-in, and mixing plain functions with agent steps in one workflow.
Agents are just workflow executors: switch-case routing, fan-out/fan-in concurrency, and mixing plain function nodes with agent nodes in one graph.
Building a computer-vision system that works in a demo is one thing; building one that works reliably in the real world — at the right speed, cost, and robustness — is another. This closing post assembles the series into practical judgment: how to approach a vision problem, the deployment realities that trip teams up, and where the field is heading. It turns pixels-to-understanding from a concept into something you can actually ship.
Building a vision demo is one thing; shipping a reliable system at the right speed, cost, and robustness is another. A workflow for approaching a vision problem, the deployment realities (efficiency for real-time/edge, robustness to distribution shift, edge cases, monitoring), and where the field is heading — multimodal and foundation models.
An objection feels like a rejection — the customer pushing back, resisting, saying no. The mental shift that transforms selling is realizing an objection is usually the opposite: a sign of engagement, a real concern surfaced, an invitation to address the thing standing between them and yes. Handled with the pushy-sales playbook (overcome it, pressure through it), objections end deals. Handled with genuine understanding, they're how deals get closed — by resolving the real concerns that were always going to decide the outcome.
An objection feels like a rejection — the customer pushing back. The mental shift that transforms selling is realizing it's usually the opposite: a sign of engagement, a real concern surfaced, an invitation to address the thing standing between them and yes. Handled with genuine understanding, objections are how deals get closed.
How Python decides what runs next — conditionals and the ternary, for-each iteration done idiomatically, while loops, break/continue and the surprising loop-else, structural pattern matching with match/case, and where truthiness and comprehensions fit in.
How Python decides what runs next — conditionals and the ternary, for-each iteration done idiomatically, while loops, break/continue and the surprising loop-else, structural pattern matching with...
How Go treats functions as ordinary values — and what that buys you: the (result, error) idiom, variadic APIs, closures over shared state, and the decorator/middleware/option patterns that fall out of passing functions around.
How Go treats functions as ordinary values — and what that buys you: the (result, error) idiom, variadic APIs, closures over shared state, and the decorator/middleware/option patterns that fall out of...
How Visa Account Updater and Mastercard Automatic Billing Updater keep stored credentials alive when cards get reissued, expire, or change numbers.
How VAU/ABU keep stored credentials current, credential-on-file mandates, and reducing involuntary churn from expired/reissued cards.