# ReMe - Doramagic AI Context Pack > Purpose: pre-work context for the user's host AI. This pack does not prove that the project has been installed, run, or validated. ## Project - canonical_name: `agentscope-ai/ReMe` - capability: ReMe: Memory Management Kit for Agents - Remember Me, Refine Me. - expected_user_outcome: ReMe: Memory Management Kit for Agents - Remember Me, Refine Me. ## Operating Boundaries - Do not claim that the project has been installed, run, called through an API, or used on local files unless separate evidence proves it. - Project facts must come from repo evidence, Claim Graph, or explicit source references. - When a capability is not verified, mark it as unverified instead of completing it as fact. - publish_status: `publishable` - blocking_gaps: none --- ## Doramagic Context Augmentation The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints. ## Human Manual Outline Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph. Host AI hard rules: - Do not treat page titles, section order, summaries, or importance values as factual project evidence. - When explaining the Human Manual outline, state that it is only a reading route or salience signal. - Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph. - **Overview & Memory-as-File Architecture**: importance `high` - source_paths: README.md, reme/reme.py, reme/application.py, reme/components/application_context.py, reme/schema/application_config.py - **Automatic Memory Pipeline (auto_index, auto_memory, auto_resource, auto_dream, proactive)**: importance `high` - source_paths: reme/steps/evolve/auto_memory.py, reme/steps/evolve/auto_memory.yaml, reme/steps/evolve/auto_resource.py, reme/steps/evolve/auto_resource.yaml, reme/steps/evolve/dream/extract.py - **Workspace Operations, CLI, and Agent Integration**: importance `high` - source_paths: reme/steps/file_io/read.py, reme/steps/file_io/write.py, reme/steps/file_io/edit.py, reme/steps/file_io/delete.py, reme/steps/file_io/move.py - **System Components, Configuration & Deployment**: importance `high` - source_paths: reme/components/base_component.py, reme/components/component_registry.py, reme/components/service/base_service.py, reme/components/service/http_service.py, reme/components/service/mcp_service.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `8c1d348468d48bcf1d2a76eb41cba749b4a65c95` - inspected_files: `README.md`, `pyproject.toml`, `docs/old/auto_cognition_design.md`, `docs/old/auto_consolidate_design.md`, `docs/old/auto_dream_design.md`, `docs/old/auto_memory_design.md`, `docs/old/auto_recall_design.md`, `docs/old/background_backup.md`, `docs/old/reme_design.md`, `docs/old/reme_design_v2.md`, `docs/old/reme_index.md`, `docs/old/reme_report.md`, `docs/old/reme_resource.md`, `docs/old/reme_scene.md`, `docs/old/structure.md`, `docs/old/todo.md`, `docs/zh/auto_dream.md`, `docs/zh/auto_link.md`, `docs/zh/auto_memory.md`, `docs/zh/auto_resource.md` Host AI hard rules: - Without repo_clone_verified=true, do not claim that the source code has been read. - Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts. - Without quick_start_verified=true, do not claim that the Quick Start path has run successfully. ## Doramagic Pitfall Constraints These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes. ### Constraint 1: Security or permission risk requires verification - Trigger: Project evidence flags a security or permission risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/agentscope-ai/ReMe/issues/280 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: Capability evidence risk requires verification - Trigger: README/documentation is current enough for a first validation pass. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: capability.assumptions | https://github.com/agentscope-ai/ReMe - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Maintenance risk requires verification - Trigger: Project evidence flags a maintenance risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: evidence.maintainer_signals | https://github.com/agentscope-ai/ReMe - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Security or permission risk requires verification - Trigger: no_demo - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: downstream_validation.risk_items | https://github.com/agentscope-ai/ReMe - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Security or permission risk requires verification - Trigger: no_demo - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: risks.scoring_risks | https://github.com/agentscope-ai/ReMe - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: Security or permission risk requires verification - Trigger: Project evidence flags a security or permission risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/agentscope-ai/ReMe/issues/275 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: Maintenance risk requires verification - Trigger: issue_or_pr_quality=unknown。 - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: evidence.maintainer_signals | https://github.com/agentscope-ai/ReMe - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 8: Maintenance risk requires verification - Trigger: release_recency=unknown。 - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: evidence.maintainer_signals | https://github.com/agentscope-ai/ReMe - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.