Decision Rain Library Project is designed for everyday use. The flow is intentionally short — find a signal, let the assistant research it, then decide what to do with it. The loop repeats every time you encounter something worth saving. You do not need to know why a signal matters when you capture it; the library is built to preserve the trace first and turn it into a decision later.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/xxyoudeadpunkxx/decision-rain-library-project/llms.txt
Use this file to discover all available pages before exploring further.
The Six-Step Daily Loop
Find a signal
A GitHub repo, tool, article, service, guide, idea, or research spark catches your attention. You do not need to have an opinion about it yet — noticing it is enough.
Save to 00_INBOX
Give the link to your AI assistant. It saves the original URL to
00_INBOX first, with status/pending-review and one next/* tag, to preserve the trace before any analysis begins.Assistant researches
The assistant reads the page, repo, docs, or available sources and gathers both official and community evidence. It does not skip this step, and it does not classify from memory or title alone.
Assistant proposes
The assistant proposes classification, tags, Verdict, Next, and uncertainty. This is a proposal only — not a decision. The entry remains in
00_INBOX with status/pending-review until you act.You validate
You read the proposal, correct anything wrong, and decide whether to approve, reject, or request more analysis. Approval is an explicit action — silence is not approval, and a clean-looking proposal is not approval.
What Counts as a Signal
A signal is anything that may be worth later attention. The library does not require you to know why it matters at capture time — the point is to preserve the trace, then turn it into a decision later. Signals include:- GitHub repositories — libraries, tools, reference implementations, research projects, or idea sparks hosted on GitHub
- Documentation pages — official docs, guides, API references, or specification pages
- Products or APIs — services you might integrate, automate against, or evaluate for adoption
- Guides and patterns — workflows, architecture patterns, implementation techniques, or best-practice write-ups
- Research projects — academic or community research that may inform future decisions
- Workflow ideas — concepts, integrations, or automations that are not yet fully formed
- Directories of tools — curated lists, awesome-lists, or catalogs that are useful for discovery
- Small sparks — fragments, quotes, or links that do not fit neatly into any category but may become useful later
Separating Signal, Analysis, and Decision
The library works because it keeps three levels distinct. Collapsing them together — treating a saved link as a decision, or an AI analysis as validation — undermines the entire system.- Signal: the item caught attention. Something about it was worth preserving.
- Analysis: the assistant explains what it is, what evidence exists, and what is missing. It may recommend a course of action. That recommendation is a proposal.
- Decision: you validate what to do with it. Only operator action converts a proposal into a canonical library entry.