JC·HARNESS

Docs & API

Public-safe documentation and machine-readable surfaces.

OpenAPI

Route contract, auth boundary, and run APIs.

MCP

JSON-RPC metadata and tool registry.

llms.txt

Concise AI-reader summary of the product boundary.

Responsible-Use Baseline

  • Authorized testing only.
  • Only test systems you own or have explicit written permission to assess.
  • The operator is responsible for target authorization and scope.
  • No anonymous active testing against arbitrary targets.
  • No denial-of-service testing unless explicitly scoped and separately enabled.
  • No destructive testing.

Getting Started

implemented

Jean-Claude setup flow, execution modes, and first dry-run path.

Open surface

Responsible Use

implemented

Authorization and safety requirements before any real run.

Open surface

Safety

implemented

No remediation, no PRs, no branch pushes, no anonymous active scanning.

Open surface

Modes

implemented

api-multi-model, local-client, local-model, and multi-mode behavior.

Open surface

Pipeline

implemented

RECON, HUNT, VALIDATE, GAPFILL, TRACE, REPORT, SCORECARD.

Open surface

Integrations

implemented

Vercel, Sandbox, AI Gateway, Neon, Trace, Docs, Sheets, Files.

Open surface

Jean-Claude boot and setup wizard

implemented

Represented in the web cockpit as real code-backed capability, protected operation, or precise manual/unconfigured state.

Dry-run and real-run selection with dry-run default

implemented

Represented in the web cockpit as real code-backed capability, protected operation, or precise manual/unconfigured state.

Execution modes: api-multi-model, local-client, local-model, multi-mode

implemented

Represented in the web cockpit as real code-backed capability, protected operation, or precise manual/unconfigured state.

Model roster: fable5, opus48, gpt55

implemented

Represented in the web cockpit as real code-backed capability, protected operation, or precise manual/unconfigured state.

Key resolution status for env, AWS SSM, key file, and Vercel AI Gateway

implemented

Represented in the web cockpit as real code-backed capability, protected operation, or precise manual/unconfigured state.

Target base URL, repositories, trust boundaries, and allowed-host validation

implemented

Represented in the web cockpit as real code-backed capability, protected operation, or precise manual/unconfigured state.