CLTK v2.2 is a modular, offline-first PowerShell toolkit for engineers and IT professionals. It bundles a signed launcher, diagnostics, reporting templates, and an add-on framework in a single self-contained folder.
Working offline is the default. Verify integrity first, then run tools intentionally using safety modes.
🔎 What you will do in this module
- 🧰 Extract CLTK v2.2 to a trusted local folder and handle MOTW safely
- 🟦 Launch the signed PowerShell launcher and understand menu sections
- 🛡️ Run integrity verification and interpret PASS, WARN, and FAIL correctly
- 🧪 Validate reports, templates, diagnostics, and logging outputs
- 🧩 Understand the add-on system basics, including install and uninstall behavior
- ✅ Complete the full v2.2 validation checklist with button-based acknowledgements
📚 Historical reading
- Historical CLTK v2.0 Onboarding and Validation
- PASS, WARN, FAIL: Understanding CLTK Integrity Results
The v2.0 onboarding article is retained as historical background. This module is also historical and superseded. Use the Knowledge Base for current guidance.
✅ Key takeaway
By the end, you will have verified an authentic CLTK v2.2 release, run the launcher safely, generated outputs, and confirmed a working offline environment.
🧭 Guided Setup and Validation
Follow the sections in order. Use the completion buttons to track progress locally in your browser. These buttons do not certify anything. They help you confirm you completed each step.
Module outline
Progress
Stored in localStorage for this browser only.
1) Introduction to CLTK v2.2
CLTK v2.2 is designed to run locally from an extracted folder. It includes a PowerShell launcher, integrity verification artifacts, Outputs and Logs folders, and an add-on framework under Tools\.
When to use it
- When you need offline diagnostics and structured outputs on a Windows host
- When you want repeatable integrity checks before executing scripts
- When you need templates and report generation stored locally
2) Preflight Setup
2.1 Extract to a trusted local folder
Extract the .7z archive using 7-Zip into a clean local path. Avoid protected folders like Program Files and avoid network-mounted locations.
2.2 Handle MOTW (Mark-of-the-Web)
If Windows flags downloaded content as blocked, unblock via file Properties when needed. You can also scan for blocked scripts using launcher option [B].
2.3 Run in a controlled PowerShell session
If your environment restricts script execution, use a temporary process-scoped policy. This does not modify system-wide settings and resets when PowerShell closes:
Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned2.4 Confirm folder structure
Expect folders such as Launcher, Tools, Templates, Logs, Outputs, catalog, and Certs.
Historical Preflight dependency (superseded)
This earlier workflow recommended CLTK Preflight Check. That recommendation is retained as historical context, not a current onboarding dependency.
For current setup and troubleshooting guidance, use the Knowledge Base.
3) Running the Launcher
3.1 First launch
cd "C:\Path\To\Constant_Labs_Tactical_Kit_v2.2\Launcher"
.\tactical_kit_launcher.ps13.2 Menu overview
Confirm you can see the main menu sections, including diagnostics, templates, logs and outputs, integrity and preflight, add-ons, and support.
3.3 Safety modes (WhatIf and Confirm)
- WhatIf simulates actions without making changes
- Confirm prompts you before actions that change state
4) Integrity Verification
4.1 Verify Integrity
Use [V] Verify Integrity. Expect mutable locations like Logs and Outputs to change during normal use.
4.2 PASS, WARN, FAIL
- PASS: verification completed successfully.
- WARN: often references expected changes (Logs, Outputs, state file). Treat as informational when scoped to mutable locations.
- FAIL: investigate the cause. Integrity mismatches are a stop signal. Certificate trust failures in v2.2 are contextual.
📖 Want a deeper explanation?
Read the companion article: PASS, WARN, FAIL: Understanding CLTK Integrity Results
4.3 Trusted vs NotTrusted certificate
CLTK v2.2 scripts are signed using a Constant Labs® code-signing certificate. In some environments, Windows may report the signature as valid but not trusted. A NotTrusted chain can be acceptable in v2.2. Trusting the certificate is optional.
For the offline reference, review Quickstart.md in the Docs/ directory included with the CLTK v2.2 package.
This earlier workflow used CLTK Preflight Check. For current environment verification, use the Knowledge Base; Preflight is not presented here as a current dependency.
If you did not import the certificate, leave the optional button unchecked. NotTrusted is acceptable in v2.2.
5) Core Tool Validation
5.1 Reports and templates
Open Templates and generate outputs using the launcher options. Validate that outputs land in Outputs and activity is recorded to Logs.
5.2 Diagnostics
Run diagnostics like Network Discovery and Log Search. Validate execution and output handling, not a specific scan outcome.
6) Add-on System Basics
Use [A] to detect installed add-ons, [N] to install from ZIP, and [U] to uninstall with backup behavior.
7) Completion Checklist (CLTK v2.2)
Use the buttons to confirm you completed each group of steps.
Preflight baseline
Extraction, MOTW handling, process execution policy, launcher start, and first integrity run.
Launcher functionality
Menu visible, safety modes toggle, and header state updates.
Reports and templates
Templates open and report outputs are created.
Diagnostics and logs
Diagnostics run and logs and outputs are produced.
Integrity and MOTW
Integrity verification, expected WARN interpretation, MOTW scan behavior.
Add-ons and docs
Add-on install and uninstall flow validated and docs accessible.
8) Final Summary
You have verified an authentic CLTK v2.2 release, validated core workflows, and confirmed a working offline environment.
What to do next
- Keep the kit in a stable local path for repeatable runs
- Re-run [V] Verify Integrity after moving the kit
- Use WhatIf when you want preview-first behavior
- Use Confirm in sensitive environments
Current CLTK guidance
This archived module is no longer the current onboarding system. Use the Knowledge Base for current documentation, installation and verification guidance.
Tip: Including your Windows version and certificate trust state helps resolve issues faster.
Reminder: This module is instructional. It does not grant compliance certification or audit approval.