MAGNIFIC | Docs

Introduction

MAGNIFIC is built around a simple premise: agent authority should be defined before execution, not inferred after a wallet signs. The platform expresses permissions, boundaries and decisions through one readable surface.

Core sequence

request → policy → simulation → execution → record

Core concepts

Agent

An automated actor that submits an onchain request through an operational workflow.

Policy

A set of explicit rules that determines whether the request fits the agent’s allowed scope.

Execution context

The target, asset, amount and action information attached to the request.

Record

A structured outcome that captures the decision context and resulting status.

Policy example

A treasury policy can be expressed with a transaction ceiling, daily operating budget and approved target list.

policy treasury_01 { max_transaction: 250 USDC daily_budget: 1000 USDC allowed_assets: [USDC, WETH] allowed_targets: [approved_router] preflight_required: true }

Operating model

MAGNIFIC is intended to give teams a clean policy view before execution and a clean record after execution. The interactive simulator in this site mirrors that same logic by showing how a request can be evaluated against an active policy rule set.

Reference the MAGNIFIC operating model.