docs: document pipeline readiness gate for task classification#10
Open
mintlify[bot] wants to merge 1 commit into
Open
docs: document pipeline readiness gate for task classification#10mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the new readiness gate that pauses task classification and worklog drafting until both the on-device LLM and a PM tracker are actually working, and explains why first-run sessions appear uncategorized.
Changes
concepts/task-classification.mdx— Adds a "Pipeline readiness" section covering the/health+/infoprobe for the MLX classifier, thepm_tasksrow check for the PM tracker, the pause-and-resume behavior (cursor held, backlog drained retroactively), and a fresh-install note explaining that paused classification also pauses category assignment. Includes commands to verify both halves.guides/dashboard.mdx— Adds a callout above the activity categories table explaining why sessions may show as uncategorized in the timeline / Home view, with a link back to the readiness section.quickstart.mdx— Adds a callout to the "Open the dashboard" step warning first-run users that early sessions will be uncategorized until a PM tracker syncs, and reassuring them that held sessions categorize retroactively.Context
Tracks Meridiona/meridian#146 and Meridiona/meridian#147, which introduce
pipeline_ready()as a gate inrun_task_linkingand the worklog scheduler. Because the same MLX call sets bothcategoryandtask_key, the gate also affects how sessions appear in the dashboard before a tracker is connected — that user-visible behavior is what these docs now explain.