Repolens
An asynchronous support workspace for open-source and developer-tool teams that represents redacted case metadata as reviewable changes while keeping sensitive customer content in a controlled system of record.
Developer-tool companies often ask maintainers to work in one review system for code and another inbox for customer support. Repolens tests whether the familiar proposal-review-merge model can make support ownership clearer without copying private ticket content into permanent code history. The repository carries durable references, redacted summaries, routing policy, and review events; a protected case store carries personal data, secrets, attachments, deletion, and legal holds.
A support, developer relations, or engineering leader at an open-source or business-to-developer company whose maintainers already participate in customer support. The record does not establish budget or minimum case volume.
The useful inversion is to borrow review discipline from code without treating a permanent code history as a safe customer-data store.
No trigger inside the preceding twenty-four months is established.
The record does not identify which barrier recently broke.
The productive tension is clear: reuse developer review habits for support while preserving the privacy and customer-access properties a code repository does not provide. Two cross-references and two inbound links offer modest recurrence.
The source does not prove a budget, a recent trigger, or a structural incumbent disadvantage. The literal ticket-as-file framing creates privacy, deletion, and usability hazards, so the viable direction requires a more careful split architecture than the original metaphor suggests.
Discussion
No comments yet — be the first to weigh in.