CATEGORY EVIDENCE · METHOD V1.1
How the “world’s first” category claim is tested.
M.A.I.C.’s category-precedence claim is evaluated against a versioned full-architecture standard. Shared vocabulary or isolated capabilities do not establish category equivalence. A qualifying earlier architecture supported by dated evidence updates the public record.
CLAIM RETAINEDPRECEDENCE REVIEW ACTIVEMETHOD · V1.1REVISED · 23 AUG 2026
CATEGORY DEFINITION
One category. Eight mandatory conditions.
The claim is not that M.A.I.C. invented risk management, market regimes, allocation, governance, policy engines, backtesting, crypto analytics, or non-custodial software. A predecessor qualifies only when dated public evidence supports the combined category architecture below.
Crypto or digital-asset capital is a primary operating domain, not incidental coverage.
Distinct analytical components produce separately addressable interpretations that may remain in disagreement. Inputs that are obligatorily fused into one posterior estimate do not, by themselves, satisfy this criterion.
Analytical outputs: scores, expected returns, rankings, target weights, or recommendations do not themselves constitute portfolio authorization. A logically distinct governance state decides whether evidence may change portfolio risk. Non-execution alone is insufficient.
Conflict remains governance-relevant and can change permission: allow, constrain, delay, or deny. Averaging, Bayesian blending, shrinkage, or score aggregation alone does not satisfy C4 unless conflict separately changes authority.
Previous authorization/posture, constraints, confirmation, or evidence quality materially participate in the next permission state. Current holdings used only for turnover, transaction cost, or rebalance distance are insufficient.
A distinct permission decision occurs before a target allocation or exposure change is treated as governed. Optimizer weights, a BUY recommendation, or “rebalance required” are not automatically capital authorization.
Asset attractiveness cannot create its own upstream portfolio-risk permission. An otherwise attractive asset can receive no capital because the upstream capital or crypto-risk state does not permit deployment.
The governed object is portfolio-risk permission from market evidence, not wallet transfer approval, custody, compliance, surveillance, or execution. The permission binds M.A.I.C.'s governed decision state and routes; it does not claim physical control over an external user's wallet, exchange, custodian, or independent action.
CONSTITUTIVE RATIONALEWHY C1-C8 EXIST · METHOD V1.1 UNCHANGEDOpen category logic
This rationale does not add a criterion or revise Method V1.1. It explains why the existing boundaries are functionally necessary to the category rather than included merely because they are rare.
Without a crypto-native operating domain and the same market-evidence → portfolio-risk governed object, the category can collapse into generic finance, custody, transaction policy, compliance, surveillance, or execution.
C2 matters because evidence may remain different. C4 matters because disagreement must be capable of changing permission. Without C4, multiple views can still be only inputs to aggregation, blending, or optimization.
C3 creates the logical boundary between analytical output and capital authority. C6 requires that permission be resolved before an allocation or exposure change is treated as governed; otherwise the optimizer or recommendation is already the decision.
C5 prevents each decision from becoming a stateless reset. C7 prevents asset attractiveness from creating its own portfolio-risk permission. Without C7, the architecture collapses toward ranking, screening, or asset-first optimization.
CONSTITUTIVE INVARIANT · METHOD V1.1 UNCHANGED
Nothing downstream can manufacture its own authority.
This is a compact expression of C3, C6, and C7, not a ninth criterion. Analytical evidence may inform governance, but rankings, scenarios, target weights, and attractive assets cannot promote themselves into upstream capital permission.
Decision support ≠ capital permission. A system can be sophisticated, multi-agent, stateful, or portfolio-aware and still fail this boundary if downstream analysis already constitutes the portfolio decision.
PRECEDENCE STANDARD
Feature overlap is evidence of overlap, not automatic equivalence.
A confirmed earlier category match requires public evidence for every mandatory criterion C1-C8. One or several overlapping capabilities are insufficient.
The source must be dated and publicly verifiable before the relevant M.A.I.C. public-provenance anchor. Undated memory, private claims, or later reconstructions do not silently become earlier publication.
Authorization must concern portfolio-risk permission derived from market evidence. Transaction approval, custody policy, compliance, surveillance, or execution govern different objects.
C1-C8 must be evidenced within the same identifiable decision or control architecture and relevant version. External data, libraries, infrastructure, or services do not disqualify an integrated architecture. What is not allowed is stitching unrelated systems together only to assemble the required criteria.
A criterion counts only when the earlier architecture is documented as actually containing that behavior. A capability that could hypothetically be added later is not evidence that the predecessor already had it.
Commercial products, open-source software, academic implementations, research systems, and institutional frameworks are all eligible. UI, pricing, company status, or commercial launch are not required if one earlier documented architecture satisfies C1-C8.
ADJACENT CATEGORYPARTIAL OVERLAPPOTENTIAL MATCHCONFIRMED EARLIER MATCHINSUFFICIENT EVIDENCE
M.A.I.C. IMPLEMENTATION DEPTH · C5 EXAMPLE
Evidence can change before authority changes.
M.A.I.C. separates provisional Terminal evidence from the weekly-confirmed public governance state. The cadence is an implementation choice, not a requirement that every predecessor use the same timeframe; the category requirement remains governance-state dependence.
Terminal-only state can change before the confirmation boundary.
New evidence must pass the governed confirmation contract.
The confirmed state remains authoritative until the next governed transition.
EARLY ≠ CONFIRMED PUBLIC STATEImplementation depth, not an additional category criterion.
CURRENT PRECEDENCE RECORD
Versioned finding under Method V1.1.
REVIEW RESULT · METHOD V1.1No reviewed predecessor has yet been confirmed to satisfy clarified C1-C8 as one earlier public architecture.
The record is maintained under Method V1.1 and rechecked when new dated evidence materially affects a criterion.
A qualifying earlier system changes the record.
METHOD DISCIPLINE · PRECEDENCE ≠ IMPLEMENTATION INFERENCE
Frontend illustration does not establish historical precedence.
C1-C8 is evaluated against dated, inspectable source records. Illustrative product diagrams explain the architecture but do not change the category standard or substitute for chronology evidence.
EVIDENCE DISCIPLINEDATED SOURCES · VERSIONED METHOD · ADVERSE EVIDENCE RETAINED
Protected thresholds, arbitration parameters, and routing implementation can remain undisclosed while public category evidence stays inspectable at the claim boundary.
CHRONOLOGY RULE
Artifact creation is not silently treated as public publication.
When a dated artifact and its later public source both exist, the record preserves both timestamps. The precedence analysis must state which date standard is being used and why.
Useful provenance, but not automatically proof that the market could publicly inspect it on that date.
Used for public-precedence comparisons unless an independently verifiable earlier publication is established.
CATEGORY CHALLENGE PROTOCOL
A counterexample is welcome when it is testable.
A challenge should make the earlier system identifiable and allow the same standard to be applied in both directions.
SUBMISSION ADMISSIBILITYCLAIM ≠ EVIDENCE · PROTOCOL REV AOpen evidence format
A challenger description is not evidence of architecture behavior. Each mandatory criterion requires directly inspectable support from the identified predecessor.
Admissibility is procedural, not a new category criterion. Method V1.1 remains unchanged. Unsupported interpretation, hypothetical add-ons, or a challenger-written reconstruction do not substitute for source evidence.
Anti-goalpost rule: a materially equivalent earlier architecture triggers a versioned methodology review, not automatic rejection. Any clarification must be general, technology-neutral, public, and applied to M.A.I.C. and challengers alike. Single-architecture rule: separate frameworks cannot be stitched together into a synthetic predecessor.
Until a dedicated research mailbox is published, prefix a submission with CATEGORY EVIDENCE. Do not send private keys, passwords, or unrelated sensitive information.
VERSIONED METHOD
The standard cannot move silently.
Revised 2026-08-23V1.1 clarifies logical decision authority versus physical execution, independent evidence states versus fused optimizer inputs, authority-affecting conflict, governance-state dependence, and authorization before allocation. It also adds the Single Architecture, Native Evidence, and Form-Neutral Predecessor rules.
V1.0 · 2026-08-23 established C1-C8, chronology, evidence status, and the challenge protocol. V1.1 · 2026-08-23 followed adversarial review that exposed ambiguity between portfolio optimization and capital authorization. The revision clarifies semantics without excluding academic, open-source, research, institutional, or commercial predecessors.
Definition · C1-C8 · decision rule · status · challenge protocol · revision history.