Product / RiskGuard

Risk review before the transaction becomes a provider problem.

RiskGuard is the pre-sign review cockpit for transaction context, KYT/AML signals, escalation, and evidence export.

Use case: Give compliance and product teams a shared risk record before money moves.
Product console

One review trail for product, compliance, and finance.

RiskGuard is designed for teams that need explainable transaction decisions across providers, chains, and internal teams.

Operating boundary

Risk inputsIntentCounterpartyVelocityProvider state
RiskGuard review layerSignalsScoreEscalationReceipt
Control outputsClearReviewBlockMonitor
Evidence destinationsComplianceSupportFinanceAudit
Review states

The cockpit makes the status obvious.

Clear

Intent is within policy and risk tolerance.

Review

Signals require human or automated escalation.

Block

The operation is stopped with reason-coded evidence.

Monitor

Approved operations can still carry watch conditions into reconciliation and support.

Signal model

Risk context should stay attached to the operation.

Counterparty

Destination, ownership, screening context, and prior interaction history.

Velocity

Amount, frequency, corridor, asset, and wallet behavior compared to policy expectations.

Provider state

Provider availability, unsupported operations, approval pauses, and native error context.

Decision evidence

The final outcome links back to the signals and reviewers that shaped it.

Evidence

Proof the buyer can inspect.

Every route keeps Alloy's public story grounded in operating records, custody boundaries, and right-sized modules.

Pre-sign timingRisk context is evaluated before provider submission.
Explainable outcomeThe decision record shows which signals mattered.
Audit exportStructured evidence can flow into customer compliance and review packages with customer-governed access and retention.
Decision logReason-coded outcomes stay attached to the transaction intent as immutable review references.
Escalation ownershipReview, block, and monitor states have visible owner and next-action context.
Next step

Bring your current provider stack.

We will map the first workflow Alloy should stabilize, the custody boundary, and the modules that create evidence.