M.A.I.C.Alpha Crypto Intelligence

DOCUMENTATION · TERMINAL OPERATION & GOVERNANCE SEMANTICS

M.A.I.C. Terminal User Guide

How to use each Terminal surface, read its controls, understand evidence freshness, and distinguish observation, projection, ranking, replay, and structural allocation from actual capital authorization.

DOC VERSION · 21 AUG 20264H EVIDENCE · WEEKLY GOVERNANCEPUBLIC WHY / PROTECTED HOW

Start with authorization, not indicators

M.A.I.C. is a crypto-native capital operating environment. The safest reading order is posture → route → risk → authorization → evidence/replay. Analytical evidence may explain a market condition, but it does not automatically grant capital permission.

OBSERVATION ≠ AUTHORIZATION
Favorable evidence can exist while deployment remains constrained, denied, or unchanged.
STRUCTURAL ALLOCATION ≠ ACTION AUTHORIZATION
Portfolio structure can remain visible under STANDBY. A displayed allocation envelope is not an instruction to create a new position.

How decision authority flows

M.A.I.C. is not reducible to one score, one predictive model, or a simple if-then rule chain. Distinct analytical surfaces observe different market dimensions; authority is determined only after conflict, prior state, and governance constraints are resolved.

OBSERVATION SURFACES ↓ CONFLICT ARBITRATION competing evidence · prior state · constraints ↓ STATEFUL GOVERNANCE confirmation · permission · boundary ↓ CAPITAL AUTHORIZATION wait · constrain · expand · rotate ↓ HISTORICAL EVIDENCE / REPLAY
No simple-majority authorization. A larger number of favorable indicators does not by itself open a portfolio route.

Access classes expand authority, not merely panel count

Class 01 observes public state. Class 02 governs the confirmed portfolio route. Class 03 opens earlier/deeper protected intelligence and interactive rationale. Class 04 uses the same intelligence ceiling as Class 03 for the future institutional mandate layer.

AccessJobAvailableStill protected / pending
Class 01 · Public ResearchObserve the marketPublic weekly-confirmed posture, public evidence, masked topology, public historical evidenceInteractive portfolio/rationale controls
Class 02 · Tactical PortfolioGovern the portfolioConfirmed weekly portfolio governance, BTC-first allocation buckets, risk review, scenario, deterministic rationale, bounded historical reviewProtected inference, deep archive, interactive Operating Rationale
Class 03 · Allocation IntelligenceSee deeper / earlierClass 02 + protected inference, topology depth, deep reconstruction, projection memory, Operating Rationale, reportingSystem asset classification appears only when supplied by the active governed model
Class 04 · Institutional MandateGovern a mandateSame market-intelligence ceiling as Class 03Mandate scope does not increase the market-intelligence ceiling

Evidence discipline: 4H confirmed evidence

EVIDENCE DISCIPLINE4H CONFIRMED EVIDENCENext governed boundary → shown by the live Terminal

Source telemetry may move at its native cadence. M.A.I.C. synchronizes decision evidence on four-hour boundaries to suppress intraday noise and unnecessary posture churn. This is a capital operating environment, not an HFT engine.

The public directive is a separate weekly-confirmed governance state. A fresh 4H evidence boundary can update what the system observes without automatically changing what the public portfolio is authorized to do.

4H EVIDENCE ≠ WEEKLY PUBLIC AUTHORIZATION

Seven Terminal phases

Each phase answers one governance question. Navigation never expands authority.

PhaseSurfaceGovernance questionInterpretation boundary
01Operational PostureWhat can the portfolio do now?Posture is the primary governed state.
02Liquidity GovernanceWhere is money moving?Flow evidence can support or challenge a route; it does not open one by itself.
03Survivability CorridorWhat can hurt the portfolio?Risk boundaries can constrain otherwise favorable evidence.
04Exposure AuthorizationWhat can actually be deployed?STRUCTURAL ALLOCATION ≠ ACTION AUTHORIZATION.
05Topology GovernanceWhat deserves capital?RANKING ≠ PERMISSION. Candidate evidence is not automatic bucket membership.
06Scenario GovernanceWhat if the market moves differently?SCENARIO ≠ AUTHORIZATION. Probability is supporting evidence.
07Governance EvidenceDid the system behave as intended?REPLAY ≠ LIVE AUTHORIZATION.

Canonical directive semantics

Signal color is a canonical state cue. The operational meaning of the directive is more important than the color itself.

DirectiveCanonical colorOperational meaning
OFFENSEBlueBroad crypto-risk deployment is open within governed model constraints.
COREGreenBTC-first / bluechip model exposure remains prioritized while broader risk stays controlled.
STANDBYYellowNo new deployment. Existing model structure may remain visible; this is not automatic liquidation.
DEFENSERedHigher-beta risk-reduction state: model exposure compresses toward stronger bluechip/cash structure.
DEGRADED / UNAVAILABLEGreyNormal state authority is constrained because evidence is incomplete or unavailable.
PUBLIC STATE LABELS ARE PRESENTATION-ONLY.
OFFENSE, CORE, STANDBY, and DEFENSE are human-facing state names. They do not change backend machine contracts, historical state logic, or API semantics.

