Harness — the workspace control plane

The harness is the control plane of a workspace. A workspace need not be code: it can be a company, an ops desk, a legal archive, a personal knowledge vault. Whatever it is, the harness is the durable apparatus that keeps it operable and legible, made of three parts:

• 01-TOOLS/<PROVIDER>/ — the operational tooling layer. One folder per external provider, co-locating credentials (.env) with the scripts that consume them. Each tool ships a working test_connection against the real API.

• 02-DOCS/ — the Karpathy chaos→knowledge engine: a domain-agnostic LLM wiki (inbox/, raw/, raw/worklog/, wiki/ with its index.md / log.md / gaps.md / scores.json and .base views), embedded in this skill — no external sub-skill required.

  Two on-ramps feed it. Ingest: the user drops any file in any format into inbox/, and the Auto-Ingest Sweep extracts, classifies, cross-links and compiles it — then goes for a walk, discovering un-ingested documents anywhere in the workspace, bounded by .rscignore (baseline: references/ingest-ignore-defaults.md) and de-duplicated through the wiki/.ingested.json ledger. Worklog: every meaningful session of work is itself a raw source in raw/worklog/, captured on PreCompact/SessionEnd, at a commit milestone, or by the daily curation pass.

  Ingest relocates, never deletes: a loose file at the workspace root moves into raw/; a file inside a folder the user maintains is copied, and consolidating that folder needs explicit consent.