Visual style test

Use this page to verify that the documentation feels consistent with the Coda Network website across typography, color, surfaces, borders, and interactive components. Dark theme enabled

Typography

Institutional decision infrastructure

Coda Network provides the decision layer for digital asset transactions. It brings wallet context, institutional intelligence, and policy together before an action is approved. This paragraph tests regular body copy, strong emphasis, italic emphasis, inline links, and inline code.

Every transaction should be explainable, enforceable, and aligned with institutional policy.

The visual hierarchy should remain clear across:

Primary headings and section titles
Standard paragraphs and supporting text
Inline links and emphasized content
Ordered and unordered lists
Inline code and quoted content

Collect the transaction context.
Evaluate institutional policy.
Record the decision evidence.
Return an actionable outcome.

Brand palette

Primary

#1A66E5

Primary light

#4684EE

Primary dark

#1453C4

Canvas

#04070F

Surface

#0A0F1C

Primary text

#EEF2F9

Secondary text

#B9C4D6

Callouts

The following components test informational and semantic states.

Coda evaluates transaction context before funds are signed, credited, or otherwise acted upon.

Decision evidence should include the evaluated policy version and the institutional context used at decision time.

Use deterministic policy identifiers so decisions can be traced across systems.

The transaction passed all configured authorization requirements and may proceed.

The transaction requires additional institutional review before execution.

The transaction violates an enforced policy and must not proceed.

This custom callout uses the Coda primary brand color.

Status badges

These badges test compact brand and semantic indicators. Policy evaluated ALLOW REVIEW DENY Pending

Badge variations

Brand Approved Requires review Blocked

Cards and surfaces

Decision engine

Evaluate wallet context, institutional intelligence, and policy before authorizing an action.

Policy controls

Configure deterministic controls that reflect institutional requirements.

Decision evidence

Record the policy version, evaluated signals, and final outcome for every decision.

Developer integration

Integrate Coda into existing transaction and signing workflows.

Coda Network

Explore the institutional decision layer for digital asset transactions.

Decision workflow

Submit transaction context

Provide the wallet, asset, amount, destination, and institutional customer context.

Evaluate intelligence

Coda collects configured intelligence from institutional and external systems.

Apply policy

The decision engine evaluates the transaction against the active institutional policy.

Return a decision

Coda returns ALLOW, REVIEW, or DENY with structured decision evidence.

Decision outcomes

ALLOW
REVIEW
DENY

The transaction satisfies all configured authorization requirements and may proceed.

ALLOW response

{
  "decision": "ALLOW",
  "policyVersion": "12",
  "evidenceRecorded": true
}

The transaction requires additional institutional approval or investigation.

REVIEW response

{
  "decision": "REVIEW",
  "policyVersion": "12",
  "reason": "Manual approval required"
}

The transaction violates an enforced policy and must be blocked.

DENY response

{
  "decision": "DENY",
  "policyVersion": "12",
  "reason": "Destination policy violation"
}

Code examples

curl --request POST \
  --url https://api.codanetwork.io/v1/decisions \
  --header "Authorization: Bearer $CODA_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "asset": "USDC",
    "amount": "1402887.50",
    "destination": "0x8f3a...d4f5"
  }'

const response = await fetch(
  "https://api.codanetwork.io/v1/decisions",
  {
    method: "POST",
    headers: {
      Authorization: `Bearer ${process.env.CODA_API_KEY}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      asset: "USDC",
      amount: "1402887.50",
      destination: "0x8f3a...d4f5",
    }),
  },
);

const decision = await response.json();

import os

import requests

response = requests.post(
    "https://api.codanetwork.io/v1/decisions",
    headers={
        "Authorization": f"Bearer {os.environ['CODA_API_KEY']}",
        "Content-Type": "application/json",
    },
    json={
        "asset": "USDC",
        "amount": "1402887.50",
        "destination": "0x8f3a...d4f5",
    },
)

decision = response.json()

Highlighted code

decision-handler.ts

type Decision = "ALLOW" | "REVIEW" | "DENY";

export function handleDecision(decision: Decision) {
  switch (decision) {
    case "ALLOW":
      return continueSigningWorkflow();
    case "REVIEW":
      return openInstitutionalReview();
    case "DENY":
      return blockTransaction();
  }
}

Decision path

Data table

Outcome	Meaning	Required action
`ALLOW`	All authorization requirements passed	Continue the transaction workflow
`REVIEW`	Additional approval is required	Hold the transaction for review
`DENY`	An enforced policy was violated	Block the transaction
`PENDING`	Evaluation is still in progress	Wait for the final decision

API fields

asset

string

required

The asset identifier used by the transaction, such as USDC.

amount

string

required

The transaction amount represented as a decimal string.

destination

string

required

The destination wallet address.

decision

ALLOW | REVIEW | DENY

required

The authorization outcome returned by the decision engine.

policyVersion

string

required

The institutional policy version used during evaluation.

evidenceRecorded

boolean

required

Indicates whether structured decision evidence was recorded.

Accordions

What should an ALLOW decision look like?

ALLOW should use a controlled success treatment. It must remain visually distinct from the primary Coda brand blue.

When should REVIEW be used?

REVIEW should indicate that the transaction is paused pending institutional approval or investigation.

What does DENY mean?

DENY represents an enforced block. It should use a clear danger treatment without overwhelming surrounding content.

How should decision evidence appear?

Evidence should use structured fields, readable code blocks, and restrained borders that match the dark institutional interface.

A should make every authorization outcome explainable.

Visual review checklist

The page background uses the deep Coda canvas color rather than pure black.
Primary links, active states, and navigation accents use Coda blue.
Cards use restrained borders and subtle surface separation.
Headings remain clear without appearing excessively bright.
Body text is readable but visually quieter than headings.
Inline code remains legible against the surrounding surface.
Focus, hover, and selected states are visible.
Mobile layouts preserve spacing and hierarchy.
ALLOW, REVIEW, and DENY remain semantically distinguishable.

Getting Started

Typography

Institutional decision infrastructure

Brand palette

Callouts

Status badges

Badge variations

Cards and surfaces

Decision engine

Policy controls

Decision evidence

Developer integration

Coda Network

Decision workflow

Decision outcomes

Code examples

Highlighted code

Decision path

Data table

API fields

Accordions

Tooltip

Visual review checklist

​Typography

​Institutional decision infrastructure

​Brand palette

​Callouts

​Status badges

​Badge variations

​Cards and surfaces

Decision engine

Policy controls

Decision evidence

Developer integration

Coda Network

​Decision workflow

​Decision outcomes

​Code examples

​Highlighted code

​Decision path

​Data table

​API fields

​Accordions

​Tooltip

​Visual review checklist

Typography

Institutional decision infrastructure

Brand palette

Callouts

Status badges

Badge variations

Cards and surfaces

Decision workflow

Decision outcomes

Code examples

Highlighted code

Decision path

Data table

API fields

Accordions

Tooltip

Visual review checklist