TINLANCE / PROOF

Evidence before customer-story theatre.

We publish engineering, research and open-source evidence with explicit scope. Customer case studies are reserved for real engagements with permission to publish.

CASE-STUDY TAXONOMY

Different evidence types should look different.

Every study identifies its type, status, product, problem, approach, evidence, result and limitations. Synthetic evaluation is never presented as customer success.

02Published evidence records

0Fabricated customer studies

6Supported case-study types

OPEN-SOURCE VALIDATIONStatus: Validated

ThreatFade early QUIC C2 validation

Product: ThreatFade · Cybersecurity

Problem: Adversarial C2 activity can reduce observable signals intentionally.

Approach: Use entropy/statistical deviation analysis and evidence preservation to identify signal reduction in encrypted traffic.

Evidence: Historical, independently documented early MVP validation in the public ThreatFade repository.

Result: The documented test population reports a Merlin QUIC z-score of 14.76 and 0% false positives across the tested MVP populations.

Scope / limitations: Early MVP test population; 490,847 documented packets. Historical experimental evidence. It does not establish universal accuracy, enterprise production performance, certification, or customer deployment.

View source

ENGINEERING CASE STUDYStatus: Tested

FDE Mastery platform engineering

Product: FDE Mastery

Problem: Enterprise AI workflows need explicit domain contracts, controls, evaluation and evidence.

Approach: Build a reusable platform with eight domain contracts, trust-plane controls, durable workflows and evaluation boundaries.

Evidence: Public repository documentation, automated test suites and documented engineering history.

Result: Repository evidence covers eight domains, production Docker/runtime smoke, eight-domain API E2E and an 800-case synthetic corpus.

Scope / limitations: Engineering repository evidence; not eight customer deployments. Does not establish customer production outcomes or independent assurance.

View source

NEXT STEP

Validate your own system.

Move from public engineering evidence to an environment-specific technical assessment.

Book an assessment