Blame · Line-by-line history
open-questions.md
Each line is annotated with the commit that last touched it. Click any SHA to jump to that commit and see the surrounding change.
| d0bc8c2 | 1 | # GlueCron — Open Questions |
| 2 | ||
| 3 | > Items that need owner input or a decision before building. | |
| 4 | ||
| 5 | ## Active | |
| 6 | ||
| 7 | ### Q001: GateTest repair boundaries | |
| 8 | - **Question:** What types of failures should GateTest auto-fix vs escalate to a human? | |
| 9 | - **Context:** Building the self-healing loop. Auto-fixing lint/format is safe. Auto-fixing logic bugs is risky. | |
| 10 | - **Proposed answer:** Auto-fix: formatting, import ordering, unused variables, missing semicolons, secret redaction, simple type errors. Escalate: logic changes, API contract changes, test failures that require new test logic, security vulnerabilities requiring architectural changes. | |
| 11 | - **Status:** Awaiting confirmation | |
| 12 | ||
| 13 | ### Q002: Client-side interactivity timeline | |
| 14 | - **Question:** When does the platform need client-side JS beyond SSE? | |
| 15 | - **Context:** Currently pure SSR. SSE handles real-time. But features like drag-and-drop project boards, inline code editing, and live collaborative review need JS. | |
| 16 | - **Proposed answer:** Build with progressive enhancement — SSR first, sprinkle vanilla JS for specific interactions (code editor, drag-drop). No React/Vue/Svelte until proven necessary. | |
| 17 | - **Status:** Low priority, track demand | |
| 18 | ||
| 19 | ### Q003: Pricing model | |
| 20 | - **Question:** Free tier limits, paid tier features, enterprise tier | |
| 21 | - **Context:** SBOM is free (differentiator). What else is free vs paid? | |
| 22 | - **Status:** Not yet discussed | |
| 23 | ||
| 24 | ### Q004: Legal review of flywheel | |
| 25 | - **Question:** Owner mentioned needing to review legal implications of the flywheel | |
| 26 | - **Context:** The flywheel learns from code review outcomes. Need to verify: data ownership, privacy (does it learn across repos?), GDPR compliance for EU users. | |
| 27 | - **Proposed answer:** Flywheel patterns are scoped per-repo by default. Global patterns only from aggregated, anonymized data. Users can opt out via repo settings. | |
| 28 | - **Status:** Owner flagged for later review | |
| 29 | ||
| 30 | ## Resolved | |
| 31 | ||
| 32 | (none yet) |