Fragment Practice
Guides are compact documents for applying structure more deliberately.
This page is for people who need clear practical guidance without a full toolkit: something that explains a distinction, a working pattern, or a usable operating move in a concise form.
In Fragment Practice, guides are not long manuals. They are focused explanatory documents designed to help someone understand what matters, what to look for, and how to apply one useful structure in context.
Why choose a guide
A guide is useful when the main need is not a full kit or worksheet, but a stronger reading of the issue and a clearer sense of what to do with it.
Focused explanation
Orientation
Current guide snapshot
The guide layer is intentionally compact. The aim is not volume, but crisp, portable explanation that genuinely helps someone apply the work more clearly.
Available now
In development
Planned
Guides
This is the current visible guide layer, including in-progress and planned entries.
Continuity Review Guide
A short practical guide for diagnosing where workflows reset, where context is lost, and what helps work continue more cleanly across sessions and people.
Decision Clarity Guide
A concise guide for separating the real decision from surrounding noise, mixed requests, and premature execution pressure.
Human-AI Boundary Guide
A practical guide to clarifying assistive use, retained authority, review obligations, and escalation points in human-AI work.
What makes something a guide here
A guide is not only a short article. It is a compact, reusable document that helps someone apply a distinction or working structure with more confidence.
A practical explanation
A stronger distinction
A lighter bridge
Best for people who want to
Use a guide when you want to:
- understand one practical issue more clearly
- apply a distinction without needing a full kit
- orient yourself before choosing the next structure
- move from concept into small practical use
- gain a better reading before making a decision or handoff
Less suited when you need:
- a repeatable fill-in form for the same task
- a worksheet for exploring a still-mixed issue
- a broader package with multiple assets and tools
- heavy custom support across a live operational situation
- a finalized implementation document for team-wide adoption
Other ways to browse
Guides are one format path. These routes are better when you want a wider or more problem-led view.
How guides relate to the rest of the studio
Guides work best as part of a larger movement through writing, framework, knowledge, and practice.
Writing
Framework
Guide
Practice
Best next step
Guides matter because not every useful next move needs a full toolkit. Sometimes the first need is a clearer explanation that changes how the issue is read.
A good guide helps someone move from vague recognition toward more deliberate use. It reduces confusion, sharpens the distinction, and makes the next structure easier to choose.