Files

T

History

L'électron rare a96780ba7e Add French documentation for standards, integrations, cockpit, evaluations, and hardware tools

- Created README_FR.md files for various standards and profiles in the `standards` directory, detailing conventions and usage.
- Added integration documentation for ZeroClaw, AutoGen, LangGraph, and n8n in the `tools/ai/integrations` directory, outlining their roles and usage.
- Introduced a comprehensive README_FR.md for the `tools/cockpit` directory, detailing operator commands and health-check routines.
- Added a README_FR.md for the `tools/evals` directory, providing a benchmark framework for electronic prompts.
- Created a README_FR.md for the `tools/hw/schops` directory, explaining CLI operations for schematic management.
- Added README_FR.md files for the `web` directory and its `project/pcb` subdirectory, outlining the web application structure and PCB viewer inputs.

2026-03-25 01:08:52 +01:00

index.html

ai(zeroclaw): publish on-demand operator runtime

2026-03-09 00:46:53 +01:00

README_FR.md

Add French documentation for standards, integrations, cockpit, evaluations, and hardware tools

2026-03-25 01:08:52 +01:00

README.md

Add French documentation for standards, integrations, cockpit, evaluations, and hardware tools

2026-03-25 01:08:52 +01:00

README.md

LangGraph Runbook

LangGraph stays in scope as an optional orchestration layer around ZeroClaw.

Use it when you want:

explicit graph-shaped control flow
checkpointed or resumable orchestration
a graph runtime separated from the canonical repo workflows

Current posture in Kill_LIFE:

ZeroClaw remains the local operator stack.
LangGraph is retained as an integration pattern, not as the default runtime path.
No LangGraph service is wired into the main mascarade stack by default.

Recommended role split:

ZeroClaw: local gateway, operator UX, prompts, pairing, follow UI
LangGraph: optional orchestration graph for complex flows
repo workflows / evidence: canonical tracked outputs

If this path is reactivated, add the concrete graph app or runner as tracked artifacts in tools/ai/ or a dedicated submodule, then link it from here.