### Collection Usage Guide Source: https://github.com/xxyoudeadpunkxx/decision-rain-library-project/blob/main/README.md Explains the purpose of each collection within the Raindrop structure, from system rules to archived links. ```text ⚙️ `00_SYSTEM` stores the rules and examples. 📥 `00_INBOX` stores new links before they are reviewed. 🔎 `10_REVIEW` stores links that need more thought. 📚 `20_LIBRARY` stores reviewed links you want to keep. 🗄️ `90_ARCHIVE` stores rejected, outdated, inactive, or historical links. ``` -------------------------------- ### Basic Workflow Source: https://github.com/xxyoudeadpunkxx/decision-rain-library-project/blob/main/README.md Illustrates the fundamental steps of saving a link, having ChatGPT inspect it, and making a decision later with context. ```text save the link -> let ChatGPT inspect it -> decide later with context ``` -------------------------------- ### Placeholder URLs for SYSTEM Documents Source: https://github.com/xxyoudeadpunkxx/decision-rain-library-project/blob/main/templates/system-bookmark-links.md Use these stable placeholder URLs for SYSTEM documents that reside exclusively within Raindrop. The actual content is derived from the bookmark excerpt, not the URL itself. ```text https://example.com/rdl-agent-contract https://example.com/rdl-system-spec https://example.com/rdl-tag-registry https://example.com/rdl-decision-rules https://example.com/rdl-note-template https://example.com/rdl-examples-golden https://example.com/rdl-usage-flow ``` -------------------------------- ### Repository Structure Overview Source: https://github.com/xxyoudeadpunkxx/decision-rain-library-project/blob/main/README.md This text block outlines the file structure of the repository and the purpose of each document. It is useful for understanding the project's organization and the role of different markdown files. ```text README.md human-facing overview and setup docs/00_AGENT_CONTRACT.md assistant authority, gates, failure rules docs/01_SYSTEM_SPEC.md collection model and ingestion flow docs/02_TAG_REGISTRY.md controlled tag grammar and StackFit model docs/03_DECISION_RULES.md status, truth, authority, fit, and next rules docs/04_NOTE_TEMPLATE.md canonical evaluated-entry note shape docs/05_EXAMPLES_GOLDEN.md drift-prevention examples docs/06_USAGE_FLOW.md day-to-day operating loop examples/sample-entry.md sample evaluated entry templates/collection-structure.md Raindrop collection layout templates/system-bookmark-links.md placeholder URL pattern for SYSTEM entries ``` -------------------------------- ### Suggested Connector Description for ChatGPT Source: https://github.com/xxyoudeadpunkxx/decision-rain-library-project/blob/main/README.md A concise description to configure the Raindrop connector for ChatGPT, emphasizing its role as a decision library backend. ```text Use Raindrop as a Decision Library backend, not as generic bookmarks. New links should first be saved to 00_INBOX. Before reviewing or moving links, read 00_SYSTEM. ChatGPT may inspect and propose, but the user decides final placement, tags, and next steps. ``` -------------------------------- ### Required SYSTEM Read Order Source: https://github.com/xxyoudeadpunkxx/decision-rain-library-project/blob/main/README.md The assistant must read SYSTEM entries in this specific order before classification, update, normalization, or promotion. This order ensures critical information like agent contract and rules are processed first. ```text 00_AGENT_CONTRACT 01_SYSTEM_SPEC 02_TAG_REGISTRY 03_DECISION_RULES 04_NOTE_TEMPLATE 05_EXAMPLES_GOLDEN 06_USAGE_FLOW ``` -------------------------------- ### ChatGPT Review Output Structure Source: https://github.com/xxyoudeadpunkxx/decision-rain-library-project/blob/main/README.md Defines the expected format and fields for ChatGPT's review of a cataloged link, including verdict, next steps, and evidence. ```text Cataloged: YYYY-MM-DD Verdict: short practical judgment. Next: the next useful action. Claim: what the link appears to provide. Evidence: what supports or weakens that claim. Authority: where the evidence comes from. Truth: how confident the review is. Practical fit: whether this is realistically useful for your situation. ``` -------------------------------- ### Raindrop Collection State Machine Source: https://github.com/xxyoudeadpunkxx/decision-rain-library-project/blob/main/README.md This diagram illustrates the lifecycle states (collections) for entries within the Raindrop system. It shows the flow from initial capture to final decision or archiving. ```text 00_SYSTEM -> governance documents only 00_INBOX -> preserved but not evaluated 10_REVIEW -> analyzed or worth analysis, not necessarily validated 20_LIBRARY -> evaluated and operator-validated decisions 90_ARCHIVE -> rejected, obsolete, duplicated, inactive, or historical entries ``` -------------------------------- ### Compact Decision Entry Template Source: https://github.com/xxyoudeadpunkxx/decision-rain-library-project/blob/main/docs/04_NOTE_TEMPLATE.md Use this template for serious decision entries. Ensure critical fields like Verdict and Next appear within the first three lines to avoid truncation. ```text Cataloged: YYYY-MM-DD Verdict: practical judgment in one or two sentences. Next: next action, such as use now, test, extract pattern, watch, reference only, archive. Claim: what the link appears to provide or prove. Evidence: what supports the claim, such as README, source code, docs, issues, tests, release activity, community use, pricing, setup reports, or hands-on test. Authority: what kind of authority supports it; keep official and community evidence separate when both matter. Truth: verified, plausible, claimed, conflicting, outdated, or unknown. StackFit: practical judgment of how realistically the operator can get value from the item. Consider value type, operator capability, adoption cost, friction threshold, and decision path. Mention whether the item is for direct use, test, assisted implementation, workflow integration, idea extraction, reference, discovery, watch, or archive. ``` -------------------------------- ### Raindrop Collection Structure Source: https://github.com/xxyoudeadpunkxx/decision-rain-library-project/blob/main/README.md Defines the recommended collection hierarchy within Raindrop for organizing links into different stages of review and storage. ```text Decision Rain Library Project 00_SYSTEM 00_INBOX 10_REVIEW 20_LIBRARY 90_ARCHIVE ``` -------------------------------- ### Normal State Transition Flow Source: https://github.com/xxyoudeadpunkxx/decision-rain-library-project/blob/main/README.md This describes the typical progression of an external signal through the Raindrop collection states, culminating in operator validation. It highlights the importance of human review before an entry is considered validated. ```text signal -> 00_INBOX -> analysis proposal -> operator validation -> 10_REVIEW / 20_LIBRARY / 90_ARCHIVE ``` -------------------------------- ### Controlled Taxonomy Tag Families Source: https://github.com/xxyoudeadpunkxx/decision-rain-library-project/blob/main/README.md Tags are a constrained grammar, not free-form labels. The system separates concerns into distinct tag families. New tag values require explicit operator approval. ```text authority/* truth/* status/* type/* domain/* source/* scenario/* risk/* stack/* fit/* next/* priority/* ``` -------------------------------- ### Truth States for Evidence Source: https://github.com/xxyoudeadpunkxx/decision-rain-library-project/blob/main/README.md Truth states follow a controlled vocabulary to describe the confidence or evidence state of information. This helps in accurately assessing the reliability of evidence. ```text truth/verified primary evidence, working test, or strong corroboration truth/plausible likely true but not tested enough truth/claimed asserted but not verified truth/conflicting credible sources disagree truth/outdated likely stale or obsolete truth/unknown insufficient evidence ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.