The tag registry defines the complete allowed tag grammar for Decision Rain Library Project. Tags use aDocumentation 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.
family/value format — for example, status/ready or truth/verified. All tags must come from approved families and approved values. Free-form tags like cool, interesting, or tool are not allowed. The registry exists to keep the library interrogable over time: every tag must carry a clear, stable meaning that does not drift with context or convention.
Tag Format
Every tag follows the patternfamily/value. The family identifies the dimension being described; the value identifies the specific classification within that dimension. Both parts are required — partial tags like status or ready alone are not valid.
New tag values are permitted only through explicit operator approval. When the assistant encounters a gap — a situation where no existing value fits — it reports the smallest proposed addition and waits before using it. The assistant does not invent convenience values, synonyms, or broad generics to fill gaps silently.
Tag Families
authority/* — who or what supports the claim
authority/* — who or what supports the claim
truth/* — confidence or state of truth
truth/* — confidence or state of truth
The
Choose the most accurate value rather than the most favorable one.
truth/* family records the confidence level of the key claim. It is not a rating of quality — it is an honest assessment of how well the claim is supported by current evidence.| Tag | Meaning |
|---|---|
truth/verified | Confirmed by primary evidence, working test, or strong corroboration |
truth/plausible | Likely true but not tested enough to confirm |
truth/claimed | Asserted but not verified |
truth/conflicting | Credible sources disagree |
truth/outdated | Likely stale or obsolete |
truth/unknown | Not enough evidence to judge |
truth/plausible is not a weak truth/verified — it is an honest record of the evidence state.status/* — operational decision
status/* — operational decision
The
Every entry that has been evaluated must carry exactly one
status/* family records the current operational decision about an entry. Status values reflect the assistant’s proposal and must be confirmed by the operator before they become canonical.| Tag | Meaning |
|---|---|
status/dissect | Deserves close analysis now |
status/ready | Usable or applicable with low ambiguity and acceptable StackFit |
status/later | Useful but not current priority |
status/core-good | Core idea is valuable even if implementation or StackFit is not practical |
status/watch | Monitor maturity, pricing, maintenance, ecosystem, or access constraints |
status/rejected | Evaluated and not worth using except as historical evidence |
status/reference | Useful mainly as reference, documentation, directory, or learning material |
status/pending-review | Assistant has processed this entry but the operator has not yet validated it |
status/* tag. Do not combine status values.next/* — next concrete action
next/* — next concrete action
The
Choose the most specific action that applies.
next/* family records the most specific next action for an evaluated entry. Always add one next/* tag per evaluated entry — it must never be omitted.| Tag | Meaning |
|---|---|
next/test | Try it in the operator environment |
next/spike | Timeboxed exploration with unknown outcome |
next/extract | Pull the pattern or idea; do not adopt the tool |
next/revisit | Park with intent to return |
next/archive | Move to 90_ARCHIVE |
next/deploy | Ready to integrate into active workflow |
next/revisit is not passive archiving — it implies an intention to return when conditions change.priority/* — optional operator attention marker
priority/* — optional operator attention marker
The
priority/* family is an optional operator attention marker. It has exactly one defined value.| Tag | Meaning |
|---|---|
priority/high | Operator attention marker for items that should stay visible |
priority/high does not mean ready, validated, urgent, or objectively more important. Do not use it as a replacement for status/* or next/*. Do not invent additional priority scales unless the operator explicitly approves them.type/* — what kind of object this is
type/* — what kind of object this is
The
type/* family describes what kind of artifact the entry is. Values are examples, not an exhaustive closed list — the operator may add new values as needed.Common values include: type/repo, type/guide, type/docs, type/framework, type/directory, type/paper, type/service, type/pattern, type/tutorial, type/idea.An entry may carry more than one type/* tag when the artifact genuinely spans multiple kinds — for example, a GitHub repo that is both a guide and docs.domain/* — topic or domain
domain/* — topic or domain
The
domain/* family describes the subject area or field the entry belongs to. Values are operator-defined and grow as needed.Common examples: domain/automation, domain/devtools, domain/agents, domain/data, domain/productivity.Domain tags are descriptive, not evaluative — they describe the subject of the entry, not its quality or fit.source/* — where the item comes from
source/* — where the item comes from
The
source/* family records the origin of the entry — where it was found or what platform hosts it.Common examples: source/github, source/web, source/paper, source/newsletter.source/* describes origin only. GitHub is a source, not a fit judgment. A GitHub entry may be code, docs, a guide, a pattern, a directory, research, an idea, or a spark — type/* captures what it is; source/* captures where it came from.scenario/* — usage scenario
scenario/* — usage scenario
The
scenario/* family records the intended or likely usage context for the entry.Common examples: scenario/learning, scenario/power-user, scenario/onboarding, scenario/automation.Scenario tags help with later retrieval by context — when you want to find entries relevant to a specific situation rather than a specific domain.risk/* — adoption or trust risk
risk/* — adoption or trust risk
The
risk/* family records notable adoption or trust risks that should be visible at a glance.Common examples: risk/ecosystem-mismatch, risk/vendor-bias, risk/overpromised, risk/stale, risk/billing-unclear.Risk tags are not penalties — they are signals that a specific concern exists and should be weighed before acting. An entry with a risk tag may still be status/core-good or status/reference.stack/* — relevant technology stack
stack/* — relevant technology stack
The
stack/* family records technology-stack relevance when the entry is tightly coupled to a specific language, runtime, or ecosystem.Common examples: stack/kotlin, stack/python, stack/javascript, stack/node, stack/rust.Use stack/* when the technology coupling is a meaningful factor in StackFit — for example, when a framework is Kotlin-only and the operator does not use Kotlin.fit/* — practical compatibility with the operator environment
fit/* — practical compatibility with the operator environment
The
fit/* family records practical compatibility with the operator’s real operating environment and adoption threshold. It is the most nuanced family — see the StackFit section below for evaluation guidance.| Tag | Meaning |
|---|---|
fit/windows | Compatible with a Windows environment |
fit/vscode | Works with VS Code |
fit/ai-assisted | Setup or use benefits from AI assistance |
fit/llm-chat | Accessible via LLM chat interface |
fit/pipedream | Integrates with Pipedream |
fit/automation-layer | Works within an automation layer |
fit/mcp | Supports the Model Context Protocol |
fit/local | Runs locally without external services |
fit/free-tier-real | Has a genuine free tier, not just a trial |
fit/no-card | Can be used without providing a payment card |
fit/account-required | Requires creating an account |
fit/paywall-risk | Has a known or likely paywall risk |
fit/freemium-risk | Free tier may be misleading or limited |
fit/dev-heavy | Requires significant developer effort to adopt |
fit/discovery-only | Entry is a starting point for further evaluation, not direct adoption |
fit/owned-hardware | Requires or assumes operator-owned hardware |
StackFit Evaluation
StackFit is not a list of the operator’s tools. StackFit is a practical judgment of how realistically the operator can get value from an item. It is evaluated across five dimensions:Value Type
What kind of value does the item provide? Choose the most accurate value type:
- Direct use — the item can be used as-is with minimal setup
- Assisted implementation — usable with documented or AI-assisted setup
- Workflow integration — fits into an existing automation or workflow layer
- Idea extraction — the idea is valuable even if the implementation is not adoptable
- Reference — useful for learning or documentation lookup
- Discovery only — the item points toward other candidates that must each be evaluated
Operator Capability
What can the operator realistically do? Consider: local workstation, editor, AI assistants, GitHub, automation layers, and Raindrop as library backend.
Adoption Cost
What is required to adopt? Consider: dependencies, local tools, accounts, APIs, frameworks, service maintenance, unfamiliar ecosystems, payment, card requirements, and billing risk.
Friction Threshold
What level of friction is acceptable? Documented and assistant-assisted setup is acceptable. A real free tier is acceptable. Card traps, unclear billing, fake freemium, enterprise assumptions, or incompatible ecosystems lower fit.
Governance Rules
The following rules apply to all tagging decisions:- No emotional or free-form tags. Tags like
cool,interesting,maybe,good,AI, ortoolare not allowed. - Use interrogable tags. Every tag must carry a clear, stable meaning —
truth/plausible,authority/source-code,status/core-good,risk/overpromised,fit/free-tier-real. source/*describes origin;type/*describes object type;fit/*describes practical compatibility. These three families are distinct and must not be conflated.- GitHub is a source, not a fit judgment. A GitHub item may be code, docs, a guide, a pattern, a directory, research, an idea, or a spark. Use
type/*to describe what it is. - Raindrop is the library backend, not a fit tag. Do not use
fit/raindropby default. - New tag values require explicit operator approval. If no existing value fits, the assistant reports the gap and proposes the smallest addition. It waits before using any new value.