Inspect one decision from context to evidence
Begin with source-published state rather than searching for a bullish indicator. These four actions form a complete first-use workflow; absent evidence must remain absent.
- Confirm the context. Open Phase 01; read LIVE versus archived, active Operating Path, publication time, Final Authority and access status.
- Challenge the reading. Compare Capital Climate with Survivability. Relative leadership and risk evidence do not independently authorize capital.
- Trace the consequence. Only after reading Final Authority, inspect Phase 04 planning and Phase 05 identity. Research and candidate ranking do not become trades.
- Verify in time. Use Scenario for conditional alternatives and Decision Chronicle for what was recorded; examine separate performance evidence without conflating LIVE, OOS and frozen forward.
Start with authorization, not indicators
M.A.I.C. is a crypto-native capital operating environment. Read context → Final Authority → consequences → constraints → recorded evidence. Analytical evidence may explain a market condition, but it does not automatically grant capital permission.
Favorable evidence can exist while deployment remains constrained, denied, or unchanged.
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.
Select a stage to inspect its operating meaning and original Terminal source.
01UnderstandIndependent evidence
Read market structure and risk as separate evidence streams. Their agreement can support a reading, but no number of positive observations can authorize deployment.
Inspect original evidence ↗02AuthorizeFinal capital permission
Governance resolves competing evidence and continuity. Final Authority alone determines whether model-reference capital risk can expand, remain bounded, or be withheld.
Inspect original evidence ↗03AllocatePortfolio roles, not tickers
An authorized mandate is expressed across Cash, Bluechip, Growth and Speculative roles. The map does not expose exact weights or convert a role into an asset.
Inspect original evidence ↗04SelectPAS identity qualifies downstream
Eligible identities are qualified inside the authorized buckets. Independent discovery cannot increase the upstream capital limit or replace effective PAS selection.
Inspect original evidence ↗05ProtectThreat is not execution
Survivability and scenario evidence challenge the route. A warning or a hypothetical hedge remains analytical until governed permission is published; external execution stays outside M.A.I.C.
Inspect original evidence ↗06VerifyRecorded decision at its date
Compare an earlier decision with its own available sources and later observations. Do not borrow current data to rewrite historical permissions or mix OOS with live-forward evidence.
Inspect original evidence ↗Three Operating Paths: separate sources and responsibilities
OBSERVATION, GOVERNANCE and AUTHORITY are not three votes on one trade. Compare the active source, confirmation and entitlement, never assume permission from the loudest signal.
| Path | Question | Boundary |
|---|---|---|
| OBSERVATION | What does Observation research show? | Access-gated research, not Spot permission or a trading instruction |
| GOVERNANCE | What does shield-aware BTC-first spot governance support? | Weekly governance is not Final Authority |
| AUTHORITY | What multi-asset spot exposure is finally permitted? | Model-reference permission, not an external order |
Workflow investigates seven specialist questions. Authorized Supervision examines the same environment through distinct COMMAND, SYSTEM and EVIDENCE perspectives without issuing a second Authority.
Access classes expand visibility and interaction rights, not model Authority
Class 01 observes public state; Class 02 inspects the confirmed model-reference portfolio; Class 03 adds earlier/deeper evidence and interactive rationale if the backend grants access. Class 04 retains the Class 03 market-intelligence ceiling for a future mandate scope. Subscription access never creates an independent market Authority.
| Access | Job | Available | Still protected / pending |
|---|---|---|---|
| Class 01 · Public Research | Observe the market | Published public posture, public evidence, anonymized topology, public historical evidence | Interactive portfolio/rationale controls |
| Class 02 · Tactical Portfolio | Govern the portfolio | Confirmed model-reference portfolio governance and published allocation buckets, risk review, scenario, deterministic rationale, bounded historical review | Earlier model inference, deep archive, interactive Operating Rationale |
| Class 03 · Allocation Intelligence | See deeper / earlier | Class 02 + earlier model inference, topology depth, deep reconstruction, projection memory, Operating Rationale, governed PAS asset qualification, reporting | Exact protected asset identities, rankings, and release entitlements remain server-authorized; Intelligence Relay activation still requires real identity and persistence |
| Class 04 · Institutional Mandate | Govern a mandate | Same market-intelligence ceiling as Class 03 | Mandate scope does not increase the market-intelligence ceiling |
Evidence discipline: 4H confirmed evidence
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.
A four-hour evidence boundary, weekly Governance and confirmed Final Mode Authority are distinct clocks and authorities. Final Authority follows its own publication and release status. Never infer a new capital permission from a 4H refresh.
Seven Terminal phases
Each phase answers one governance question. Navigation never expands authority.
| Phase | Surface | Governance question | Interpretation boundary |
|---|---|---|---|
| 01 | Operational Posture | What can the portfolio do now? | Posture is the primary governed state. |
| 02 | Capital Climate | Where does relative leadership and risk appetite stand? | Relative leadership is not measured capital flow and cannot open a route. |
| 03 | Survivability Corridor | What can hurt the portfolio? | Risk boundaries can constrain otherwise favorable evidence. |
| 04 | Exposure Geometry Lab | Which published capital route can planning research examine? | PLANNING ≠ AUTHORIZATION. Server-owned geometry and stress research do not open a new route or execute deployment. |
| 05 | Topology Governance | Which candidates warrant investigation after permission? | RANKING ≠ PERMISSION. Candidate evidence is not automatic bucket membership. |
| 06 | Scenario Governance | What if the market moves differently? | SCENARIO ≠ AUTHORIZATION. Probability is supporting evidence. |
| 07 | Temporal Decision Chronicle | What was recorded and can be verified? | REPLAY ≠ LIVE AUTHORIZATION. |
Portfolio roles and downstream identity
Phases 04 and 05 answer different questions: what role may be funded, and which asset can qualify inside that role? Neither research view can create new Final Authority.
Inspect what each portfolio sleeve means before asking which asset can fill it.
01CASHReserve capacity
Cash is a governed role for retained capacity. No displayed role is an instruction to transfer funds or to assume all reserves are risk-free.
Open source phase ↗02BLUECHIPCore liquidity
Bluechip defines the core role; its authorized effective identity can change across eligible asset categories. Bitcoin is not a permanent synonym for Bluechip.
Open source phase ↗03GROWTHQualified expansion
Growth describes a permitted risk role, not a promise of return. An attractive candidate does not add risk capacity independently.
Open source phase ↗04SPECULATIVEBounded optionality
Speculative research is distinct from an effective authorized asset. Optional discoveries cannot replace a protected PAS identity.
Open source phase ↗Canonical directive semantics
Signal color is a canonical state cue. The operational meaning of the directive is more important than the color itself.
This is a four-state interpretation guide, not a live selector or a portfolio simulator.
01STANDBYNo new deployment
The model withholds new deployment. Existing published portfolio structure may remain visible; that is not an automatic liquidation signal.
Inspect actual published Authority ↗02OFFENSEGoverned risk expansion
Broader deployment can be permitted within eligible buckets when Final Authority publishes this mandate. It does not make every research candidate eligible.
Inspect actual published Authority ↗03CORESelective core exposure
Core/Bluechip priority is governed by the active multi-asset route. The role is not always synonymous with a specific instrument.
Inspect actual published Authority ↗04DEFENSEProtect capital
Higher-beta risk is constrained, with defensive eligible roles and cash prioritized according to canonical Authority—not a universal instruction to sell everything.
Inspect actual published Authority ↗| Directive | Canonical color | Operational meaning |
|---|---|---|
| OFFENSE | Blue | Broad governed deployment is open across portfolio-eligible sleeves; downstream crypto qualification expands only when the crypto route is authorized. |
| CORE | Green | Core/bluechip exposure is prioritized under the active multi-asset route; the effective identity may be Bitcoin or defensive metals according to governed relative leadership. |
| STANDBY | Yellow | No new deployment. Existing governed portfolio structure may remain visible; this is not automatic liquidation. |
| DEFENSE | Red | Higher-beta risk is reduced and capital is routed toward defensive eligible sleeves and cash under the active Authority state. |
| DEGRADED / UNAVAILABLE | Grey | Normal state authority is constrained because evidence is incomplete or unavailable. |
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
Inspect the selected epoch's actual publication, Authority, source record and later observed outcomes. Historical reconstruction, frozen projection and present LIVE state are separate tracks.
Read this timeline as three evidence states, not as simulated prices or the actual date of an event.
01Recorded decisionPoint-in-time Authority
The chosen archived epoch identifies the source, state, portfolio context and permission that were available at that time. Selecting a historic date never authorizes today's capital.
Inspect recorded source ↗02Frozen projectionOriginal expectation and time
Where a canonical frozen projection is published, inspect its original range, timestamp, source and uncertainty. Do not move the frozen region when later prices are known.
Inspect recorded source ↗03Later observationOutcomes without refitting
Compare later source-published observations against the frozen record when both exist. Missing outcomes remain missing: no interpolated price path, backfilled event or retrospective authorization.
Inspect recorded source ↗| Evidence | What to verify |
|---|---|
| Recorded epoch | Dated source and decision, without borrowing current data |
| Frozen projection | Originally published range, freeze time and uncertainty; not a target or trade |
| Later observation | Recorded outcome, without revising the earlier projection after the fact |
Internal state-transition recipes are not public evidence. Inspect Phase 07 source ↗
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.
Command palette and keyboard-native operation
Ctrl/Cmd+K opens one palette with three different jobs: > selects local navigation without a backend request; / requests server-authorized evidence; a plain-language question requests Operating Rationale only when permitted. A navigation alias is not a server command result.
The same palette does not turn a local navigation into an evidence request or a rationale into Authority.
01NAVIGATIONLocal navigation
Opens an existing eligible phase or view. Local compatibility aliases such as /posture also route without returning server evidence.
Inspect Terminal access boundary ↗02EVIDENCEBackend-authorized evidence
Requests an existing source-owned command. Requires the current published command entitlement and LIVE context; it is not a universal free-form analytics engine.
Inspect Terminal access boundary ↗03RATIONALEOperating Rationale
A plain-language question asks for a bounded explanation when authorized. It may discuss evidence and constraints but cannot issue new capital permission.
Inspect Terminal access boundary ↗Essential keyboard controls
| Key | Operation |
|---|---|
| Ctrl/Cmd+K; Ctrl/Cmd+Shift+K | Open palette; toggle optional Keyboard Mode |
| 1–7; O/G/A; W/V | Phases; Observation/Governance/Authority; Workflow/Supervision. Character keys require Keyboard Mode and access |
| B/I; C/S/E; Alt+1/2/3 | Baseline/Inference; Supervision COMMAND/SYSTEM/EVIDENCE where eligible |
| R; L; ? or /; Ctrl+M | Authorized Rationale; language; help; Survivability review |
| F6 / Shift+F6; arrows; Enter/Escape | Eligible workspace regions; local spatial focus; enter/exit instrument controls |
Source-owned command grammar
| Kind | Actual examples | Boundary |
|---|---|---|
| Local navigation | > Phase 02; /posture; /load-archive; /topology --mask; /live | Routes to a view; no model calculation or entitlement upgrade |
| Governed evidence | /posture --compare; /risk --boundaries; /risk --tail-event; /topology --divergence; /topology --assets | Runs only if the LIVE backend command contract permits; data may be withheld |
| Operating Rationale | Plain-language question | Bounded explanation of published evidence; never another Authority |
Current server access status—not a static minimum-class table—determines whether a command can execute.
Operating Path, Workspace and Analytical Focus
OPERATING PATH changes which independent source perspective you read. WORKSPACE chooses specialist Workflow or eligible Supervision. ANALYTICAL FOCUS applies inside Supervision: COMMAND explains capital consequence; SYSTEM shows state relationships; EVIDENCE inspects support, disagreement and provenance.
Workflow keeps EVIDENCE as its fixed focus. None of these controls changes source publication, Authority, identity eligibility or the server-granted access class.
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.
Diagnose the state before retrying
| Symptom | Inspect | Correct response |
|---|---|---|
| No new posture | LIVE/replay and confirmed publication time | 4H refresh alone is not new Authority |
| Protected or disabled | Backend entitlement and current phase/source | A stored key or visible control is not granted access |
| Missing/stale evidence | Native source status and as-of timestamp | Do not substitute current LIVE or artificial zeros |
| Replay differs from LIVE | Selected epoch, historic marker and decision | Inspect both independently; return explicitly to LIVE |
| Command denied | > versus / versus text; backend command status | Read denial; a navigation success is not a server result |
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.
