docs: Article A master — the dynamic-forms tutorial - #26
Merged
Conversation
Hands-on walk from an empty dict to a validated round trip: the base form and the batching rule; the six 0.5.0 constructs one at a time (snippets lifted verbatim from REFERENCE_FORM, each with the answer it validates to, plus a live proof that confirm refuses a default); the same dict on four hosts (widget / batched questions / MCP elicitation / markdown, with the skeleton tail); the return path (deterministic parse -> validate -> re-ask only the failing field); when not to build any of it; and a marked 0.6.0 section for ranking + assumption review. Verification before commit: every python block was extracted from this file and executed — 17 blocks against attune-forms 0.5.0 from PyPI in a fresh venv, 2 (the 0.6.0 section) against main — and every printed number in the text is the number the code printed. ~1,450 prose words + 19 code blocks. Master per the master/projection rule; not projected. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
silversurfer562
marked this pull request as ready for review
August 16, 2026 04:22
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
Adds
docs/tutorial-dynamic-forms.md, the verified master of Article A from the content plan — the hands-on tutorial. Empty dict → batching rule → the six 0.5.0 constructs one at a time (snippets lifted verbatim fromREFERENCE_FORM, each with the answer it validates to; a live proof that confirm refuses adefault) → the same dict on four hosts (widget / batched questions / MCP elicitation / markdown, skeleton tail shown) → the return path (deterministic parse → validate → re-ask only the failing field) → when not to build any of it → a clearly marked 0.6.0 section for ranking + assumption review.~1,450 prose words + 19 code blocks. Voice: first person, every stated number is a printed number.
Verification (the master's contract)
Every python block was extracted from this file and executed as plain scripts:
attune-forms==0.5.0from PyPI in a fresh venv — the version a reader gets frompip installtoday.main(be1bfc1), stated in the text as "on main, ships in 0.6.0".---rule), and a widget-size number that varied with the per-render instance id (now pinned withinstance_id="tutorial"→ 22,200 bytes).Draft for the chair's read. Not projected anywhere. Projection order per the plan: B is on main (#23) → this → posts. Before projecting after 0.6.0 ships, flip §7's framing from "on main" to "in 0.6.0" and re-run the blocks against the released package.
🤖 Generated with Claude Code