By name: engram-business-rules description: > Product and business-rule guardrails for Engram. Trigger: Any change that affects sync behavior, project controls, permissions, or memory semantics. license: Apache-2.0 metadata: author: gentleman-programming version: "1.0"
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
- Local-first remains the default mental model.
- Org-wide security controls belong in cloud, not only in local clients.
- Project sync policy must be enforceable server-side if it is meant for admins.
- UI controls must map to real business rules, never fake toggles.
- 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.