Vipin Wiki

This is a working knowledge dashboard for fast answers, slow ingest, research ideation, and project memory.

Language: English · 中文 · 日本語

Start here

Press Ctrl+K or / to search the whole public wiki. Use the graph and backlinks to move through related pages instead of reading the catalog from top to bottom.

Command Center

LaneUse it forEntry points
Fast answerAnswer from maintained pages before broad ingest.Catalog, queries-home, local-project-roots
ResearchReframe projects, inspect evidence boundaries, and search for stronger mechanisms.research-projects, research-ideation-policy, 2026-05-10-vipin-research-project-map
Project routingLocate local project roots by content nature without copying folders into the wiki.local-project-roots, weipingyan-portfolio, undergraduate-projects-netherlands
Durable ingestPreserve reusable knowledge after the quick answer.overview, log, synthesis-home

Active Research Map

  • uncertainty - Task-grounded calibrated uncertainty for LLM-based recommendation.
  • truce-rec - Uncertainty-aware generative recommendation with strict evidence gates.
  • tgl-rec - Temporal graph-to-language recommendation focused on next-need transitions.
  • analog-agent - Layered AI4EDA analog circuit design agent.
  • donebench - Specification-grounding benchmark for tool-using agents.
  • uncertaintyprotein-ai4s - AI4S protein optimization under feedback shift.
  • protein-optimization-feedback-shift - Conceptual page for uncertainty-aware closed-loop protein sequence optimization.

Knowledge Shortcuts

  • frontend-frameworks-public - Curated public corpus for reusable frontend project shells, docs/wiki frameworks, app frameworks, build tooling, and release ideas.
I want to…Open
see every public pageCatalog
resume saved Q&Aqueries-home
browse topic clusterstopics-home
compare tradeoffscomparisons-home
read long-running synthesissynthesis-home
inspect recent maintenancelog
understand repo structureoverview

Recent Durable Answers

Active Questions

  • How should uncertainty be represented when it must improve decisions rather than only calibration metrics?
  • Which current research project should be radically reframed instead of incrementally polished?
  • Which top-conference projects or strong open-source systems should inform the next research move?
  • Which repeated course/project questions should become durable topic pages?
  • Which public pages are useful but stale, and which low-value pages should be proposed for deletion?

Operating Rules

  • Fast answer first, durable ingest second.
  • Public wiki/ is the website source; private/raw layers stay out of the public build.
  • Use live rescans before current-state claims about external local roots.
  • For abstract or general research/project prompts, look outward to strong GitHub projects and top-conference paper projects for inspiration, then synthesize without copying.
  • Do not delete information without explicit user approval; preserve useful old information through annotation, archiving, or merging.

How This Site Works

The public site is built with Quartz from the maintained Markdown wiki. It preserves wikilinks, search, backlinks, tags, and graph navigation while keeping raw and private materials out of the published artifact.