Interlink Bridge Independent Research
Public Showcase
TP-CERT / Public Certification-Flow Demonstrator

See the certification flow.
Not the protected engine.

Choose a small public finite Gaussian scenario and follow it through a deliberately bounded certification workflow. The protected TP-CERT engine is represented as a black box: this page does not call it, expose it, or reproduce its proof machinery.

Deterministic public fixture Browser-only No engine/API call No protected mathematics Unsigned specimen receipt
01 / Selected public-safe interface views

What the protected system looks like.

Two selected screenshots show the product surface without exposing protected mathematics, proofs, keys, customer data or internal evidence payloads.

TP-CERT capability router and installed scenario packs overview
Interface view A · Capability router

Choose what you want to verify

The overview shows the governed entry point: supported verification goals are routed only to installed, proof-capable scenario packs instead of arbitrary execution.

Selected screenshot · public-safe presentation view · no engine access
TP-CERT matrix and invertibility certification scenario workflow
Interface view B · Concrete workflow

Bind the exact claim before certification

A concrete matrix scenario illustrates the product discipline: declared domain, exact input structure and explicit claim are visible before a certification action is permitted.

Selected screenshot · no result, proof or sensitive evidence disclosed
Why only these two? They explain product architecture and workflow without revealing proof internals. A third public screenshot should be added only when we have a deliberately sanitized Result / Evidence / Receipt view.
02 / Public specimen workflow

Finite scenario → protected boundary → bounded result

The purpose is architectural: to show what TP-CERT is meant to do without publishing how the internal certification core proves its obligations.

This is not a live TP-CERT service. The three scenarios and their specimen outcomes are pre-authored public fixtures. The page performs only local presentation and SHA-256 hashing of the selected public fixture. No request is sent to Interlink Bridge.
Step 1 · Public input

Finite Gaussian scenario

A small synthetic finite geometry expressed only through public-safe input metadata.

size=3 · family=public-fixture · shifts=small
Step 2 · Protected boundary

TP-CERT

Capability routing, exact obligations, certification logic, proof/evidence internals and protected research remain behind the boundary.

ENGINE / PROOF / KEYS
NOT EXPOSED
Step 3 · Public-safe projection

Bounded specimen result

A narrow result surface: status, scope, assumptions, nonclaims, input hash and release label — not the internal proof.

SPECIMEN RECEIPT
UNSIGNED / NOT LIVE
Ready. Select a scenario and run the specimen flow.
03 / Disclosure architecture

Three surfaces. Three different promises.

Keeping these surfaces separate is intentional. A visualization, a specimen flow and the protected certification system answer different questions.

Public numerical sandbox

Gaussian Explorer

Shows small finite Gaussian matrices and ordinary numerical sensitivity. It is a mathematical illustration, not a certification result.

Public architectural demonstrator

Certification Flow

Shows request and bounded-result semantics using deterministic fixtures. It does not execute or emulate the protected TP-CERT proof machinery.

Protected system

TP-CERT Engine

Internal certification infrastructure, protected capability bindings, evidence, proof material, keys and operational controls remain outside the public website.

04 / Why the boundary matters

“The software ran” is not the same as “this claim closed.”

TP-CERT is designed around bounded claims. A result is meaningful only together with the exact capability, admitted input family, assumptions, scope, evidence status and explicit nonclaims. The public demonstrator shows that structure without disclosing the protected derivation.

Public demonstration ≠ mathematical proof ≠ product access ≠ distribution authorization. No public page on this site grants access to the internal engine, proof archives, keys, restricted records, customer gateway or operational signing path.