Visual direction

Diagram system comparison

Every current docs diagram shown with its Mermaid default and a proposed Nava-native diagram system.

Loading diagram...

The same flow, reorganized around ownership, trust boundaries, and the decision that changes execution.

Ownership laneYour integration

Verification laneNava Guardian

BuildConstruct the exact action

Keep signing and venue submission local.

RequestRequest a policy verdictPOST /transactions

EvaluateResolve policy and run checks

Deterministic checks only.

VerdictReturn a versioned decisionpending / approved / rejected

HandleAct on the exact verdict

ApprovedSubmit to venueEverything elsePause action

Architecture map

System architecture

Make ownership and the internal policy loop visible before showing implementation detail.

Loading diagram...

The same system, grouped by ownership with the policy loop exposed inside Nava's verification boundary.

01User layer

OriginUser or dApp

Provides the instruction.

instruction ↓

02Builder layer

Execution ownerAgent or integrating builder

Builds, signs, and submits the exact action.

structured proposed action ↓

03Verification layer

Developer boundaryNava Service

Routes the request and returns the verdict.

Deterministic evaluatorNava Guardian

Resolves policy and evaluates checks.

versioned verdict ↑

04External venue

Approved path onlySupported protocol

Receives the signed action from the builder.

Sequence

Transaction lifecycle

Preserve the order of operations while separating the decision from the execution handoff.

Loading diagram...

A numbered sequence keeps the primary path readable, then separates the execution decision into explicit outcomes.

UserBuilderNavaVenue

User → BuilderInstruct the agent

Builder → BuilderBuild the structured action

Builder → Nava ServiceSubmit proposed action

Nava Service → Nava GuardianRequest policy verdict

Nava Guardian → Verdict storeEvaluate checks and record evidence

Nava Guardian → BuilderReturn versioned verdict

Builder → VenueSign and submit

State flow

Compact verdict lifecycle

Keep processing stages calm and reserve semantic color for the terminal decision.

Loading diagram...

The processing pipeline stays neutral; semantic color appears only where the terminal decision changes execution.

01InputProposed action

02ResolveActive policy

03EvaluateDeterministic checks

04Initial statePending verdict

Decision boundaryTerminal verdict

ApprovedExact action may continue

Reason codes and evidence remain attached.

RejectedExecution stays blocked

Reason codes and evidence explain the decision.

Payment sequence

Gateway payment lifecycle

Separate quote, verification, and settlement so the fee and merchant payments cannot be mistaken for one another.

Loading diagram...

Three phases separate authorization, policy verification, and settlement so the two independent payments cannot be confused.

Payer + resourceQuote and authorize

Request protected resource
Return merchant and optional fee requirements
Sign independent authorization(s)

Facilitator + GuardianVerify and decide

Verify exact x402 payment and quote binding
Evaluate merchant payment against policy
Return terminal outcome or unavailable

Resource + BaseSettle or fail closed

ApprovedMerchant settlement

Consume approval, settle once, return 200.

Rejected / timeout / errorDo not settle merchant payment

Return 402 or a fail-closed error.

System decisions

Brand comes from structure, not decoration.

Readable first16px labels, shorter copy, generous node spacing.
Ownership is visibleBuilder and Guardian steps live in explicit lanes.
One accentNava red identifies product-owned steps; status colors remain semantic.
Responsive by designThe numbered flow stacks in order on narrow screens.

Diagram system comparison

Default Mermaid output

Policy verdict boundary

Policy verdict boundary

System architecture

Default Mermaid output

Layered system architecture

Layered system architecture

Transaction lifecycle

Default Mermaid output

Transaction lifecycle

Transaction lifecycle

Compact verdict lifecycle

Default Mermaid output

Compact verdict lifecycle

Compact verdict lifecycle

Gateway payment lifecycle

Default Mermaid output

Gateway payment lifecycle

Gateway payment lifecycle

Brand comes from structure, not decoration.