Methodology

How we convert Oracle signals into treasury operations.

Signal Flow

Oracle/King
On-chain analysis
↓
Posture Event
Regime + Stance + Confidence
↓
Policy Engine
Rule evaluation
↓
Trade Intent
Human approval required
↓
Ledger
Immutable audit trail

Market Regimes

GOLD

Strong bull market conditions

High conviction, favorable for accumulation

SILVER

Moderate bull conditions

Good but not exceptional signals

BRONZE

Neutral/unclear conditions

Mixed signals, caution advised

IRON

Bear market conditions

Defensive posture recommended

VOID

Extreme uncertainty/crisis

No reliable signal, maximum caution

Position Stances

ACCUMULATE

Favorable conditions for building position

HOLD

Maintain current position, no action

DISTRIBUTE

Consider taking profits or reducing exposure

DEFENSIVE

Risk reduction recommended

Policy Engine

The policy engine evaluates incoming posture against predefined rules. Each rule specifies:

  • •Trigger conditions (regime, stance, confidence thresholds)
  • •Allowed actions (BUY, SELL, or HOLD)
  • •Maximum trade size (% of portfolio)
  • •Cooldown period between trades

Rules are evaluated in priority order. Matching rules generate trade intents that must be approved by authorized personnel before execution.

Audit Trail

Every operation is recorded in an immutable audit log with SHA-256 hash chaining:

  • ✓Posture events from Oracle
  • ✓Trade intents generated
  • ✓Approval/rejection decisions
  • ✓Ledger entries with cryptographic verification
  • ✓Policy rule changes