Luminescence SoftwareAnonymous collaboration · identity withheld
A desktop workspace for repository investigation, ticket preparation and planned code changes. Durable workflows, typed tools and explicit approvals.
A developer workspace that investigates repositories, prepares tickets and implementation plans, and proposes code changes. Desktop interfaces and backend orchestration make the process visible and reviewable. Product identity remains private.
AI needs useful repository context and bounded capabilities, while people need to understand, review and approve the changes it proposes.
Repository inspection gives the investigation relevant files and technical context. Structured results and conversation history help an operator refine the problem before implementation planning.
Repository inspection · Ticket drafts · Refinement
Implementation plans define which paths may be created, edited or deleted. Typed file tools operate inside disposable coding workspaces and report what remains in the approved plan.
Planned paths · Bounded file tools · Change status
Proposed patches and review context are presented to the operator. Approval separates preparing a change from publishing it through the source-control integration.
Proposed patches · Human review · Publication
Electron · Next.js · TypeScript
The desktop renderer uses an isolated context with Node integration disabled and a typed preload bridge. Product operations go through the backend rather than giving the interface direct repository execution access.
Temporal · NestJS · PostgreSQL
Temporal workflows coordinate repository initialization, investigation and implementation planning. Backend services persist ticket and run state, while realtime events make ongoing work visible in the client.
TypeScript · Typed contracts
Inspection tools return bounded repository context. Coding tools distinguish text replacement, planned file creation and deletion, and a change-status report. Change status and operator review keep the proposed patch visible and traceable.
Git · NestJS · PostgreSQL
Repository investigation and coding use temporary checkouts. Prepared changes remain proposals until operator approval; a trusted publication service handles the source-control operation and cleanup logic removes abandoned temporary workspaces.
Repository evidence, bounded tools and operator approvals.
Work on the desktop experience, typed backend contracts, durable workflow coordination and repository-aware AI tooling. The product makes proposed changes and human approval visible. We can help turn repository-aware AI capabilities into a considered product experience.
A calmer place to learn. Personal flashcards, thoughtful review sessions, and the freedom to study wherever life takes you—even offline. We also prepared the store assets, fully set up both store listings and released the iOS and Android apps ourselves.
Inside the product
Everyday finances, brought into focus. Accounts, expenses, plans, and shared costs in one considered mobile experience.
Inside the product