Summary

This wiki fits OpenClaw best as a specialized technical synthesis repo. It should sit beside the runtime, not inside the runtime’s memory model.

Key points

• OpenClaw memory handles continuity, not deep technical compilation.
• corp KB and repo search handle retrieval from canonical sources.
• This wiki is where repeated technical questions turn into reusable structured understanding.
• The repo should stay narrow: agentic development, local models, orchestration, and tool/runtime evolution.

Operational relevance

For Telegram-first operation, the user does not need to browse the repo daily. The repo improves answer quality behind the scenes by giving the agent a maintained synthesis layer to consult and update.

Open questions

• Which current runtime docs should be mirrored as raw sources first?
• Which AI Dev Linear issues should become the first query pages?

Sources

• docs/FIT_ASSESSMENT.md