engram-business-rules

SkillDocs & knowledge

Lets your agent follow Engram's product rules when changing sync, permissions, or memory behavior.

Then ask your AI: use the engram-business-rules skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Add it as a step in a pipeline you build on Ahel, or connect Ahel to Claude, ChatGPT, Cursor, Claude Code or Codex and ask your AI to use it.

About this skill

Product and business-rule guardrails for Engram. Trigger: Any change that affects sync behavior, project controls, permissions, or memory semantics.

What this skill tells your AI

The instructions your AI receives, as published by gentleman-programming/engram in skills/business-rules/SKILL.md and read by Ahel’s review.

When to Use

Use this skill when:

  • Changing enrollment, sync, auth, admin controls, or cloud behavior
  • Implementing project-level or org-level policy
  • Adjusting what data appears locally vs remotely

Product Rules

  1. Local-first remains the default mental model.
  2. Org-wide security controls belong in cloud, not only in local clients.
  3. Project sync policy must be enforceable server-side if it is meant for admins.
  4. UI controls must map to real business rules, never fake toggles.
  5. Data visibility and sync permissions must be deterministic and testable.

Sync Rules

  • Enrollment controls what may sync from local.
  • Cloud pause controls what the organization currently allows.
  • When a policy blocks sync, fail loudly rather than dropping data silently.
  • Preserve auditability whenever admin policy changes behavior.

Signals

GitHub stars
7k
Forks
733
Last commit
Oct 2026
Advanced
Item type
skill
Key
engram-business-rules
Source
github.com/gentleman-programming/engram