# Causal-Memory-Layer - 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: `safal207/Causal-Memory-Layer` - capability: CML (Causal Memory Layer) — a foundational memory layer for recording reasons, permissions, and responsibility behind actions, not just events or results. Enables systems in AI, fintech, security, and distributed computing to preserve meaning and causal accountability across time, independent of execution or transport. - expected_user_outcome: CML (Causal Memory Layer) — a foundational memory layer for recording reasons, permissions, and responsibility behind actions, not just events or results. Enables systems in AI, fintech, security, and distributed computing to preserve meaning and causal accountability across time, independent of execution or transport. ## 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 to CML**: importance `high` - source_paths: README.md, pyproject.toml, ROADMAP.md, docs/START_HERE.md, docs/NON_CLAIMS.md - **Causal Records, Chains, CTAG and Audit Rules**: importance `high` - source_paths: cml/__init__.py, cml/record.py, cml/chain.py, cml/ctag.py, cml/audit.py - **CLI, REST API, MCP Server and Deployment**: importance `high` - source_paths: cli/main.py, cli/audit.py, cli/chain.py, api/server.py, api/store.py - **vCML Reference Implementation, LLM Integrations and Research Directions**: importance `high` - source_paths: vcml/README.md, vcml/multi_boundary.md, vcml/audit.md, vcml/linux-ebpf/README.md, vcml/linux-ebpf/exec_monitor.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `5abcb3367db77370c4c71f0825170dccc81cb274` - inspected_files: `Dockerfile`, `README.md`, `docker-compose.yml`, `pyproject.toml`, `docs/CML_AI_ADOPTION_EQUILIBRIUM_LAYER.md`, `docs/CONTRIBUTOR_IMPACT_RUBRIC.md`, `docs/FINTECH_LIMIT_DEMO.md`, `docs/GRANT_EVIDENCE.md`, `docs/GRANT_REVIEWER_CHECKLIST.md`, `docs/LTP_CML_BRIDGE.md`, `docs/NON_CLAIMS.md`, `docs/PORTFOLIO_RELATIONSHIP.md`, `docs/README_STAR_CONVERSION_SNIPPET.md`, `docs/RELATED_CAPU_PERSONA_BOUNDARY_UPDATE.md`, `docs/RELATED_LS_GRANT_PATH.md`, `docs/RELEASE_NOTES_REVIEWER_READY.md`, `docs/REVIEWER_PATH.md`, `docs/START_HERE.md`, `docs/STAR_HOOK.md`, `docs/api/HOSTED_AUDIT_API_MVP.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/safal207/Causal-Memory-Layer/issues/139 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: 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/safal207/Causal-Memory-Layer/issues/66 - 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: 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: packet_text.keyword_scan | https://github.com/safal207/Causal-Memory-Layer - 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/safal207/Causal-Memory-Layer - 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/safal207/Causal-Memory-Layer - 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/safal207/Causal-Memory-Layer - 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/safal207/Causal-Memory-Layer - 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/safal207/Causal-Memory-Layer/issues/141 - 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/safal207/Causal-Memory-Layer/issues/47 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 10: 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/safal207/Causal-Memory-Layer - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.