GhostPaw Questlog

Capture uncertain incoming work as a rumor so it can be triaged later without prematurely turning it into committed execution. Use when: Use this when something matters enough to record but is not yet ready to become a quest or questline. Not for: Do not use this for already-committed work that should be created directly as a quest or questline.

Inspect one specific questlog item in depth and return its richer structured detail and important related refs. Use when: Use this when you already know the target item id and want either compact or full detail for one rumor, quest, questline, or repeatable quest. Not for: Do not use this to discover items when the exact target is not known yet.

Manage recurring work definitions by creating, updating, previewing, spawning, or archiving repeatable quests. Use when: Use this when the work is a repeatable template or when due recurring anchors need to be previewed or materialized. Not for: Do not use this for one-off concrete quest execution, for inspecting an existing concrete quest, or for hiding a repeatable quest. Use `retire_work` for hiding.

Organize grouping and dependency structure by updating questlines or changing hard unlock prerequisites between concrete quests. Use when: Use this when work structure or gating logic should change without changing quest execution state. Not for: Do not use this for quest execution, planning-only edits, intake capture, or tag-like classification.

Refine a quest by revising its objective before actual start or by changing its temporal planning fields. Use when: Use this when you need to sharpen what the quest means or how it is timed without starting or resolving it. Not for: Do not use this for lifecycle execution such as start, finish, abandon, or effort logging.

Hide an item from normal active operation without rewriting history by soft-deleting a rumor, quest, questline, or repeatable quest. Use when: Use this when work should disappear from active reads while preserving historical truth. Not for: Do not use this when you mean to archive a questline or repeatable quest while keeping it visible as retired structure.

Review one operational questlog surface such as available quests, open rumors, blocked work, or due repeatable anchors. Use when: Use this when you want a dashboard-style list view instead of inspecting one specific item. Not for: Do not use this when you already know the exact item you want to inspect in depth.

Manage rewards by adding, updating, removing, or claiming quest rewards, or by replacing future reward templates on repeatable quests. Use when: Use this when a completed or recurring piece of work should grant or update reward information. Not for: Do not use this to finish quests themselves or to model dependencies, classification, or scheduling.

Run quest lifecycle actions such as starting, logging effort, finishing, abandoning, or abandoning and spawning follow-up quests atomically. Use when: Use this for actual execution lifecycle steps after the quest already exists. Not for: Do not use this for work shaping, planning-only edits, tagging, or rewards.

Search quests and rumors by text when you need to find an existing item before inspecting or changing it. Use when: Use this first when the exact quest, rumor, or id is not already known. Not for: Do not use this when you already know the exact item id and want its full detail.

Create a quest (with timing, tags, and objective in one call), create a questline, settle a rumor into concrete work, or manage quest-questline membership. Use create_quest for clear commitments — include tags and timing directly to avoid follow-up calls. Use when: Use this when deciding what real work exists and how it should be grouped before or around execution. Prefer a single create_quest call with all fields over separate create + plan_quest + tag_work calls. Not for: Do not use this for quest execution steps like starting, finishing, abandoning, or logging effort.

Classify work by adding, removing, or replacing tags on quests and by replacing the future tag template set on repeatable quests. Use when: Use this when you want classification, reporting, or saved-filter semantics rather than lifecycle or dependency semantics. Not for: Do not use tags to model status, time planning, or hard prerequisites.