docs: competitive feature scope vs Home Assistant & Homebridge - #74
Merged
Merged
Conversation
Add a grounded feature-scoping doc that maps the two competitors onto the two gaps where Lumen genuinely locks users out today — HomeKit-only device support (Homebridge's niche) and geofence-only automation triggers (Home Assistant's niche) — and scopes closing both on Lumen's calm/consent terms. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
mohabbis
marked this pull request as ready for review
July 14, 2026 01:58
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
docs/competitive-feature-scope.md— a grounded scoping doc for competing with Home Assistant and Homebridge on Lumen's terms (calm, explainable, consent-before-action), not by cloning their breadth/density.The doc maps each competitor onto the one gap where Lumen genuinely locks a user out today:
Scenehas one trigger axis — geofence arrival/departureScope tiers
SmartHomeBridgefor local-LAN devices (DeviceServiceis already multi-bridge, routing bydevice.bridgeID— HomeKit is just the first bridge); time/schedule triggers for scenes, generalizing the singlegeofenceTrigger.SuggestionEngine), an explainable conditional-rule builder, and a calm "what happened today" history over the persistedExecutionEvents.Moat guardrails
Explicit non-goals section reaffirms
ROADMAP.md: no auto-apply-without-confirmation, no plugin runtime, no cloud integrations, no dashboard-density race. Flags the one open decision that needs aROADMAP.mdsign-off before building — whether a scheduled scene firing directly counts as pre-given consent.Docs-only change; no code or tests touched.
🤖 Generated with Claude Code
Generated by Claude Code