Bounded origin context
Identify the earliest plausible origin-related candidate found inside the history window examined. A bounded candidate is not presented as definitive proof of the creator.
foundOS / signal terminal
Deep Forensics extends the basic token scan with staged historical investigations. It looks for origin-context, funding, related-mint, launchpad and wallet-activity clues while explicitly separating verified launch-adjacent evidence from bounded historical observations.
Blockchain history can be incomplete, rate-limited or ambiguous when reconstructed from public RPC and market context. foundOS uses bounded language so the interface does not turn an earliest observed item into an unsupported claim about the true beginning of a token.
Identify the earliest plausible origin-related candidate found inside the history window examined. A bounded candidate is not presented as definitive proof of the creator.
Inspect available funding relationships around the candidate context and label what was observed versus what could not be resolved.
Look for launch-platform evidence and report the platform, state and confidence rather than forcing every token into a launchpad classification.
Inspect transaction and wallet activity around the bounded sample, then only score launch-adjacent behavior when the timing evidence supports that interpretation.
foundOS is designed around explicit evidence states. These terms describe how the report avoids turning partial data into false certainty.
Start with Fast Scan, then use Deep Forensics when origin, funding or launch-context questions matter enough to investigate further.