CtrlK
BlogDocsLog inGet started
Tessl Logo

engram-business-rules

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

63

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/business-rules/SKILL.md
SKILL.md
Quality
Evals
Security

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.
Repository
Gentleman-Programming/engram
Path

skills/business-rules/SKILL.md

Commit

763a6ba

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.

Claim skill