Historical Market Replay & Bottom Projection

Historical Market Replay reconstructs the governed context of a selected epoch. It must not redefine the live directive or leak a replay-specific annotation into the current public posture.

STANDBY remains the yellow public state.
Inside Historical Market Replay only, the first full STANDBY week immediately after a governed DEFENSE may retain a red epoch transition marker so the replay can preserve the same top-cycle / bottom-projection episode. The public state remains STANDBY and its operational meaning remains “no new deployment.”

Bottom Projection is therefore interpreted as an episode state machine, not as a color rule attached only to ROTATE. The interpreter reads every canonical posture to determine whether an episode is opened, observed, cancelled, or frozen.

Observed postureReplay / projection interpretation
DEFENSEOpens the candidate top-cycle / bottom-projection episode.
STANDBYPreserves the no-new-deployment state; the first post-DEFENSE replay epoch may keep red lineage solely to show episode continuity.
COREIf it appears before projection freeze, the pending episode is cancelled as an invalid / false top candidate.
OFFENSEIf it appears before projection freeze, the pending episode is cancelled as an invalid / false top candidate.

Projection freeze remains a governed weekly observation condition. The projected range is probabilistic downside evidence, not a guaranteed target, not a live sell order, and not a replacement for the current posture.

Historical Review vs Temporal Posture Memory

Historical Governance Review is bounded evidence review for Class 02+. Temporal Posture Memory is Class 03+ arbitrary-epoch selection, deep reconstruction, and live/archive restore. Lower classes may discover the capability without receiving its controls.

Decision Rationale vs Operating Rationale

Class 02 receives deterministic Decision Rationale derived from confirmed state. Class 03 receives Operating Rationale: ASK THE SYSTEM WHY. It may interrogate evidence, conflict, uncertainty, history, constraints, and change conditions while remaining tethered to the governed decision.

Rationale may explain canonical authority; it may not manufacture a second decision engine.

Routing Access, command palette, and Keyboard Mode

Commands and shortcuts accelerate navigation and workflow. They delegate to canonical controls; there is no shortcut around access, posture, survivability, or routing denial.

Keyboard shortcuts

KeyRoute / action
1-7Phase navigation
O / GObservation / Governance lens
B / IBaseline / Inference visibility
W / VWorkflow / Supervision
C / S / ECommand / System / Evidence depth
ROperating Rationale (only when authorized)
LEnglish / Indonesia
? or /Shortcut reference
Ctrl+KCommand Search / Routing Access
Ctrl+MSurvivability Review
Ctrl+Shift+KKeyboard Mode on/off

Command Search routes

CommandMinimum accessDestination
/postureClass 01Operational Posture
/riskClass 02Survivability Corridor
/allocationClass 02Exposure Authorization
/deployClass 02Confirmed Deployment Review
/topologyClass 03Topology Governance / protected depth
/auditClass 02Historical Governance Review
/archiveClass 03Temporal Posture Memory reconstruction
/supervisionClass 03Allocator Oversight Surface
/reportClass 03Governance report
/rationaleClass 03Operating Rationale

Review Lens, Workspace, and Evidence Depth

Review Lens changes observation/governance framing; Workflow vs Supervision changes operating surface; Command/System/Evidence changes disclosure depth. These are presentation controls, not decision authority.

Evidence freshness and degraded state

The Terminal distinguishes fresh governed evidence from stale, incomplete, or unavailable telemetry. When source evidence cannot support normal confidence, the surface should say so explicitly rather than silently extending a prior state.

Use the displayed evidence boundary and next governed refresh as the primary freshness reference. A degraded label describes evidence quality; it does not create a new market directive.

Mobile controls

Phones use one persistent rail: POSTURE / LIQUIDITY / RISK / MORE. MORE routes Exposure, Topology, Scenario, Historical Review, Memory, Commands, and Evidence according to class. CONTROLS and WHY are contextual utilities. Wide analytical canvases pan or scroll inside bounded containers rather than overflowing the document.

Security, privacy, and authority boundary

Protected access is enforced by the authorized service boundary, not by what happens to be visible in the browser interface. Presentation controls cannot manufacture a higher access class. Physical execution, custody, brokerage, and capital transfer remain outside the M.A.I.C. Terminal.

Nothing authority-sensitive should depend on frontend secrecy. Public documentation explains behavior and boundaries without publishing protected implementation.

Troubleshooting

If state appears stale, check the evidence boundary, next governed refresh, and degraded status before forcing reload. If a control is visible but unavailable, read its access or capability label: discoverability does not guarantee interaction authority. If replay appears different from live state, confirm whether you are viewing an epoch annotation or the current governed posture.

Short glossary

CONFIRMED = canonical weekly governance state. EARLY / INFERENCE = protected provisional evidence. GOVERNED = state after constraints and authority are applied. OBSERVATION = evidence that does not automatically become permission. AUTHORIZATION = capital consequence allowed by the system. STRUCTURAL ALLOCATION = portfolio envelope/reference, not automatic deployment. RANKING = candidate ordering, not portfolio permission. SCENARIO = probabilistic supporting evidence, not authorization. REPLAY = historical context, not live authority. DEGRADATION = evidence is not fresh or complete enough for normal confidence.