KSP — Kush Secure Protocol

Core & Lifecycle

RFC § 16.2 — Workspace Isolation

Purpose

Initialize a new KSP workspace configuration in the current directory (`ksp.toml`).

Syntax

Command-line specification

bash / powershell

ksp init [DIRECTORY] [OPTIONS]

Arguments

Argument	Description
[DIRECTORY]	Optional target directory to initialize (defaults to current working directory).

Options & Flags

Option Flag	Description
--profile <TYPE>	Preset configuration template: `default`, `high-security`, `low-latency`, or `embedded`.
--force, -f	Overwrite existing `ksp.toml` configuration if already present.
--json	Output initialization status as structured JSON.

Example Usage

Example command

ksp init ./my-project --profile high-security

Expected Output

════════════════════════════════════════════════════════════
══            KSP Workspace Initialization                ══
════════════════════════════════════════════════════════════
  [+] Directory:    C:\projects\my-project
  [+] Profile:      High-Security (ChaCha20-Poly1305 + Strict Replay Window)
  [+] Created file: ksp.toml (248 bytes)
  [+] Created dir:  .ksp/certs/

  ✔ Workspace initialized successfully. Run `ksp doctor` to verify environment.

Implementation Notes

Creates a standard `ksp.toml` configuration file along with a local `.ksp/` cache folder for session state and certificate verification material.

Related CommandsView All 50 Commands →

ksp new

ksp doctor

ksp config

CLI Installation Guide· Quick Start Workflow· GitHub Source Repository