Synapse - Spatial Knowledge Twin

The description states that Synapse transforms educational material (PDFs, research papers, notes) into an interactive visual knowledge graph. It offers two views:

• A 3D Galaxy View, powered by react-force-graph-3d
• A 2D Flowchart View, using @xyflow/react

Each concept is represented as a node with color-coded mastery states:

• 🔴 Knowledge Gap
• 🟡 Review
• 🟢 Mastered
• 🔒 Locked

Clicking a node opens an Active Recall Inspector that includes explanations, KaTeX-rendered formulas, citations, and recall questions. The system updates mastery in real time, unlocks connected concepts, and animates the repair path.

The tool processes documents locally using pdfjs-dist, extracts structured data via a GPT-based workflow (server-side), and validates output with Zod. It uses Dexie and IndexedDB for local progress persistence.

Inference The product is described as a browser-based application built in React/TypeScript, not a SaaS offering or hosted platform.

The author positions Synapse as an alternative to passive reading and generic AI chatbots. It aims to make learning more active by enabling spatial exploration of concepts and real-time mastery tracking.

Key claims:

• “Stop passively reading. Start navigating your learning.”
• “Transform linear text into an interactive 3D knowledge galaxy”
• “Creates a more visual, spatial learning experience”

These are marketing-style positioning statements rather than evidence of traction or product-market fit.

Inference The project evolved from a hackathon idea into a prototype with technical depth, but no indication it has moved beyond that stage.

The description states Synapse is intended for students studying long textbook chapters or dense research papers. It is designed to help them:

• Explore concepts
• Identify weak prerequisites
• Master what they are learning

It also mentions potential future use cases like teachers creating knowledge graphs and classroom analytics.

Inference The primary ICP appears to be individual learners (students), with a possible expansion toward educators or curriculum developers. No evidence of specific customer segments beyond this.

There is no mention of pricing, monetization, or business model in the description.

Not evidenced

The author built Synapse using:

• Frontend: React, TypeScript, Vite, Tailwind CSS
• 3D Visualization: react-force-graph-3d
• 2D Visualization: @xyflow/react
• PDF Parsing: pdfjs-dist
• AI Processing: GPT-based workflow (server-side)
• Validation: Zod schema validation
• Local Storage: Dexie + IndexedDB
• Math Rendering: KaTeX
• Architecture Tools: Codex

Challenges addressed include:

• Maintaining synchronization between 2D and 3D views
• Performance optimization for WebGL rendering
• Handling complex PDF layouts and formatting
• Free-response answer evaluation with rubrics and misconception detection

Inference The tool is a client-side web application that can function without backend services, though it relies on AI APIs during processing.

The project is described as a hackathon submission, built in one week. It includes:

• A functional prototype
• Local processing capabilities
• Multi-view UI with real-time updates
• Fallback architecture for API failures

However, there is no evidence of:

• Users or customers
• Revenue or monetization
• Product adoption metrics
• Customer feedback or usage data

Not evidenced

The description does not mention any competitors. It implies Synapse aims to improve upon generic AI tools and traditional reading methods.

Not evidenced

1. Single Developer: Only one team member is listed, suggesting limited development capacity or scalability.
2. Prototype Status: The tool is described as a hackathon prototype with no evidence of further development or traction.
3. AI Dependency Risk: While fallbacks exist, the system still depends heavily on external AI APIs for processing and evaluation.
4. No Commercial Evidence: No revenue, customers, or product-market fit data are provided.
5. Unproven Market Demand: The author makes claims about user needs but provides no evidence of demand or market validation.

1. What is the actual user base or pilot group for this tool?
2. Has there been any feedback from students or educators on usability or effectiveness?
3. How does Synapse handle complex document types like scanned PDFs, tables, diagrams, or multilingual content?
4. Are there plans to integrate with existing LMS platforms or educational institutions?
5. What are the technical limitations of the current prototype that would need to be addressed for production use?
6. Is there any plan to monetize or scale beyond a personal tool?