<!doctype html>
<html lang="en-GB">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="theme-color" content="#071018">
<meta name="description" content="Telosieve questions infrastructure instructions before they are enforced, using corroborated evidence and explicit refusal.">
<meta property="og:title" content="Telosieve | Question the instruction">
<meta property="og:description" content="Corroborated control for desired-state systems. Evidence before confidence. Refusal is a valid result.">
<meta property="og:type" content="website">
<meta property="og:url" content="https://kabudu.github.io/telosieve/">
<meta property="og:image" content="https://kabudu.github.io/telosieve/assets/social-card-1200x630.png">
<meta name="twitter:card" content="summary_large_image">
<title>Telosieve | Question the instruction</title>
<link rel="icon" href="assets/favicon-32.png" sizes="32x32">
<link rel="stylesheet" href="styles.css">
</head>
<body>
<a class="skip-link" href="#main">Skip to content</a>
<header class="site-header">
<a class="brand" href="#top" aria-label="Telosieve home">
<img src="assets/telosieve-symbol.svg" width="42" height="42" alt="">
<span>Telosieve</span>
</a>
<nav aria-label="Primary navigation">
<a href="#how">How it works</a>
<a href="#integrations">Integrations</a>
<a href="#evidence">Evidence</a>
<a class="nav-cta" href="https://github.com/kabudu/telosieve">View source</a>
</nav>
</header>
<main id="main">
<section class="hero" id="top">
<div class="hero-copy">
<p class="eyebrow"><span></span> Read-only evaluation candidate</p>
<h1>Question the instruction<br><em>before enforcing it.</em></h1>
<p class="hero-lede">Telosieve examines infrastructure intent as evidence, not truth. It keeps authorities separate, tests what could be wrong, and refuses when the surviving evidence cannot justify one bounded result.</p>
<div class="hero-actions">
<a class="button primary" href="#how">See how it works <span aria-hidden="true">↓</span></a>
<a class="button secondary" href="https://github.com/kabudu/telosieve/blob/master/docs/EXTERNAL_ASSESSMENT.md">Assessment guide <span aria-hidden="true">↗</span></a>
</div>
<p class="boundary"><strong>Current boundary:</strong> evaluates and records decisions; never mutates Kubernetes, OpenTofu, Redis, PostgreSQL, or HTTP targets.</p>
</div>
<div class="hero-visual" aria-hidden="true">
<div class="orbit orbit-one"></div><div class="orbit orbit-two"></div>
<img class="hero-mark" src="assets/telosieve-symbol.svg" width="390" height="390" alt="">
<div class="signal signal-goal"><i></i><span>Goal</span></div>
<div class="signal signal-observation"><i></i><span>Corroborated observation</span></div>
<div class="signal signal-viability"><i></i><span>Viability</span></div>
<div class="result-chip"><b>REFUSE</b><span>when evidence diverges</span></div>
</div>
</section>
<section class="problem section-shell">
<p class="section-kicker">The control-plane assumption</p>
<div class="split-heading">
<h2>A valid signature does not make an instruction true.</h2>
<p>Reconcilers are designed to make reality match desired state. If that desired state is stale, compromised, inconsistent, or malicious, perfect reconciliation can faithfully create the wrong outcome. Telosieve investigates a stricter model: authenticate every source, trust none implicitly, and preserve uncertainty as a result.</p>
</div>
<div class="principle-grid">
<article><span>01</span><h3>Provenance is not truth</h3><p>Identity and signatures show where evidence came from. They do not prove that its content is correct.</p></article>
<article><span>02</span><h3>Refusal is useful</h3><p>When surviving explanations disagree, stopping with inspectable evidence is safer than inventing certainty.</p></article>
<article><span>03</span><h3>Bounds are part of correctness</h3><p>Inputs, hypotheses, execution time, outputs, and compatibility are explicitly limited and fail closed.</p></article>
</div>
</section>
<section class="architecture section-shell" id="how">
<div class="section-intro">
<p class="section-kicker">How it works</p>
<h2>One instruction. Several possible realities.</h2>
<p>Telosieve accepts a result only after it survives the declared faults and an independent viability check.</p>
</div>
<figure>
<img src="assets/telosieve-architecture.svg" width="1600" height="920" alt="Goal instructions, corroborated observations, and viability rules remain separate. Telosieve verifies provenance, tests declared fault hypotheses, independently checks every surviving plan, and emits either a bounded certificate or an explicit refusal while retaining evidence.">
<figcaption>Current integration modes are read-only. A certificate records a bounded evaluation result; it does not authorize production actuation.</figcaption>
</figure>
</section>
<section class="integrations section-shell" id="integrations">
<div class="section-intro">
<p class="section-kicker">Testable integrations</p>
<h2>Meet infrastructure where its evidence lives.</h2>
<p>Each integration uses narrow read-only permissions, explicit resource bounds, and mandatory observation quorum.</p>
</div>
<div class="integration-grid">
<a href="https://github.com/kabudu/telosieve/blob/master/docs/KUBERNETES_REAL_CLUSTER.md"><span class="integration-code">K8S</span><div><h3>Kubernetes</h3><p>Shadow snapshots and live four-read coherence checks against a real disposable API server.</p></div><b aria-hidden="true">↗</b></a>
<a href="https://github.com/kabudu/telosieve/blob/master/docs/OPENTOFU_PLAN.md"><span class="integration-code">TOFU</span><div><h3>OpenTofu</h3><p>Saved plan bytes through corroborating producers, with no backend credentials or apply path.</p></div><b aria-hidden="true">↗</b></a>
<a href="https://github.com/kabudu/telosieve/blob/master/docs/REDIS_INTEGRATION.md"><span class="integration-code">RDS</span><div><h3>Redis</h3><p>Bounded namespace collection through technically restricted read-only identities.</p></div><b aria-hidden="true">↗</b></a>
<a href="https://github.com/kabudu/telosieve/blob/master/docs/POSTGRESQL_INTEGRATION.md"><span class="integration-code">PG</span><div><h3>PostgreSQL</h3><p>Repeatable-read snapshots through SELECT-only roles, including concurrent-writer tests.</p></div><b aria-hidden="true">↗</b></a>
<a href="https://github.com/kabudu/telosieve/blob/master/docs/HTTP_JSON_INTEGRATION.md"><span class="integration-code">HTTP</span><div><h3>HTTP/JSON</h3><p>Fixed GET-only collection with bearer or TLS 1.3 mutual authentication and revocation checks.</p></div><b aria-hidden="true">↗</b></a>
<a href="https://github.com/kabudu/telosieve/blob/master/docs/INTEGRATION_CONTRACT.md"><span class="integration-code">V1</span><div><h3>Your system</h3><p>A versioned executable adapter and quorum response contract for further read-only integrations.</p></div><b aria-hidden="true">↗</b></a>
</div>
</section>
<section class="evidence section-shell" id="evidence">
<div class="evidence-panel">
<div>
<p class="section-kicker">Evidence, not theatre</p>
<h2>Negative findings stay visible.</h2>
<p>Telosieve retains refusals, exclusions, timeouts, unsupported cases, and known correlated-fault limits alongside successful results. Project-controlled testing is labelled as such. Independent operation and independent assessment are not implied.</p>
<a class="text-link" href="https://github.com/kabudu/telosieve/blob/master/docs/ADVERSARIAL_COVERAGE.md">Explore adversarial coverage <span aria-hidden="true">↗</span></a>
</div>
<dl>
<div><dt>4</dt><dd>supported evaluation modes</dd></div>
<div><dt>10</dt><dd>registered adversarial classes</dd></div>
<div><dt>0</dt><dd>target mutations in supported integrations</dd></div>
<div><dt>1</dt><dd>required outcome: agreement or refusal</dd></div>
</dl>
</div>
<div class="limits">
<h3>What Telosieve does not claim</h3>
<ul><li>A general proof of safety</li><li>Production-ready actuation</li><li>Independent organisational fault domains</li><li>Protection against arbitrary attackers</li><li>Legal name or mark clearance</li><li>Completed independent assessment</li></ul>
</div>
</section>
<section class="closing section-shell">
<img src="assets/telosieve-symbol.svg" width="116" height="116" alt="">
<p class="section-kicker">Inspect the mechanism</p>
<h2>Confidence should have to explain itself.</h2>
<p>Build the candidate locally, replay the retained scenarios, challenge the trust boundary, or implement a read-only integration.</p>
<div class="hero-actions">
<a class="button primary" href="https://github.com/kabudu/telosieve">Explore the repository <span aria-hidden="true">↗</span></a>
<a class="button secondary" href="https://crates.io/crates/telosieve">Install from crates.io <span aria-hidden="true">↗</span></a>
</div>
</section>
</main>
<footer><span>Telosieve</span><p>Question the instruction before enforcing it.</p><p>Apache-2.0 · Evaluation software · No telemetry</p></footer>
</body>
</html>