engram-business-rules

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

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "engram-business-rules" with this command: npx skills add gentleman-programming/engram/gentleman-programming-engram-engram-business-rules

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.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

engram-memory-protocol

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

gentleman-bubbletea

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

engram-testing-coverage

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

engram-pr-review-deep

No summary provided by upstream source.

Repository SourceNeeds Review