There are two allocation levels
The first level is cross-asset capital routing: where capital belongs at all. The second level exists only inside an authorized crypto sleeve and determines how crypto risk is distributed across Bluechip, Growth, Speculative, and Cash buckets.
Separating those levels prevents an attractive token or sector from manufacturing its own upstream capital permission.
Portfolio destinations are broader than crypto
Cash preserves optionality. Gold and Silver can become defensive or relative-strength destinations. Equities can become an eligible risk sleeve. Crypto can receive capital when its own evidence and upstream Authority agree.
Treasury is different: M.A.I.C. reads Treasury and rates as macro evidence, but Treasury is not a current portfolio destination.
Crypto buckets are downstream construction
Bluechip, Growth, and Speculative describe the internal shape of authorized crypto exposure; they do not define the entire portfolio universe. Within that route, PAS selects identities under the active bucket rules and frozen-basket discipline.
PAS never overrides Final Mode Authority. It answers which assets qualify after capital permission already exists.
Why exact weights and identities stay protected
Exact cross-asset weights, bucket weights, PAS rankings, selected identities, rejected candidates, and route parameters are executable intelligence. Public surfaces therefore show architecture, state, and broad consequence rather than the protected implementation.
Historical and OOS evidence can still be audited at the model-portfolio level without publishing the route law itself.
Common questions
How does M.A.I.C. allocate across asset classes?
Final Mode Authority can route model capital among Cash, Gold, Silver, Equities, and Crypto according to governed conditions. Treasury remains observation-only.
Where do Bluechip, Growth, and Speculative buckets fit?
They are downstream construction inside the authorized crypto route. They are not the full multi-asset portfolio universe.
What does PAS do?
Protected Asset Selection chooses asset identities only inside Authority-approved buckets. It cannot create upstream capital permission.
This education page explains the concept. M.A.I.C. public state shows the current posture, while exact weights and token-level routes stay protected.