# continuum - 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: `nikhilkagita04/continuum` - capability: Context dies when you switch apps. Continuum is an open, local-first memory layer for your Mac — it remembers what you do in every app (on-device) and hands it to any AI over MCP. Ask Claude what you were just doing in another tab, and it knows. - expected_user_outcome: Context dies when you switch apps. Continuum is an open, local-first memory layer for your Mac — it remembers what you do in every app (on-device) and hands it to any AI over MCP. Ask Claude what you were just doing in another tab, and it knows. ## 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. - **Introduction and Quickstart**: importance `high` - source_paths: README.md, package.json, bin/continuum.mjs, CONTRIBUTING.md - **The Four-Stage Pipeline**: importance `high` - source_paths: daemon/pipeline.mjs, daemon/stage1/capture.swift, daemon/stage1/screen.swift, daemon/stage1/files.mjs, daemon/stage2/segmenter.mjs - **Capture Quality, Noise Filtering, and Self-Exclusion**: importance `high` - source_paths: daemon/stage1/capture.swift, daemon/stage1/screen.swift, daemon/stage4/distill.mjs, daemon/pipeline.mjs, docs/architecture/capture-quality.md - **MCP Server, Graph Sidecar, and Custom Tools**: importance `medium` - source_paths: daemon/mcp-server.mjs, backend/graphiti/sidecar.py, backend/graphiti/README.md, examples/claude-desktop.json, examples/standup.mjs ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `3f5b20bb92f2501cf42e92661b7925bfdacd941d` - inspected_files: `README.md`, `package.json`, `docs/architecture/capture-quality.md`, `docs/architecture/ingestion-pipeline.md`, `examples/claude-desktop.json` 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: Configuration risk requires verification - Trigger: Project evidence flags a configuration 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: capability.host_targets | https://github.com/nikhilkagita04/continuum - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: Configuration risk requires verification - Trigger: Developers should check this configuration risk before relying on the project: Capture: LLM structuring pass to attribute episodes (who said what) - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Capture: LLM structuring pass to attribute episodes (who said what). Context: Source discussion did not expose a precise runtime context. - Why it matters: Developers may misconfigure credentials, environment, or host setup: Capture: LLM structuring pass to attribute episodes (who said what) - Evidence: failure_mode_cluster:github_issue | https://github.com/nikhilkagita04/continuum/issues/2 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Configuration risk requires verification - Trigger: Developers should check this configuration risk before relying on the project: Capture: emit AX focused-element as clean user-authored text - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Capture: emit AX focused-element as clean user-authored text. Context: Observed when using macos - Why it matters: Developers may misconfigure credentials, environment, or host setup: Capture: emit AX focused-element as clean user-authored text - Evidence: failure_mode_cluster:github_issue | https://github.com/nikhilkagita04/continuum/issues/1 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: 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/nikhilkagita04/continuum - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: 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/nikhilkagita04/continuum - 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: 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/nikhilkagita04/continuum - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: 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/nikhilkagita04/continuum - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 8: 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/nikhilkagita04/continuum/issues/2 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 9: 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/nikhilkagita04/continuum/issues/1 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 10: Capability evidence risk requires verification - Trigger: Developers should check this conceptual risk before relying on the project: Capture: exclude Continuum's own windows (dashboard/terminal) from capture - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: Developers may hit a documented source-backed failure mode: Capture: exclude Continuum's own windows (dashboard/terminal) from capture - Evidence: failure_mode_cluster:github_issue | https://github.com/nikhilkagita04/continuum/issues/4 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.