Platform
The pipeline that proves what your model learned from.
Every sample your model trains on passes through one gate: its source judged, its content checked, its verdict sealed. This is the machinery, end to end.
01 · End to end
One straight line, five stops.
Agentiks deploys from a Helm chart onto a streaming backbone (Kafka and Flink) inside your cluster. Data flows through it in one direction, and every stop leaves evidence.
02 · The trust engine
Grooming stops working when trust decays.
Five behavioral signals feed each source’s score, and recent behavior outweighs old history on a half-life of roughly three weeks. The classic attack, months of clean submissions to build trust and then a flip to poison, buys an asset that evaporates as fast as it turns hostile.
Regaining a tier costs more than losing it, so a source hovering at a boundary cannot flap on noise.
A lone detector family cannot destroy a source: penalties stay capped until an independent signal corroborates.
A behavioral alarm opens a case. Clean escalated inspection refunds most of it; confirmation makes it permanent. Never all of it, so probing costs.
When a ring duplicates an honest source's content, per-member victim scoring spares the source that got copied.
03 · Check the sample
Bad data has a geometry.
Every sample is embedded (mapped into a space where similar content sits close together) and examined for what eyes cannot see: content that drifts from the clean reference, near-duplicates coordinated across supposedly independent sources, and clusters that change shape over time.
Each sample gets a verdict: pass, quarantine, or reject, with an escalation path for deeper checking. Detections flow back into the source’s trust score, so content evidence and behavioral evidence reinforce each other.
04 · Runs in your cluster
Nothing leaves. Nothing phones home.
One Helm chart into your cluster. Air-gapped works; there is nothing to call home to.
Point a training pipeline's ingestion at the gate in shadow mode: observing and scoring, never blocking.
Detectors and trust thresholds calibrated on your real telemetry, with the founders in the loop.
Calibration defaults and detector internals are shared under evaluation, not published: printed thresholds are a gaming manual for the adversaries this system exists to catch.
05 · Operate and prove
Day two is a console, not a spreadsheet.
A control plane reads the whole pipeline live: trust trajectories per source, the verdict stream, and the sealed-ledger status. Underneath, every consequential event sits in an append-only, hash-chained ledger with Merkle checkpoints that an offline verifier can prove intact.
When an auditor asks, you export integrity certificates: per-sample attestations with inclusion proofs, in standard formats (in-toto, SLSA, CycloneDX).