leanctx-ip-governance — Claude Code rule: purpose and setup
The leanctx-ip-governance rule sets product, licensing, and release boundaries for LeanCTX. It guides agents working on code, documentation, and releases.
Apache-2.0 ★ 3,956 updated 2026-10-29
.cursor/rules/leanctx-ip-governance.mdcWhat leanctx-ip-governance does
The rule applies to every task. Before editing, the agent must read SKILL.md, AGENTS.md, and the references covering product scope and connector and decision security. New work must connect an authorized source to a decision and then to a bundle or receipt. Team coordination context is in scope; general agent and model orchestration is not.
Keep Apache rights intact and never remove open-source code automatically. New EE work must stay private. A public release requires approval from both the founder and an independent reviewer, so one approval alone is not enough. Changes must state the source ACL, integration coverage, affected licence, tests, and rollback plan.
What it helps with
- check whether a proposed feature fits LeanCTX product scope
- preserve Apache rights while keeping new EE work private
- verify approval requirements before a public release
- record source ACL, integration coverage, tests, and rollback steps
Example prompts for the agent
- Check this change against LeanCTX scope, licensing, and release rules.
- Explain how this task connects an authorized source to a decision and a bundle or receipt.
- Review the change and report the source ACL, integration coverage, affected licence, tests, and rollback plan.
How to install leanctx-ip-governance
Manually: put the files in place
.cursor/rules/leanctx-ip-governance.mdcFrontmatter: description, globs, alwaysApply
Manually: put the files in place
.claude/rules/leanctx-ip-governance.mdThe paths frontmatter field limits the files: move globs from the source into paths
AGENTS.md
Codex reads AGENTS.md: paste the rule text there
Manually: put the files in place
.github/instructions/leanctx-ip-governance.instructions.mdThe applyTo field sets which files it applies to: move globs from the source into applyTo
Manually: put the files in place
.devin/rules/leanctx-ip-governance.mdManually: put the files in place
.clinerules/leanctx-ip-governance.mdStep by step, with commands for each platform: Cursor rules: .mdc files, four modes and what replaced .cursorrules
Questions about leanctx-ip-governance
How do I install leanctx-ip-governance in Claude Code?
Add the rule file at .claude/rules/leanctx-ip-governance.md.
What does leanctx-ip-governance do?
It sets product and licensing boundaries for LeanCTX work and defines approval requirements for public releases.
What must new LeanCTX work connect?
It must link an authorized source to a decision, then to a bundle or receipt. General agent and model orchestration falls outside product scope.
Source text
leanctx-ip-governance.mdc · Apache-2.0
--- description: LeanCTX Context Gateway source/decision scope, Apache IP and private EE safety gate for all coding, docs and releases. alwaysApply: true --- Before editing, read `.agents/skills/leanctx-ip-governance/SKILL.md` and `AGENTS.md`, including `references/PRODUCT_SCOPE.md` and `references/CONNECTOR_AND_DECISION_SECURITY.md`. LeanCTX is Context Gateway (Select → Control → Prove); new work must map authorized source→decision→bundle/receipt. General agent/model orchestration is not product scope; team coordination context (presence, leases, workspace bus, shared work graph) is. Preserve existing Apache rights, do not auto-delete OSS, keep new EE private, no public publish without real founder+independent release approval. State source ACL, integration coverage, affected licence, tests and rollback.
© yvgude · Apache-2.0 · yvgude/lean-ctx