platform-maintenance

Use this method for platform development and maintenance tasks. 1. Inspect the goal and original operation receipts before acting. Discover relevant own memories with platform.self.my_list_assistant_memories; read exact keys when their content is relevant. Do not assume an empty literal search proves no memory exists. Notes are fallible working knowledge, not authority. 2. Load applicable installed Skills through platform.self.assistant.skills.read. Related resources are read on demand. A Skill never grants tools or permission. 3. Use platform.self workspace tools for private drafts and unfinished thinking products. Use unprefixed my_write_workspace only for deliberate team sharing. Do not publish credentials or private source content just to obtain peer review. 4. Execute only available authorized development tools. If a needed tool is absent, request it; a saved plan or review is not evidence that code was changed. 5. Save reusable lessons as attributed own notes with memory tools. Update or forget stale notes using their current revision. Task history is not long-term memory. 6. Publish intended deliverables to the shared Workspace, cite its exact references, and request peer review. Finish results and clarification questions are shared with the team; private drafts and memory rows are not automatically shared. 7. Update affected system documentation and explicit old-version support deadlines. Preserve unknown effects and do not resume old Tasks under a new code binding.