The capabilities below combine architectural responsibilities and specific local evidence. Each links to the scope that supports it.
Cryptocurrency markets, domestic and overseas equities, and listed futures and options use market-specific exchange and broker paths. Coverage follows each system and supported product, rather than a single host label.
Reviewed implementation scope and owner-confirmed host roles
Inspect the supporting material →Independent engines retain their own account context and permission boundary. Shared support does not create one universal execution gate.
Architecture and observed integration limits
Inspect the supporting material →Inference supplies proposals. Permission must be attributable, scoped and readable by the path that consumes it.
Design model; selected settings have dated observations
Inspect the supporting material →Source linkage, observation contracts and point-in-time provenance determine whether a research input is acceptable.
A dated readiness run recorded a refusal to continue
Inspect the supporting material →Local counterexamples exercise initialization failure, unreadable output and incomplete observations.
Scoped repairs are tested; operating adoption is separate
Inspect the supporting material →Reused values retain their original observation time. Missing or invalid evidence is not counted as a verified result.
Local producer and consumer behavior
Inspect the supporting material →Results retain source pins, original failures and the measured population. Negative controls test whether verification can reject broken behavior.
Internal technical evidence with explicit reproduction limits
Inspect the supporting material →A capability description is not certification of every live path. The evidence pages distinguish design, tested local behavior and natural operating observations.