telemetry-lab is a local, file-based detection workflow lab. It is organized around committed sample inputs, deterministic demo pipelines, and reviewer-facing artifacts.
flowchart TD
Inputs["Committed sample inputs<br/>JSONL, CSV, YAML configs"]
CLI["Unified CLI<br/>telemetry-lab run window<br/>telemetry-lab run ai-assisted<br/>telemetry-lab run dedup<br/>telemetry-lab run config-change<br/>telemetry-lab run cloud-iam<br/>telemetry-lab verify"]
Window["telemetry-window-demo<br/>normalize -> windows -> features -> alerts"]
AI["ai-assisted-detection-demo<br/>rules -> cases -> JSON-only drafting"]
Dedup["rule-evaluation-and-dedup-demo<br/>raw hits -> cooldown -> suppression reasons"]
Config["config-change-investigation-demo<br/>config changes -> bounded evidence correlation"]
CloudIAM["cloud-iam-change-investigation-demo<br/>CloudTrail-like events -> IAM change signals"]
Artifacts["Reviewer artifacts<br/>CSV, JSON, JSONL, Markdown, PNG<br/>run_manifest.json"]
Review["Reviewer inspection<br/>README, reviewer path, reviewer pack, tests"]
Inputs --> CLI
CLI --> Window
CLI --> AI
CLI --> Dedup
CLI --> Config
CLI --> CloudIAM
Window --> Artifacts
AI --> Artifacts
Dedup --> Artifacts
Config --> Artifacts
CloudIAM --> Artifacts
Artifacts --> Review
- Detection decisions stay deterministic and inspectable.
- The Python project identity is
telemetry-lab, the primary import package istelemetry_lab, andtelemetry_window_demois compatibility-only. - All primary local runs go through
telemetry-lab run <demo>and writerun_manifest.jsonwithexecution_mode: synthetic-local. - The AI-assisted demo is limited to bounded JSON-only case drafting.
- Bounded correlation stays inside fixed time windows, fixed entity or scope keys, and fixed event families or rule-local family sets.
- Artifacts are file-based and suitable for local regeneration or GitHub review.
- Artifact names are reviewer-visible contracts during the v1 reviewer contract stabilization phase.
- The repository does not provide production monitoring, real-time ingestion, dashboards, alert routing, case management, autonomous response, or final incident verdicts.
- Notebooks are auxiliary exploration only. The core reviewer pipeline is headless: CLI commands, fixed inputs, committed artifacts, schema validation, and tests.
| Demo | Boundary |
|---|---|
telemetry-window-demo |
Converts raw events into window features and alerts; does not become a live stream processor. |
ai-assisted-detection-demo |
Drafts constrained summaries from deterministic cases; does not decide incident outcomes or call tools. |
rule-evaluation-and-dedup-demo |
Explains cooldown and suppression behavior; does not route alerts. |
config-change-investigation-demo |
Correlates risky changes with bounded local evidence; does not monitor live infrastructure. |
cloud-iam-change-investigation-demo |
Reviews synthetic CloudTrail-like IAM and cloud-control-plane signals; does not connect to AWS or assert incident verdicts. |
Primary commands:
telemetry-lab run window --config configs/default.yaml
telemetry-lab run ai-assisted
telemetry-lab run dedup
telemetry-lab run config-change
telemetry-lab run cloud-iam
telemetry-lab verifyCompatibility commands remain available for older notes and external links:
python -m telemetry_window_demo.cli run --config configs/default.yaml
python -m telemetry_window_demo.cli run-ai-demo
python -m telemetry_window_demo.cli run-rule-dedup-demo
python -m telemetry_window_demo.cli run-config-change-demo
python -m telemetry_window_demo.cli run-cloud-iam-change-demoThe compatibility layer does not define a separate product identity.