AITP-Research-Protocol

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.

Compatibility pointer for the Codex AITP v5 runtime; canonical Codex skills and plugin assets live under deploy/codex and plugins/aitp-research-protocol.

Compatibility note for manually connecting OpenClaw to AITP v5; no dedicated OpenClaw lifecycle installer is release-supported.

Reference note for the OpenCode adapter surface; the active bootstrap lives in ~/.config/opencode/plugins/aitp.js and reuses the canonical v5 skill content.

First-run setup assistant for the AITP Research Protocol Codex plugin: detect setup mode, ask for repo/topics paths, persist configuration, and explain when to restart Codex.

Enter the local AITP kernel from OpenClaw through the bundled plugin tools or the installed `aitp` CLI so the run stays auditable, resumable, and conformance-checked.