L'électron rare
a96780ba7e
- 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.
1.5 KiB
1.5 KiB
ZeroClaw Integrations
ZeroClaw remains in scope as the local operator stack for Kill_LIFE.
This directory is synced by tools/ai/zeroclaw_stack_up.sh into
artifacts/zeroclaw/integrations/, then served by the follow UI.
Current integration posture:
ZeroClaw: kept as the local operator stack entrypoint.n8n: kept as an external automation bridge and workflow handoff surface.LangGraph: kept as an optional orchestration pattern, not the default runtime.AutoGen: kept as an optional multi-agent experimentation path.
These integrations are intentionally documented as operator runbooks. They are not required for the canonical repo-local stable path.
Operator posture:
ZeroClawruntime is started on demand viatools/ai/zeroclaw_stack_up.sh.zeroclaw.saillant.ccis the live runtime surface when the native stack is up.zeroclaw-docs.saillant.ccserves the ZeroClaw runbooks behind the authenticatededge-proxy.langgraph.saillant.ccserves the LangGraph runbook behind the authenticatededge-proxy.- When the local
ZeroClawruntime is stopped,zeroclaw.saillant.ccshould present an operator-friendly offline page instead of raw proxy errors.
Available runbooks: