{
  "checked": "2026-10-08",
  "site": {
    "code": "CSA",
    "name": "Crypto Signal Authority",
    "project": "cryptosignalauthority",
    "domain": "https://cryptosignalauthority.pages.dev",
    "theme": "crypto",
    "lede": "Crypto signal reviews, message-history checks and execution evidence. Compare the exact service, not its biggest screenshot.",
    "library": "articles/index.html",
    "dataset": "data/providers.jsonld",
    "scope": "Public-document research and educational exercises. No paid-room tracking, exchange connection or audited customer return is claimed.",
    "home": [
      [
        "Start with the tradeable object",
        "A message, a bot setting, a wallet transfer and a copied exchange order are different objects. Before comparing services, write down which one you will receive and which decisions remain yours. A beautifully documented alert still cannot establish the price at which your account would fill. A bot marketplace can supply useful automation without validating every seller on it."
      ],
      [
        "The record needs its missing rows",
        "Keep original calls, later amendments, expired entries, cancelled orders, losses and unresolved positions in the same ledger. A winning screenshot cannot supply that population. A hash can identify particular content; it does not reveal the calls that were never included. Treat coverage, publication timing and trading outcome as separate questions."
      ],
      [
        "Evidence before a subscription",
        "Begin with the message-history guide, inspect the permissions required by any automation and compare a gross move with realistic costs. The directory separates platform documentation from seller-specific results. It does not award an automatic winner or attach a precise scam percentage to an unmeasured market."
      ]
    ],
    "method": [
      [
        "Four separate evidence questions",
        "First establish who operates the exact service and where its terms live. Next identify the complete call population and revision policy. Then examine whether timestamps and outcomes can be reproduced. Finally compare those claims with the fills, fees and constraints of a particular subscriber account. Strong evidence for one question does not answer the others."
      ],
      [
        "What our assessments mean",
        "These are document-based buying assessments, not subscriptions secretly tested with real capital. The source link identifies the product description being discussed. Missing evidence in this review is not a finding that no evidence exists anywhere. No star score, sample of paying users or universal platform failure rate is inferred."
      ],
      [
        "Commercial and ownership boundary",
        "The owner describes the publication as legally independently owned. Commercial records have not been supplied for an independent audit of sponsorship or referral arrangements. Ordinary source links are not evidence of endorsement, and the presence of a provider in this directory is not approval to send it money or API credentials."
      ]
    ],
    "sources": [
      [
        "CFTC: virtual-currency pump-and-dump warning",
        "https://www.cftc.gov/LearnAndProtect/AdvisoriesAndArticles/beware_virtual_currency_pump_dump.html"
      ],
      [
        "OpenTimestamps: verification and upgrade",
        "https://opentimestamps.org/"
      ],
      [
        "Cryptohopper: paper trading product description",
        "https://www.cryptohopper.com/features/paper-trading"
      ]
    ],
    "tool": {
      "path": "tools/crypto-signal-outcome-ledger.html",
      "kind": "ledger",
      "title": "Crypto signal outcome ledger",
      "description": "Separate closed wins, closed losses and unresolved calls before reading a win-rate headline.",
      "fields": [
        [
          "wins",
          "Closed wins",
          12
        ],
        [
          "losses",
          "Closed losses",
          8
        ],
        [
          "open",
          "Unresolved calls",
          5
        ],
        [
          "cancelled",
          "Cancelled or expired calls",
          3
        ]
      ],
      "notes": [
        [
          "The denominator is a policy choice",
          "The closed-trade rate uses wins divided by wins plus losses. The all-resolved-event rate also includes cancelled or expired calls in its denominator and must not be advertised as the same metric. Unresolved calls are shown separately. These counts must be mutually exclusive; a cancellation after a genuine fill belongs in the execution ledger, not the never-filled bucket."
        ],
        [
          "What this count cannot measure",
          "Twenty tiny wins and one large loss can still lose money. This worksheet does not calculate expectancy, leverage, drawdown, costs or whether omitted calls exist. Its invented defaults explain denominators only. A complete publisher record must define scratches, partial exits and duplicated messages before entering counts."
        ]
      ]
    }
  },
  "guides": [
    {
      "path": "articles/crypto-signal-history-and-revision-audit.html",
      "title": "How to audit a crypto signal history",
      "description": "A practical ledger for original messages, amendments, cancellations and unresolved positions.",
      "sections": [
        [
          "Define a call before counting one",
          "Choose the unit of analysis before opening the performance dashboard. One idea might generate an entry message, three target updates and a final cancellation. Counting every profitable target as a different winning trade exaggerates activity unless the same rule is applied to losses and position size. Give the idea a persistent identifier and retain each message as a separate event attached to that identifier.\n\nRecord service name, channel identifier, instrument and contract, side, publication timestamp with timezone, entry condition and original risk instructions. An exchange perpetual and a spot token with a similar ticker are not interchangeable. Save the original content, not merely the most recent message displayed by the app."
        ],
        [
          "Preserve a revision timeline",
          "An amendment needs its own observed time, the field changed and the reason supplied. Do not overwrite the first entry. If a provider moves the stop after the market passes the original stop, the original policy and the amended policy are different experiments. A screenshot after the change cannot reconstruct what an earlier subscriber saw.\n\nFor a cancellation, record whether the entry condition had already become executable. A never-triggered limit is different from a filled position whose alert was later deleted. When the source does not let you establish that order, label the outcome indeterminate rather than choosing whichever interpretation produces the better result."
        ],
        [
          "Keep unresolved exposure visible",
          "An open call is neither a win nor a loss. Show it as unresolved with the last observation time and the outstanding exposure you can actually establish. If the publisher provides only closed-trade summaries, say that the open-position risk is unknown. A flat balance curve does not establish that account equity was flat during the period.\n\nFor a fictional batch with twelve wins, eight losses and five open calls, the closed-only win rate is 60%. That number says nothing about how the five open calls will resolve or their size. Add three never-filled cancellations and the event count changes, but a closed-trade rate should not silently change definition."
        ],
        [
          "Check completeness separately from timestamps",
          "A matching digest connects one document with one commitment. It cannot demonstrate that every call was committed or that the document reached subscribers before a move. For coverage, reconcile the channel event log, numbered call sequence, revision log and published outcome ledger. Missing identifiers require an explanation even when all the surviving receipts verify.\n\nOpenTimestamps distinguishes receipt creation from the later proof that can be verified against a Bitcoin block. Keep a pending calendar receipt labelled pending until the required attestation is available. Preserve the original file bytes because changing whitespace, encoding or field order can change the digest."
        ],
        [
          "Reconstruct an executable interpretation",
          "Separate publisher price, first available quote after receipt, your submitted order and any actual fill. A single candle may touch both stop and target without telling you which occurred first. Use finer observations when they exist; otherwise report the ambiguous case and a predeclared conservative treatment. Do not look ahead to select the favourable tick.\n\nInclude fees on both legs, spread, slippage, signed funding or borrowing costs when relevant and incomplete fills. A signal result in percent may use notional, margin or account equity as its base. Ask which one before comparing it with another service."
        ],
        [
          "Publish a small reproducible evidence package",
          "A useful package contains the event ledger, outcome policy, original messages or permitted excerpts, timestamp receipts, observation sources and a change log. Redact personal identifiers without redacting the fields required to reproduce the calculation. Record exactly which material you were allowed to inspect and the date it was available.\n\nDo not promote an educational reconstruction into a paid-account audit. The practical output is a list of resolved claims and remaining questions: complete population, immutable content, chronological delivery, execution assumptions and cash-account outcome. Each needs its own answer."
        ]
      ]
    },
    {
      "path": "articles/crypto-bot-permissions-and-emergency-stop.html",
      "title": "Crypto bot permissions and emergency-stop checklist",
      "description": "Review API scope, open orders, copied positions and revocation before connecting automation.",
      "sections": [
        [
          "Draw the custody and instruction map",
          "Write down where assets are held, who can place orders and which service stores the API credential. A marketplace seller, bot host and exchange may be three different parties. Check the current exchange documentation for permissions, product eligibility and regional restrictions rather than relying on an old tutorial.\n\nRead-only, trade-enabled and withdrawal-enabled credentials create different risks. A bot that can trade but cannot withdraw can still create severe losses through unwanted exposure. Minimum permissions reduce a particular risk; they do not make an automation strategy safe or profitable."
        ],
        [
          "Inspect the actual strategy configuration",
          "Save allowed symbols, direction rules, maximum concurrent positions, order sizes, leverage settings where applicable and the treatment of insufficient funds. Identify which settings are account-wide and which belong to one bot. A seller description of a cautious strategy does not establish that your current configuration matches it.\n\nCheck how the bot handles duplicate messages, delayed messages, price gaps, partial fills and disconnected exchange sessions. An alert that arrives twice should not automatically double exposure. Ask what happens when a cancellation arrives before the original entry event has been processed."
        ],
        [
          "Treat paper trading as a rehearsal",
          "Cryptohopper describes a paper-trading simulator. That documentation establishes the product category, not a return for any seller. Use simulation to rehearse your configuration, order lifecycle and emergency process. Keep simulated fills clearly distinct from exchange account fills.\n\nA rehearsal can reveal a unit error or a bot continuing after you thought it was paused. It cannot fully reproduce queue priority, market impact, outages or the emotional decisions made with real capital. Do not label a successful rehearsal a verified live strategy."
        ],
        [
          "Plan the stop sequence before a failure",
          "Different controls may stop new instructions, stop one bot, cancel resting orders or revoke an API key. None necessarily closes an existing position. Record the documented effect of each control for the exact service. The emergency plan needs separate rows for new signals, pending orders and open exposure.\n\nA fictional drill might pause new entries, inspect open orders directly at the exchange, cancel the orders you intend to cancel and make an explicit decision about remaining positions. This is a planning sequence, not a universal instruction to liquidate. The correct action depends on the product, account and current risk."
        ],
        [
          "Keep recovery evidence",
          "Record the last processed event identifier, last successful exchange acknowledgement, outstanding orders and the service status at the interruption. After recovery, reconcile account state before replaying messages. Blindly replaying an old buy instruction can create a new trade after the original opportunity has expired.\n\nRotate or revoke exposed credentials through the exchange, retain the incident timeline and inspect account activity. Use the platform's verified support path, not a direct message from someone claiming to be support. No API secret, seed phrase or account credential belongs in this site's worksheets."
        ]
      ]
    },
    {
      "path": "articles/crypto-signal-costs-and-breakeven.html",
      "title": "Crypto signal costs and break-even maths",
      "description": "Compare fixed-notional fees, slippage and subscription cost without confusing leverage with an edge.",
      "sections": [
        [
          "Choose a common denominator",
          "Compare costs in account currency and against a declared notional amount. A percentage of posted margin is not the same thing as a percentage of trade notional or account equity. Leverage changes exposure and liquidation risk; it does not remove transaction costs or prove that a signal has an advantage.\n\nFor a fictional $2,000 fixed-notional round trip, one basis point is $0.20. Eight basis points of total fees cost $1.60. If the assumed spread and slippage add twelve basis points, execution friction totals $4.00 before subscription, funding, borrowing and taxes."
        ],
        [
          "Allocate fixed subscriptions carefully",
          "An illustrative $30 monthly subscription divided across ten completed ideas allocates $3 to each idea. Across only two completed ideas it allocates $15. Neither is an observed provider price. A buyer should use the actual invoice, taxes and refund terms and count the ideas they were practically able to follow, not every message published.\n\nDo not scale the number of trades simply to make a subscription look inexpensive. More turnover can increase fees and correlated risk. A useful comparison keeps the intended activity and notional fixed, then asks how much gross benefit is needed to cover total cost."
        ],
        [
          "Signed financing is product-specific",
          "A funding payment can be a debit or a credit depending on the contract, direction, observed rate and payment boundary. Do not assume every venue has the same interval or that the current rate continues for an entire hold. Borrowing costs on a margin position are a different item from perpetual funding.\n\nUse the exact contract specification and account statement. If the next funding event is unknown, publish scenarios rather than a fabricated forecast. Avoid double-counting a funding item already included in the exchange's reported realised outcome."
        ],
        [
          "Separate gross opportunity from filled outcome",
          "A publisher may report the movement from an ideal entry to the highest later price. Your order may fill later, partially or not at all. Preserve both values with their definitions. Subtracting a generic fee from a best-price screenshot does not reconstruct a subscriber trade.\n\nIn the example above, a 0.5% gross move on $2,000 is $10. After $4 execution friction and $3 allocated subscription cost, $3 remains before other charges. A small change in assumptions can erase it. The example demonstrates arithmetic, not a profitable trading setup."
        ],
        [
          "Keep the decision reversible",
          "Before paying, request the population definition, cancellation policy, renewal terms and a sample export. Compare a no-subscription baseline with the same exposure and execution assumptions. A fee can be modest while the evidence is still insufficient; an expensive service is not automatically fraudulent.\n\nThe strongest practical output is a written purchase condition: what must be inspectable, what remains unknown and which risk would stop the purchase. Do not turn an educational break-even calculation into expected income or a recommendation to increase leverage."
        ]
      ]
    }
  ],
  "bibliography_notes": {},
  "scope": "Public-document research and educational exercises. No paid-room tracking, exchange connection or audited customer return is claimed.",
  "expanded_edition": "2026-10-14",
  "disclosure": "This publication's brief includes promoting Darren O'Neill and Vector Ridge. The owner says legal ownership is independent; that does not establish independent editorial direction or absence of compensation. Funding, sponsorship and referral records remain unconfirmed. The content is AI-assisted public-source synthesis, not a named tester panel, paid-room experiment or customer-rating sample.",
  "expanded_guides": [
    {
      "path": "guides/declared-population-and-missing-identifiers.html",
      "title": "Crypto signal populations and missing call identifiers",
      "description": "Reconcile declared ideas, listed rows, unknown states and omitted records before interpreting a crypto win percentage.",
      "sections": [
        [
          "Write eligibility before looking at winners",
          [
            "A population definition names the service, channel, interval, instrument class and qualifying instruction. An idea may require an actionable entry condition and original risk boundary, while commentary remains outside it. Record the treatment of retries, restated ideas and expired entries beforehand. Do not let a publisher's final winner list define the population retrospectively. A public preview can have different eligibility from a paid room. Preserve what you actually had permission to inspect, and distinguish that observed subset from the universe the seller claims to describe."
          ]
        ],
        [
          "Identity belongs to the idea, not every update",
          [
            "Use a persistent call identifier with linked message and execution events. A target announcement, amendment, duplicate forward or deletion notice is not automatically another trade. Keep the original channel context because a number alone can refer to different objects. Missing sequence values invite a reconciliation request, not an automatic accusation: they might be commentary, unavailable history or genuine absent calls. Conversely, a contiguous locally generated spreadsheet does not prove complete collection. Ask how the identifiers arose and reconcile them against original source records."
          ]
        ],
        [
          "Do not erase uncertainty from the denominator",
          [
            "Listed unclassified calls have an identifier but lack enough fields to determine their state. Missing records are declared ideas with no supplied row. Open calls have an unresolved position or idea state under the stated policy. Each represents a different evidence gap. Excluding all three from a closed-only headline may be legitimate only with an explicit scope; it cannot imply a complete record. Retain the counts and explain the unknown fields beside the percentage. Unknown does not mean zero profit, no exposure or an eventual win."
          ]
        ],
        [
          "Coverage and win fractions answer separate questions",
          [
            "The authored workbook declares twelve ideas, lists ten, classifies nine and closes six. Three gross winners produce a 50% closed fraction when one flat remains in the closed denominator. Known winners are only 25% of the declaration. Neither describes account return or verifies the declaration itself. The lens also shows a hypothetical maximum that assigns every unresolved or missing idea to a gross win. That arithmetic scenario is not a statistical interval, expected success rate or forecast. A larger unknown region weakens conclusions rather than create hidden evidence."
          ]
        ],
        [
          "A defensible purchase condition",
          [
            "Request a lawful export containing original ideas, versions, cancellations and outcomes with the population definition attached. If the seller supplies only selected screenshots, document the scope you could inspect and the precise missing fields. Do not invent a market-wide scam percentage from that gap or declare every seller on the platform dishonest. A buyer may decline because the evidence does not meet their needs without making an allegation of crime. A later fuller record should be identified as a new source version, not silently inserted into an earlier assessment."
          ]
        ]
      ],
      "case": "Authored case: EDU-10 has an identifier but no original instruction; EDU-11 and EDU-12 have no rows at all. The review therefore keeps one listed unclassified state and two missing records. Filling the gaps with plausible tokens or outcomes would fabricate provider evidence. The next request is the original eligible register and collection coverage, not another attractive dashboard. No real channel, actual market price, customer transaction or paid subscription was observed in this teaching packet.",
      "rows": [
        [
          "Declared",
          "12 ideas",
          "Not independently verified"
        ],
        [
          "Listed",
          "10 rows",
          "Two missing records"
        ],
        [
          "Classified",
          "9 rows",
          "One listed unknown"
        ],
        [
          "Closed",
          "6 ideas",
          "One gross flat included"
        ]
      ],
      "sources": [
        "telegram",
        "ots"
      ],
      "related": [
        "amendment-chronology-and-original-policy",
        "cancelled-unfilled-and-post-fill-exits"
      ]
    },
    {
      "path": "guides/amendment-chronology-and-original-policy.html",
      "title": "Crypto call amendments and the original trading policy",
      "description": "Preserve initial instructions, later changes and ambiguous timing without retroactively converting a losing idea into a winner.",
      "sections": [
        [
          "Keep versions rather than overwrite the instruction",
          [
            "Save the first lawfully observed instruction and append later changes. Each version needs the fields changed, original source context, observed time and the reason actually supplied. An edit marker establishes that a change exists, not necessarily the full previous content. A manually reconstructed predecessor needs that label. Do not backdate a clean spreadsheet row into a genuine prior instruction. A new entry condition or stop can create a different executable policy even when the author calls it a minor clarification. Both policies retain their own identity."
          ]
        ],
        [
          "Three clocks can disagree",
          [
            "Source creation, your observation and exchange acknowledgement are different events. Forwarding, reconnection and platform editing can separate them. A displayed message date does not prove that a particular subscriber received the original version before the price crossed a boundary. Preserve the available clock, timezone, precision and collection gaps. If genuine event order cannot be established, say so. The workbook's anonymous steps are educational ordering only, not authenticated dates. Never create plausible timestamps to make the invented amendment appear an actual prior risk-management decision."
          ]
        ],
        [
          "A changed boundary needs a declared interpretation",
          [
            "Suppose an authored initial stop differs from an amended stop. The result under the original policy and the result under the later policy require different inputs. Do not choose whichever gives a favorable answer after inspecting the path. For actual research, the native frozen entry and exit policy remains authoritative; this consumer guide grants no permission to replace it. For a service review, state which version a subscriber could reasonably have acted on and what evidence supports that statement. Missing observations can prevent either reconstruction."
          ]
        ],
        [
          "Retain deletion and duplicate history",
          [
            "A deletion notice is an event attached to an idea, not permission to remove a losing row. A forwarded duplicate is another delivery event, not another winning trade. A repost with a materially different instruction requires an explicit successor relationship rather than silently inherit the predecessor's performance. Original records may contain personal information or restricted paid content, so preserve only what you lawfully hold and redact without changing necessary fields. Hashes can identify retained bytes but do not restore an earlier version that was never captured."
          ]
        ],
        [
          "What an audit conclusion can say",
          [
            "A useful finding identifies the versions observed, chronology supported, exact ambiguity and next required source. It need not invent an authoritative outcome when a candle touches both stop and target or receiver time is absent. Separate data correction, amended instruction and interpretation change in the release note. A source platform's documentation describes how messages work; it does not certify a particular seller's honesty or full archive. The review can remain valuable by explaining why one selected winner is not yet reproducible under the advertised policy."
          ]
        ]
      ],
      "case": "Authored case: EDU-02 retains an initial instruction and a later alternative boundary, then a gross-loss teaching label. No real price path is attached, so the label is not independently established by the chronology. The amendment is a sixteenth-event-packet entry, not a new winning idea. A genuine investigation would request original versions and adequately timed observations, keeping any impossible ordering unresolved rather than fabricate an executable winner.",
      "rows": [
        [
          "Initial",
          "Retained text",
          "Not authenticated payload"
        ],
        [
          "Amendment",
          "New linked event",
          "Not overwritten original"
        ],
        [
          "Receiver",
          "No genuine arrival",
          "Delivery unanswered"
        ],
        [
          "Outcome",
          "Teaching label",
          "No market reconstruction"
        ]
      ],
      "sources": [
        "telegram",
        "updates",
        "ots"
      ],
      "related": [
        "event-arrival-clock-and-order-ambiguity",
        "proof-receipts-byte-scope-and-completeness"
      ]
    },
    {
      "path": "guides/cancelled-unfilled-and-post-fill-exits.html",
      "title": "Cancelled crypto calls, unfilled entries and actual exits",
      "description": "Distinguish a never-filled cancellation from an expired condition or a position closed after execution.",
      "sections": [
        [
          "The order lifecycle matters more than the label",
          [
            "A publisher may write cancelled while an exchange order is still resting or a subscriber already holds a position. Record the original entry condition, order submission, acknowledgement, fills and cancellation acknowledgement separately. A message is not an exchange action. Without actual order records, a review can discuss the instruction but cannot claim the account ended flat. The same label can describe an idea withdrawn before entry or a position abandoned after exposure, so use a state definition instead of infer the financial effect from the word."
          ]
        ],
        [
          "Never-filled is a specific claim",
          [
            "A never-filled cancellation requires evidence that the relevant order or condition did not produce an entry before withdrawal. An unfilled expiration means the eligible entry window ended without a fill under the declared rule. The lens keeps those states separate even though both are non-winners in its resolved-event share. If timing cannot establish whether entry occurred, retain an unknown state. Do not remove the idea because it never contributed to a closed-only win headline. It still belongs in the original eligible population when the definition includes issued actionable calls."
          ]
        ],
        [
          "Partial fills prevent a binary shortcut",
          [
            "An order can fill partly before its remainder is cancelled. The cancelled quantity and executed quantity need separate records. A fully cancelled remainder does not cancel the existing exposure. Position costs and exits belong to the filled portion, with quantities and cash treatment specified. Counting one order status as the whole idea's outcome can hide this distinction. A real account review needs exchange-side evidence rather than a bot's final banner alone. The educational count lens has no quantities and deliberately does not reconstruct a partial-fill financial result."
          ]
        ],
        [
          "Denominators must keep their names",
          [
            "Closed-trade win rate excludes never-filled states when that is the declared policy. A resolved-event share includes them and therefore answers another question. Neither convention automatically proves an edge. In the default authored batch, three winners over eight resolved events is 37.5%, while three over six closed ideas is 50%. A room advertising one should not silently switch to the other after favorable cancellations. A buyer should ask whether expired entries, withdrawn calls and post-fill exits were applied consistently to both winning and losing opportunities."
          ]
        ],
        [
          "Plan evidence collection without live-risk experiments",
          [
            "An actual review should obtain lawful original history and selected account records, not connect a stranger's bot with excessive permissions merely to learn what cancelled means. Use a rehearsal to identify documented controls, then keep rehearsal fills separate from actual exchange fills. Record the ability to stop new instructions, cancel resting orders and inspect remaining positions as different actions. The site has not conducted that paid-account test. Current platform conditions and regional eligibility require direct confirmation before a buyer depends on a service."
          ]
        ]
      ],
      "case": "Authored case: EDU-05 is a never-filled cancellation and EDU-06 an unfilled expiration. Both remain issued ideas. The packet does not give them a net result or claim genuine exchange cancellation. A hypothetical partly filled call would need another explicit quantity record and could not be hidden in either bucket. The next evidence request is the order lifecycle with acknowledgement and fills, not a screenshot showing a bot was paused.",
      "rows": [
        [
          "Cancelled",
          "No teaching fill",
          "Original call retained"
        ],
        [
          "Expired",
          "Window ended unfilled",
          "Not a closed loss"
        ],
        [
          "Post-fill",
          "Exposure existed",
          "Execution ledger required"
        ],
        [
          "Ambiguous",
          "Timing unavailable",
          "Unknown, not guessed"
        ]
      ],
      "sources": [
        "hopper",
        "telegram"
      ],
      "related": [
        "partial-exits-and-idea-level-denominators",
        "API-revocation-open-orders-and-recovery"
      ]
    },
    {
      "path": "guides/partial-exits-and-idea-level-denominators.html",
      "title": "Partial crypto exits and idea-level win denominators",
      "description": "Separate target events, quantities and remaining exposure before counting a multi-target call as a win.",
      "sections": [
        [
          "A target is an event, not necessarily a new idea",
          [
            "One call can generate three target messages and a final stop. If every favorable target becomes a win but the final losing remainder counts only once, the event rule may inflate the headline. Choose idea-level or execution-level analysis before viewing results and apply it symmetrically. Keep a persistent parent idea with child fills and exits. A message saying target reached does not establish that an order was resting, executable or filled. An actual transaction needs its venue, product, quantity and acknowledgement rather than an announcement alone."
          ]
        ],
        [
          "Retain the remaining quantity",
          [
            "After a partial exit, preserve original size, closed amount and remaining exposure. A tiny first target can coexist with a much larger later loss. A stop moved to breakeven may still leave financing and execution costs. Do not call a position risk-free merely because one price boundary changed. Multiple contracts or token redenominations need explicit conversion. If size records are missing, state that an idea-level directional label cannot answer the weighted account question. The workbook supplies no real quantities and therefore does not calculate a subscriber return."
          ]
        ],
        [
          "Define gross flats and net outcomes separately",
          [
            "A price-flat exit is a gross directional state under the chosen convention, not necessarily a zero-money outcome. Fees, spread, slippage and signed funding can make it negative. The new lens retains flats in its closed denominator, while the older four-count ledger uses only wins and losses. Those different definitions should stay visible. A publisher could choose another declared policy, but must preserve how every call was classified. Changing the flat rule after seeing the chart is a revision that requires recomputation, not an unannounced improvement."
          ]
        ],
        [
          "Avoid weighted claims without weights",
          [
            "A count of favorable ideas gives equal voting weight to every classified idea. Financial aggregation needs quantities, exposure, capital ownership, cash flows and actual costs. A risk-normalized outcome can aid comparison only when its unit and initial risk are honestly defined. Different R values do not automatically share one account weight. Adding them into a large percentage creates a new claim not supported by the count table. Keep account equity, gross idea labels and conditional educational cost arithmetic in separate outputs, and identify what each one omits."
          ]
        ],
        [
          "A reproducible request to the seller",
          [
            "Ask for the original multi-target policy, allocation at each exit, treatment of stop changes and full idea-to-order mapping. Include unfilled ideas and unknown quantities rather than restrict the export to profitable target notifications. If a paid room forbids redistribution, request permitted inspection and describe that access scope without republishing private material. Missing evidence here does not prove no evidence exists anywhere. It means the review cannot establish the specific advertised outcome from its supplied records. An honest narrower finding is more useful than a precise fabricated score."
          ]
        ]
      ],
      "case": "Authored case: a hypothetical idea has several target announcements but remains one idea in the declared population. Its quantities and actual fills are absent, so the guide assigns no weighted financial outcome. EDU-03 is a gross flat with assumed cost in a separate table; it demonstrates why flat price and flat cash are not interchangeable. The next request is the original quantity allocation and exchange lifecycle, with unfavorable remaining exposure retained.",
      "rows": [
        [
          "Idea",
          "One persistent identity",
          "No extra wins for updates"
        ],
        [
          "Target",
          "Linked event",
          "Fill still unverified"
        ],
        [
          "Remainder",
          "Quantity needed",
          "Do not infer zero exposure"
        ],
        [
          "Account",
          "Weights and cash flows",
          "Not a count fraction"
        ]
      ],
      "sources": [
        "hopper",
        "cftc"
      ],
      "related": [
        "gross-wins-net-losses-and-signed-funding",
        "account-equity-cash-flows-and-marking"
      ]
    },
    {
      "path": "guides/gross-wins-net-losses-and-signed-funding.html",
      "title": "Gross crypto winners, net losses and signed financing",
      "description": "Keep fee units and signed funding separate from directional labels and account-return claims.",
      "sections": [
        [
          "Start by identifying the unit",
          [
            "A percentage can describe price change, trade notional, posted margin or account equity. Those units are not interchangeable, especially when leverage changes. A cost expressed in basis points must be applied to its stated notional, while a subscription is a fixed cash item under actual billing terms. Write units beside every field before subtraction. A best hypothetical research fill is not an actual broker execution, and this educational guide changes no established research fill convention. Actual account arithmetic needs its own fills and quantities rather than an ideal publisher price."
          ]
        ],
        [
          "Gross direction is not net money",
          [
            "The count lens classifies closed gross wins, losses and flats. It does not deduct transaction costs to decide their state. The workbook separately assigns invented gross-R values and assumed costs to six closed ideas. EDU-07 gains 0.5 R gross and incurs 0.7 R cost, giving -0.2 R net before any other item. Calling it a gross win can be descriptively consistent under that policy but does not imply the buyer earned money. A site should display the convention instead of turn the attractive count into a return claim."
          ]
        ],
        [
          "Financing must keep its sign and provenance",
          [
            "The packet subtracts signed financing: a positive assumed value is a debit and a negative one is a credit. Actual perpetual funding depends on the contract, direction, observed rate and relevant payment boundary. Borrowing charges are another object. An exchange statement may already include some items in a displayed realized figure, so avoid subtracting them twice. Do not project the latest rate over an entire holding period without labelling that assumption. The authored credit row teaches sign handling, not an observed funding payment for a real contract."
          ]
        ],
        [
          "Subscription allocation is a scenario",
          [
            "Dividing an invoice by completed ideas changes with the actual usable activity. Counting every published message as a followed trade can make the allocation falsely small. Retain total subscription expense beside any per-idea teaching allocation, and do not encourage extra turnover simply to dilute a fixed fee. Taxes and regional rules require separate qualified treatment and are not modeled. An actual selected checkout and existing customer agreement determine entitlement. A marketing page's old price cannot silently serve as a current financial input after the offer changes."
          ]
        ],
        [
          "Do not aggregate absent account weights",
          [
            "Six independent R rows can explain subtraction without defining a capital path. Initial risk, concurrent positions, cash, deposits, fees and currency conversion are missing from this packet. Therefore no account sum, compounded return or expected income is produced. Open and unknown ideas have null hypothetical net results rather than assigned zeros. A stronger real conclusion needs full record reconciliation, not more decimal places. Preserve source price, actual fill and after-cost account result separately so a buyer can see exactly which claim is supported and which remains conditional."
          ]
        ]
      ],
      "case": "Authored case: EDU-08 has gross -1 R, cost 0.1 R and financing -0.05 R, resulting in -1.05 R. The negative financing term is an assumed credit, not proof a venue paid it. EDU-03's price-flat outcome becomes -0.2 R after assumed cost. Neither row carries an actual fill or account weight. This deliberately separates a correct subtraction from evidence a real subscription produced the result.",
      "rows": [
        [
          "EDU-07",
          "0.5 - 0.7 - 0",
          "-0.2 R, hypothetical"
        ],
        [
          "EDU-08",
          "-1 - 0.1 - (-0.05)",
          "-1.05 R, hypothetical"
        ],
        [
          "Open states",
          "Net result absent",
          "Null rather than zero"
        ],
        [
          "Account sum",
          "Weights absent",
          "Not computed"
        ]
      ],
      "sources": [
        "decimal",
        "hopper"
      ],
      "related": [
        "account-equity-cash-flows-and-marking",
        "partial-exits-and-idea-level-denominators"
      ]
    },
    {
      "path": "guides/account-equity-cash-flows-and-marking.html",
      "title": "Crypto account equity, cash flows and open-position marking",
      "description": "Reconcile a complete valuation path instead of interpreting selected closed-trade screenshots as account growth.",
      "sections": [
        [
          "Declare the account and valuation currency",
          [
            "Identify the actual account boundary, reporting currency, valuation clock and included wallets or subaccounts. An isolated winning position does not identify the remaining portfolio. A balance figure may omit open exposure while equity includes a particular marking convention. Use the platform's exact definition rather than infer it from a green screenshot. Stablecoin units, token units and fiat valuations can change relative to each other. An account outcome needs a consistent conversion policy and observation source, with missing valuations explicit rather than filled using a favorable later price."
          ]
        ],
        [
          "Deposits are not trading profits",
          [
            "Keep contributions, withdrawals, transfers and trading cash flows in distinct fields. A larger closing balance may come from a deposit; a lower balance may reflect a withdrawal. Internal transfers between included subaccounts should not be counted twice. Token migrations, reward distributions and borrowing obligations need their own treatment. Choose a suitable return convention before interpreting the path and retain the underlying cash-flow timestamps. This guide does not calculate a money-weighted or time-weighted return from absent records, and a count of closed winners cannot supply the required values."
          ]
        ],
        [
          "Mark unresolved positions honestly",
          [
            "Open positions carry exposure even when they are excluded from a closed-only win fraction. Record their quantities, contract specification and valuation source at the declared clock. A stale quote can make an equity path look smooth without reducing underlying risk. If reliable marking is unavailable, publish that gap rather than assume zero change. Pending orders also require reconciliation, though they differ from filled exposure. The packet's open call is merely an authored state; it supplies no actual position, mark, liquidation level or account drawdown."
          ]
        ],
        [
          "Costs and currency conversions belong to the path",
          [
            "Fees, funding, borrowing, conversions and subscription expenses can live in different ledgers. Identify which are already reflected in exchange P&L and which remain separate. Avoid comparing an account result after some costs with a publisher's ideal gross price move. Valuation policy may create differences even when the transactions agree. A real audit should preserve original statements and explain every reconciliation adjustment, rather than quietly modify the export until the headline matches. Redaction can protect identity without erasing the quantities and cash treatment needed for reproduction."
          ]
        ],
        [
          "What a complete review would publish",
          [
            "State the period, account scope, capital ownership, source versions, missing intervals and exact calculation convention. Separate the financial result from any claimed model causality or subscriber delivery. A founder's competition account can be genuine without identifying the current subscription's capital path. A broker export can support transaction evidence without certifying the complete idea population. The consumer conclusion should name these limits. This publication has no actual account sample and does not invent a drawdown series, customer cohort or independently reproduced compound return to make the page look authoritative."
          ]
        ]
      ],
      "case": "Authored case: a fictional viewer sees three winners but has no opening equity, deposits, fees or open-position marks. The closed fraction is calculable under the declared counts; account growth is not. Entering zero for the missing values would convert absent evidence into a numerical result. The next request is a complete account-boundary export and consistent valuation policy, with both profitable and unfavorable intervals retained.",
      "rows": [
        [
          "Balance",
          "Platform definition",
          "May differ from equity"
        ],
        [
          "Deposit",
          "External flow",
          "Not a trading gain"
        ],
        [
          "Open position",
          "Quantity and mark",
          "Unknown is not flat"
        ],
        [
          "Return",
          "Whole path required",
          "Not reconstructed here"
        ]
      ],
      "sources": [
        "cftc",
        "ethereum"
      ],
      "related": [
        "gross-wins-net-losses-and-signed-funding",
        "wallet-labels-chain-events-and-exchange-fills"
      ]
    },
    {
      "path": "guides/wallet-labels-chain-events-and-exchange-fills.html",
      "title": "Wallet labels, on-chain events and exchange fills",
      "description": "Separate an observed chain transaction from inferred ownership, directional intent and an executed exchange order.",
      "sections": [
        [
          "The transaction and the label are different sources",
          [
            "A chain record may establish a transaction under the network's rules while a human-readable owner label comes from another source. Preserve chain, transaction identifier, observed block context and the label's issuer and version. A later relabelling can change the interpretation without change the underlying transaction. Do not treat a famous name beside an address as cryptographic proof of beneficial ownership. The site supplies no actual wallet investigation, verified entity attribution or measured predictive result, so anonymous teaching identities should not become real whale evidence."
          ]
        ],
        [
          "A transfer has several possible meanings",
          [
            "An exchange deposit, internal reshuffle, collateral movement, bridge action or custody transfer can look similar at a high level. A token moving does not necessarily mean a market sale occurred. State alternative explanations before a directional claim. If a source knows more through proprietary attribution, identify the actual accessible evidence and uncertainty rather than borrow its confident wording. A single selected chart after a large transfer is not an independent validation sample. Keep the event observation separate from the trading hypothesis and any action a subscriber could have taken."
          ]
        ],
        [
          "Availability determines whether a decision was causal",
          [
            "Record when the event became observable to the relevant system, not merely the time later displayed in a retrospective explorer. Block inclusion, finality assumptions, indexing delay and a user's receipt are separate boundaries. Historical reconstructed labels may use knowledge unavailable at the decision point. A causal strategy needs its frozen information policy and source version. This guide grants no permission to weaken the actual instrument factory or change its research fill convention. The authored packet uses no blockchain timestamps to fabricate causal availability."
          ]
        ],
        [
          "An exchange order remains a separate object",
          [
            "A chain transfer can fund an account without identifying any subsequent order. Centralized exchange trading may occur off-chain, with its own account and execution records. Venue, contract, direction, quantity, order acknowledgement and fills are needed for an execution claim. A wallet balance cannot reconstruct a derivative position's funding or liquidation policy. Conversely, an exchange fill does not validate a wallet-owner label. Build the evidence map across these boundaries instead of treating a transaction hash as a universal proof of trade timing, profitability and operator identity."
          ]
        ],
        [
          "A useful limited assessment",
          [
            "A buyer can ask whether the product supplies raw events, inferred entity labels, discretionary analysis or actionable instructions. Those are different deliverables with different evidence needs. Confirm the selected product's source rights, update cadence and correction policy rather than infer an automated bot from a commentary page. A review can explain this mechanism even without paid access, but it must not claim a tested predictive hit rate. Missing attribution evidence is not an accusation that the vendor invented it; it bounds what the present record can establish."
          ]
        ]
      ],
      "case": "Authored case: an EDU event is labelled an exchange transfer in a fictional note, but has no real address, transaction, label issuer or order record. The packet therefore assigns no buy, sell or fill. A genuine later source should provide chain context and label lineage, followed by separate execution evidence if an account trade is claimed. Plausible hexadecimal strings are not substituted for absent primary records.",
      "rows": [
        [
          "Transaction",
          "Chain event",
          "Not intent"
        ],
        [
          "Label",
          "External attribution",
          "Not guaranteed ownership"
        ],
        [
          "Order",
          "Venue record",
          "Not chain transfer"
        ],
        [
          "Outcome",
          "Account reconciliation",
          "Not hash alone"
        ]
      ],
      "sources": [
        "ethereum",
        "ots"
      ],
      "related": [
        "event-arrival-clock-and-order-ambiguity",
        "historical-token-universe-and-migrations"
      ]
    },
    {
      "path": "guides/event-arrival-clock-and-order-ambiguity.html",
      "title": "Crypto signal arrival clocks and ambiguous execution order",
      "description": "Distinguish publisher time, receiver arrival and executable order events when a price path cannot resolve stop and target order.",
      "sections": [
        [
          "Name the clock before sorting the ledger",
          [
            "A displayed source date, collection timestamp, subscriber arrival and exchange acknowledgement represent different objects. They may have different timezone, precision and synchronization. Sorting a spreadsheet by one field cannot establish another boundary. Preserve which clock was observed and which was reconstructed. A manually typed date is not a genuine delivery receipt. The workbook deliberately uses step identifiers rather than fabricate authenticated times. A buyer evaluating timeliness should ask for lawful receiver evidence and account-side events, not assume a publisher's timestamp proves everyone could act then."
          ]
        ],
        [
          "Collection interruptions require a gap record",
          [
            "Reconnection and changed access can leave a collector with incomplete history. Platform sequence mechanisms concern their defined context and do not automatically establish the complete paid-service population. Retain collection start, interruptions, scope and recovery evidence. A later download of current messages may omit prior versions or deletes. Report the interval you can actually inspect. Do not silently fill it using the seller's summary or treat an apparently contiguous teaching register as evidence that no real events were missed. Scope and completeness need separate tests."
          ]
        ],
        [
          "A candle can be insufficient evidence",
          [
            "If a bar's high and low cross both target and stop, their order may remain unknown at that resolution. A favorable assumption is not an observed fill. Use finer lawful observations when available and retain the predeclared execution convention. If adequate observations are absent, publish an ambiguous outcome rather than choose the route that maximizes a headline. Research references and actual broker fills remain distinct. This guide does not override the established best hypothetical fill convention or native exit policy of genuine research; it identifies the evidence required for a consumer execution claim."
          ]
        ],
        [
          "Latency and expiry can change the paid object",
          [
            "A forwarded alert arriving after its entry window has expired is not the same executable opportunity as the original idea. Record source instructions, receiver delay and the declared handling of stale events. Automatic replay can duplicate or revive an instruction that should no longer create exposure. A test needs current configuration and actual venue acknowledgement. Documentation about message transport can explain why these questions matter without supplying a seller's measured latency distribution. The site has not measured a paid-room delivery percentile or performed a live exchange integration."
          ]
        ],
        [
          "Conclusions should retain the unresolved order",
          [
            "An assessment can say the original idea was available in a captured source while subscriber arrival or execution order remains unknown. That is narrower than declaring the trade impossible or verified profitable. A later timing source needs its own identity and reconciliation with the prior record. Missing evidence must not be backdated into an earlier clean history. In the diligence card, the next request is original versions, actual arrival and adequate price observations. More linked articles do not convert absent timestamps into independent confirmation."
          ]
        ]
      ],
      "case": "Authored case: EDU-02 has an initial and an amended instruction but no genuine receiver clock or market path. Its step order cannot establish whether a subscriber entered before a boundary changed. A real review would preserve both policy versions and declare which ordering remains unknowable. The packet's gross-loss label is educational, not a recovered broker outcome. No invented microsecond timestamp or favorable candle path is added.",
      "rows": [
        [
          "Publisher",
          "Source creation",
          "Not receiver arrival"
        ],
        [
          "Collector",
          "Observed record",
          "Scope can have gaps"
        ],
        [
          "Exchange",
          "Acknowledgement/fill",
          "Requires account evidence"
        ],
        [
          "Bar path",
          "Order unknown",
          "No favorable guess"
        ]
      ],
      "sources": [
        "updates",
        "telegram"
      ],
      "related": [
        "amendment-chronology-and-original-policy",
        "API-revocation-open-orders-and-recovery"
      ]
    },
    {
      "path": "guides/API-revocation-open-orders-and-recovery.html",
      "title": "Crypto API revocation, open orders and recovery evidence",
      "description": "Inspect the documented effect of stopping automation separately from cancelling orders or resolving existing positions.",
      "sections": [
        [
          "Map authority without exposing secrets",
          [
            "Identify the service storing a credential, exchange granting authority, permitted products and exact permission scope. Read-only and trade-enabled access create different risks; inability to withdraw does not prevent trading losses. Use current official configuration and regional eligibility information rather than an old tutorial. Never paste a seed phrase, private key or API secret into this site's forms. A consumer assessment can request a redacted permission description while keeping authentic account identifiers private. No credential or exchange connection was collected for this publication's fictional packet."
          ]
        ],
        [
          "Pause, cancel and close are different actions",
          [
            "A bot pause may stop new decisions without cancel resting orders or eliminate positions. An API revocation can stop further authorized instructions while existing venue state remains to be inspected. The exact behavior depends on documented product and account rules, so do not offer a universal promise that one button makes an account safe. Record new-message processing, pending orders and filled exposure in separate rows. The original permission workbench retains those distinctions. A screenshot of a stopped bot cannot establish every exchange-side consequence."
          ]
        ],
        [
          "Reconcile the venue before replay",
          [
            "Recovery needs the last processed instruction, acknowledgement, open-order inventory and existing position state. Blindly replaying an old message can create an extra entry or revive an expired condition. Duplicate handling should retain parent idea identity and actual account events. A fictional duplicate-forward event teaches that distinction but is not a tested idempotence guarantee for any platform. In a real installation, configuration version and documented recovery behavior need lawful inspection. A paper-trading rehearsal may expose workflow errors while leaving queue priority and live liquidity untested."
          ]
        ],
        [
          "Keep incident evidence and official support paths",
          [
            "Preserve the observed interruption, authorized actions and account records you lawfully hold. If a credential is suspected exposed, use the verified exchange process rather than a private message from purported support. Record what was actually revoked and inspect activity instead of assume every product uses the same key model. Avoid publishing private identifiers or third-party paid content without rights. This guide does not claim an incident occurred at a named vendor. It gives buyers a way to ask what a service's documented controls actually do."
          ]
        ],
        [
          "No software pass is a safety certification",
          [
            "The site's browser tests verify count arithmetic, imports and navigation. They do not test an exchange integration, permission enforcement or real emergency liquidation. The new lens connects no account and creates no order. A stronger automation review requires selected current offer, lawfully inspected configuration and actual lifecycle evidence, including failures and remaining exposure. Production data systems must run in managed cloud services with workstations off; this publication creates no PC fallback, tunnel or scheduled trading process. A public static guide remains different from a certified operational route."
          ]
        ]
      ],
      "case": "Authored case: an EDU duplicate arrives after a teaching cancellation. The packet retains both events without executing anything. The buyer's next evidence request is the platform's current stale-message and duplicate policy plus venue-side order state. No assertion that revocation closes positions is made. Actual credentials, configured bot, exchange fills and a successful recovery test remain absent rather than being simulated into a verified safety badge.",
      "rows": [
        [
          "Pause",
          "New instructions",
          "Position state separate"
        ],
        [
          "Cancel",
          "Resting quantity",
          "Filled amount retained"
        ],
        [
          "Revoke",
          "Credential authority",
          "Inspect venue state"
        ],
        [
          "Recover",
          "Reconcile first",
          "No blind replay"
        ]
      ],
      "sources": [
        "hopper",
        "cftc"
      ],
      "related": [
        "cancelled-unfilled-and-post-fill-exits",
        "real-provider-investigation-rights-and-failure-records"
      ]
    },
    {
      "path": "guides/proof-receipts-byte-scope-and-completeness.html",
      "title": "Crypto proof receipts, included bytes and complete-history claims",
      "description": "Keep byte commitments, attestation status, delivery and population completeness as separate evidence objects.",
      "sections": [
        [
          "Identify the exact included content",
          [
            "A digest concerns a particular byte sequence under a stated algorithm and serialization. Save the actual payload and identify whether fields such as stop, target, quantity or costs were included. A proof for an entry-only record cannot establish omitted risk instructions. Changing whitespace or encoding may change identity even when displayed text seems equivalent. A real check needs its actual payload and receipt; the site's fictional packet supplies neither. The review does not manufacture a plausible digest and describe it as an authenticated trading commitment."
          ]
        ],
        [
          "Receipt creation is not every later claim",
          [
            "OpenTimestamps has distinct receipt and verification stages. A pending submission should remain pending until the required attestation can be verified against the relevant exact content. A completed byte attestation still has a bounded scope. It does not automatically establish publisher authorship, lawful source rights, receiver arrival, executable price or account profit. Keep the attestation object, verification result and missing stages named rather than convert a broad verified badge into all those conclusions. This publication checked no genuine provider payload/proof pair for the authored cards."
          ]
        ],
        [
          "A valid included row can coexist with omissions",
          [
            "Even if every supplied row has a valid commitment, the archive may omit other eligible calls. Coverage requires reconciliation with the independently defined population, original channel context and retained version events. A declared total also needs support; it is not complete because it was placed in a signed file. The denominator lens keeps two missing identifiers visible in its default. The maximum scenario cannot infer how those calls resolved. Cryptographic identity and collection completeness are different questions, and neither becomes subscriber financial performance merely through repetition across sites."
          ]
        ],
        [
          "Publication and subscriber delivery need their own records",
          [
            "A file might exist before a move without reach a particular buyer before execution became stale. Record actual publication, receiver arrival and order acknowledgement separately when making a delivery claim. An authenticated earlier document does not reconstruct a later fill. A meaningful service review states which boundaries were tested and which remain missing. Anonymous educational step IDs are not proof times, and a web deployment receipt verifies this site's publication files rather than a trading call's historical delivery. Do not interchange those objects."
          ]
        ],
        [
          "Use a bounded verification report",
          [
            "A genuine report should state exact source bytes, algorithm, proof status, verifier and result, then explain the fields outside scope. Failed and unavailable receipts remain in the report rather than disappear from a favorable summary. Private material needs lawful inspection and safe redaction; a hash does not grant redistribution rights. A stronger return claim still needs quantities, costs, weights and complete account reconciliation. A proof can be valuable while leaving those requests outstanding. The honest next artifact is specific, not another unsourced endorsement."
          ]
        ]
      ],
      "case": "Authored case: a teaching card asks whether an entry-only commitment could certify a changed stop. No actual commitment is supplied, and the absent field cannot be inferred. The same packet has two missing population identifiers, so a hypothetical successful check on ten rows would not resolve coverage. Actual bytes, completed attestation, subscriber arrival and financial accounting remain separate next-evidence requests rather than be condensed into a fabricated audited-history claim.",
      "rows": [
        [
          "Payload",
          "Exact included fields",
          "Absent fields remain absent"
        ],
        [
          "Receipt",
          "Status required",
          "Pending is not completed"
        ],
        [
          "Coverage",
          "Full eligible population",
          "Not proven by one row"
        ],
        [
          "Return",
          "Account path",
          "Not a byte commitment"
        ]
      ],
      "sources": [
        "ots",
        "telegram"
      ],
      "related": [
        "declared-population-and-missing-identifiers",
        "amendment-chronology-and-original-policy"
      ]
    },
    {
      "path": "guides/historical-token-universe-and-migrations.html",
      "title": "Historical token universes, migrations and survivor bias",
      "description": "Preserve historical membership, contract identity and executable access instead of build a crypto comparison from current winners.",
      "sections": [
        [
          "A ticker is not a sufficient instrument identity",
          [
            "Tokens can share symbols, migrate contracts, redenominate or trade on different venues and networks. Preserve chain, contract or native-asset identity, venue, product type and historical eligibility. A spot asset and perpetual contract with similar names have different accounting and execution. Do not splice them into one performance record without a declared mapping. The authored packet uses anonymous EDU assets and no genuine instrument history, so its symbols are teaching labels rather than evidence an actual token had continuous executable prices."
          ]
        ],
        [
          "Membership must exist at the historical date",
          [
            "An index built from today's surviving winners can omit failed or delisted assets. Record inclusion and removal dates, liquidity filters, weighting and rebalancing policy before judging rotation signals. A current constituent list is not an as-of historical universe. If only a fixed surviving set is available, label it a limited research reference instead of a representative market record. Missing old tokens are an evidence gap, not permission to fabricate zero prices or invent a delisting return. The comparison must retain how inaccessible assets were treated."
          ]
        ],
        [
          "Migration needs a versioned conversion policy",
          [
            "A redenomination or contract swap may require conversion factors, dates and rights information. Preserve original source records and distinguish raw prices from adjusted references. A smooth adjusted chart can aid one question while obscure what an actual holder could execute. Fees, exchange support and timing may differ. Do not silently map an old ticker to a new contract because the name resembles it. A genuine instrument task must use the authoritative asset route and independently verified source adapter rather than force a new class through an unrelated method."
          ]
        ],
        [
          "Availability and liquidity constrain execution",
          [
            "A reported price at a venue does not prove a subscriber could trade a stated amount there. Preserve spread, depth, account access, order rules and observation timing when the claim requires execution. Thin tokens can show dramatic percentage moves without support the promoted position size. A current accessible venue is not evidence it was accessible in the chosen historical interval. This page has no actual order-book sample or paid-room transaction history and therefore gives no measured slippage rate or universe-wide performance statistic."
          ]
        ],
        [
          "Benchmark selection should stay frozen",
          [
            "A bot-versus-hold comparison needs the same capital boundary, period, eligible universe and cost convention. Selecting the best surviving token after viewing its return changes the benchmark question. Keep failed ideas and unfavorable rebalancing intervals in the source population. Real research retains raw causal entry identity, one predeclared native exit and its required independent master. A topical guide does not complete those gates. The buyer can request this evidence structure without receive a fictional empirical finding, current altcoin-season forecast or guarantee of profitable implementation."
          ]
        ]
      ],
      "case": "Authored case: EDU-ASSET-01 is only an anonymous label. Replacing it with a current famous token would imply an actual tested instrument absent from the packet. A real investigation would first pin historical contract identity, universe membership, migration source and trading access. Only then could a declared rule be evaluated. A smooth surviving chart and a confident symbol name cannot supply those records.",
      "rows": [
        [
          "Ticker",
          "Display label",
          "Not full identity"
        ],
        [
          "Universe",
          "As-of membership",
          "Not today's survivors"
        ],
        [
          "Migration",
          "Versioned mapping",
          "Not silent splice"
        ],
        [
          "Benchmark",
          "Frozen rule",
          "Not selected winner"
        ]
      ],
      "sources": [
        "ethereum",
        "cftc"
      ],
      "related": [
        "wallet-labels-chain-events-and-exchange-fills",
        "account-equity-cash-flows-and-marking"
      ]
    },
    {
      "path": "guides/real-provider-investigation-rights-and-failure-records.html",
      "title": "Real crypto provider investigations: access, rights and failures",
      "description": "Define a lawful review scope and preserve failed or unavailable records before claiming a live provider test.",
      "sections": [
        [
          "Identify what was actually purchased or inspected",
          [
            "A public-document assessment, free preview, paid room and connected-account experiment have different scope. State the exact product version, observation interval, account boundary and access rights. A brand can operate several distinct offers, so a source about its bot infrastructure does not validate every seller on the marketplace. This publication has performed no paid-room or real-capital test. Its complete authored cards are documentation examples, not a portfolio of completed investigations. The absence of a source here also does not prove a vendor has no source anywhere."
          ]
        ],
        [
          "Get rights before collecting or distributing records",
          [
            "A useful audit may require lawful original instructions, amended versions and redacted execution records. Confirm what can be retained, inspected and republished under the applicable agreement. Public accessibility alone does not transfer every redistribution right. Avoid uploading personal identifiers, private channel content or credentials into the site's educational forms. Describe unavailable evidence explicitly when access is denied, instead of reconstruct plausible private messages. A review can publish a bounded question and primary product link without invent a successful inspection of materials it never received."
          ]
        ],
        [
          "Keep failures and interruptions in the packet",
          [
            "Record missing intervals, deleted or unrecoverable versions, unavailable proofs, incomplete fills and contradictory summaries. They are part of collection scope, not inconvenient rows to discard. A failed source retrieval should carry observed status or error and date rather than a fabricated successful read. Product documentation can change after review, so distinguish a dated mechanism description from a continuously monitored guarantee. The release process checks the published site and its tools; it creates no automatic paid-room observation pipeline, source monitor or scheduled AI writer."
          ]
        ],
        [
          "Commercial context changes the interpretation",
          [
            "A marketing commission, referral relationship or sponsorship is relevant even when legal ownership is separate. The owner has described these publications as legally independently owned, but that statement does not establish editorial independence or absence of compensation. A credible investigation names its known purpose and outstanding commercial records. It does not manufacture a neutral reviewer panel, star average or customer sample. Coordinated pages repeating one supplied figure are not multiple independent audits. Favorable conclusions should follow the same source standard as unfavorable ones."
          ]
        ],
        [
          "Publish a claim-by-claim conclusion",
          [
            "Separate supported product mechanism, unresolved population, chronological evidence, hypothetical research reference and actual financial outcome. A software arithmetic pass does not validate a trading strategy, while a source gap does not establish a crime. A real instrument research claim still requires the full canonical factory and independent master rather than a component test. If stronger evidence arrives, give it a new scoped version and describe its impact. More content can improve reader understanding and search access, but cannot guarantee indexing, rankings, AI citations or subscriber acquisition."
          ]
        ]
      ],
      "case": "Authored case: a prospective audit request asks for paid-room originals and customer fills, but neither is supplied. The teaching card fills every documentation field while actual source, market data, fills and proof times remain null. Its conclusion is a specific evidence request, not a claim the service passed or failed a live test. Rights, purchase identity, collection interruptions and material commercial ties remain required before stronger independent language could be used.",
      "rows": [
        [
          "Access",
          "Exact offer and period",
          "Public is not paid"
        ],
        [
          "Rights",
          "Permitted inspection",
          "No fabricated archive"
        ],
        [
          "Failures",
          "Retained scope gaps",
          "Not discarded rows"
        ],
        [
          "Conclusion",
          "Claim-specific",
          "No blanket verified badge"
        ]
      ],
      "sources": [
        "cftc",
        "ots"
      ],
      "related": [
        "API-revocation-open-orders-and-recovery",
        "declared-population-and-missing-identifiers"
      ]
    }
  ],
  "workbook": {
    "path": "complete-call-population-and-revision-workbook.html",
    "classification": "authored education, not actual provider history"
  }
}
