القائمة
Compatibility note for manually connecting OpenClaw to AITP v5; no dedicated OpenClaw lifecycle installer is release-supported.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use after AITP v5 routing has claimed a theoretical-physics task; continue the work through typed records, validation gates, and summary regeneration instead of ad hoc notes.
First-run setup assistant for the AITP Research Protocol Kimi Code plugin: detect setup mode, ask for repo/topics paths, persist configuration, and explain when to reload Kimi Code.
HIGHEST PRIORITY - Use for ANY theoretical-physics research, topic continuation, exploratory physics discussion, old-knowledge Q&A tied to project topics, prior topic progress/status inquiries, idea steering, paper learning, derivation work, validation planning, or study of physical systems. Classify request intensity before deciding read-only or write-capable flow.
Continue an AITP v5 theoretical-physics topic through typed claims, source provenance, artifacts, evidence, validation gates, human checkpoints, and trust-controlled memory.
Enter the local AITP v5 research protocol from Codex for theoretical-physics work, topic continuation, prior progress checks, paper reading, derivations, validation, and trust-controlled research memory.
Compatibility pointer for the Claude Code AITP v5 adapter; active templates live under deploy/templates/claude-code.
| name | aitp-runtime |
| description | Compatibility note for manually connecting OpenClaw to AITP v5; no dedicated OpenClaw lifecycle installer is release-supported. |
OpenClaw is not a default AITP research host and currently has no dedicated v5 lifecycle installer or verified automatic hook path. A manual integration may connect only to:
brain/v5/native_mcp.pyaitp_v5_*Such an integration must use bounded v5 recovery/context reads and explicit typed writes. It must not enable legacy L0-L4 writes, auto-promote trust, install Skills, or claim host lifecycle support that has not passed a host fixture.
Use Codex for the supported default interactive workflow.