Project rules & decisions
Core rules (summary in our words):
- Exact manufacturerName+productId, one couple one driver; a specific driver wins, generic stays fallback.
- One reliable source is enough; never invent; record the source. Unconfirmed β provisional tier (data/leads/provisional-couples.json).
- Native clusters are mandatory for pairing; Tuya EF00 and others stay optional.
- Additive only; nothing that works is removed. Versions strictly incremental and aligned across branches.
- No copy-paste from other projects: rewrite, credit with id, link and author.
- No --no-verify, no force-push, no history rewrite. Every fix ships with unit tests.
Full texts (SSOT):
- Automation first (P3097, 2026-10-31)
- Autonomy safety (P3097, t644u)
- Bastien House App β private Zigbee track (P2606)
- 𧬠BYPASS ELITE LAYERS & NATIVE SDK3 MIGRATION ARCHITECTURE
- Complementary variant enrich β ALWAYS (P2520)
- Couple removal evidence (P3134, mandatory)
- Couple source policy (SSOT)
- CRITICAL MISTAKES - Never Repeat (v8.5.0 Phoenix Sovereign + Fleetwood Gateway)
- Cross-App Prompt Rules
- Daily resume β enrichment mode (standing rules)
- Deep functional enrich (P2529)
- Development Rules - Tuya Unified Zigbee
- Diagnostic History Rules
- Driver continuations (P3206, 02/11/2026 Paris)
- Dual-App Vision β master vs stable-v5 (+ Bastien house)
- Five couples listed in two drivers (PC harvest round 2, item 3)
- Dynamic adaptation β nothing is mandatory (P3207)
- Rules for Dynamic Healing & Identification (v1.0.0)
- Smart-home ecosystem audit (Matter Bridge, Google, Alexa, SmartThings) β 2026-10-04
- Firmware-limit compensation (P3101, t656u)
- Forum leads β own rules distilled from harvest dumps (spec 005)
- Forum Silent Enrichment & Human Voice Doctrine
- _TZ3000_4uuaja4a: TS130F curtain module (collision TS0726/TS130F, 2026-10-04)
- GitHub voice β human first (P2394)
- Grok-off readiness (P3111, 01/11/2026 Paris)
- _TZE284_hodyryli: one couple, one driver (P3070)
- Tile state, HomeKit and capability coverage rules (t699u, t719u-t722u)
- Ambiguous IAS identities: one mfr/model, several physical products (JohanBendz #1113 deep read)
- Contact + illuminance door sensors (JohanBendz #1298 deep read)
- Standard-ZCL temperature/RH sensors β own rules from the JohanBendz #797 family (spec 009 deep read)
- JohanBendz/com.tuya.zigbee branches β cross-check 2026-10-03 (inspiration only, no code copied)
- Johan branch gaps resolved 2026-10-04 (research notes, our wording)
- KNOWLEDGE BASE & AI HEURISTICS (Local BDD)
- NEXUS ULTIMATE MANIFESTO (v7.2.14)
- π OPUS 4.6 MEGA-PROMPT β Universal Tuya Maintenance Framework
- PC harvest r2, item 1: missing devices (per couple)
- PC harvest round 3: couple checks
- Post-Promotion Documentation & Registry Synchronization (MANDATORY)
- Pragmatic internal roadmap (compass)
- R20: identifier matching (manufacturerName, productId/modelId)
- R22 architecture sources (spec 010 / T0)
- π Security Rules v8.5.0
- Session Stability & Heuristic Rules Specification
- Shipped JavaScript Latin-1 and package images (P3320)
- The "56 Years Ago" Bug and Tuya Sleepy Devices
- Source digest rule (P3138 β t734u / t735u / t736u)
- SSOT couple-sources ledger (P3136, t731u)
- Unit-test anti-rΓ©gression (P2469)
- Rule (SSOT): unknown commands and method chains (P3016βP3017)
- Unsupported Devices & Categories
- User Device Expectations β Tuya Unified Zigbee
- User reports are presumed true (P3200, t765u)
- W5 interview vs driver clusters (PCr2-2, 2026-10-04)
- WHY interrogation doctrine (P215)
- WiFi vs Zigbee Separation Standard & Architectural Guidelines
- Zigbee2MQTT / ZHA to Homey Capability Mapping Dictionary
- ZIGBEE_TUYA_RULES.md β Tuya Zigbee Protocol Reference