Shipping v0.1.6 - #6
Open
inosaint wants to merge 7 commits into
Open
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Orchestrator step 1: hand to Curator immediately when dataset is provided; do not ask posture or direction before Curator has seen the data - Orchestrator: add Stage Transition Commentary rule — brief what the previous skill produced and what the user decided before handing to the next skill - Curator: add step 6 — after reporting data fitness, ask posture and analytical direction as one combined button-ready interaction before cleaning and shaping - Curator handoff notes: include confirmed posture and direction Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Stage transitions are orchestrator-driven — invoke next skill immediately after commentary, do not wait for user between stages. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Analyst now proposes a narrative_arc (ordered tier sequence with claim, evidence, chart_form, and transition_to_next) when the user selects directions that stack naturally. Narrator gains arc mode in the Language Load Contract: per-tier language load, claim copy, and connective transition prose, with arc_tiers in the handoff contract for Designer. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…res it Curator step 6 now detects stackable dimensions and presents a multi-tier arc as a direction option, resolved before Analyst runs. Curator step 9 handoff includes narrative_intent (single or multi-tier arc with tier sequence). Analyst steps 6-7 now receive arc intent from Curator rather than proposing it mid-analysis — Analyst structures and evidences the confirmed arc, not discovers it. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
1 participant
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
RELEASE.mdwith step-by-step release checklist covering version refs, doc review across all surfaces, and npm publish smoke testPlanned for this release (not yet implemented)
data-vizard uninstallCLI subcommandTest plan
npm pack --dry-runto confirm package contentsnpm publish:npx --yes data-vizard@0.1.6 --version🤖 Generated with Claude Code