Four kinds of information
Personality: droid identity, backstory and speaking style.
Build knowledge: wiki, manuals, configured components and verified capabilities.
Memory: approved preferences and corrections, with edit and forget controls.
Live status: timestamped Cortex readings; stale readings remain clearly marked.
Proposed flow: voice question → relevant wiki/status lookup → answer. New entries become available through the lookup connector without retraining the language model. Learned preferences stay separate from verified build facts.
AIPI: documented features, pending connector
AIPI documents character editing, conversation memory, knowledge uploads and custom MCP tools. Its setup guide says profile changes take effect on the next conversation. Wi-Fi/cloud AI is required. Automatic knowledge-base uploads and mid-conversation refresh are not verified.
Our plan is a read-only knowledge/status connector first, then user-controlled memory and validated command tools. This is a design; it is not installed on a device.
Setup guide · Changelog · Reference manual“What batteries are installed?” looks up configuration and current telemetry. “Remember my droid’s name” saves a preference. “Open the periscope” uses a separate command tool that checks the configured mechanism and controller readiness.
JSON for our app; AIPI import compatibility is not confirmed.