Digests keep members current. Assets bring strangers in. A searchable asset — a how-to, a teardown, a comparison, a template — is a community discussion distilled, verified, credited, and published where search engines and newcomers can find it. This lesson builds the gate that decides what gets converted, and the pipeline that converts it fairly.

The flywheel gate: publish or not

Not every thread deserves permanence. Run each candidate through four questions:

1. Recurring value? Will a stranger have this problem in six months? A filing-footnote technique recurs; a "what did you think of Tuesday's call?" does not. 2. Verified? Has the approach been tested by more than one member, or at least Stress-tested by critique? Single untested claims stay in the archive; they do not become articles. 3. Consent and credit clear? Have contributing members agreed to reuse, and do you know exactly whom to credit? Silence is not consent. 4. Better as an asset? Does distillation actually help — a clean sequence a newcomer can follow — or does the thread's back-and-forth carry the lesson? Some discussions teach through disagreement and should stay discussions with a good summary pointer.

Score honestly. Publishing ten thin derivatives clogs your public library and embarrasses the contributors. Publishing one solid asset per month that ranks, gets linked, and gets cited inside the community compounds for years. The gate's default answer is "not yet" — and "not yet" should come with a reason and a path ("two more tested examples and it qualifies").

The community-to-asset pipeline

When a thread passes, run five steps:

1. Nominate. Anyone may nominate with a link and one line on recurring value. Keep a visible nominations list so selection never looks like favoritism.

2. Verify. A human checks claims against originals, tests the method if testable, and marks anything single-sourced as such. AI may draft a fact-check checklist ("claims made, evidence quoted, gaps flagged") but the human signs it.

3. Consent. Ask each quoted contributor explicitly: "May we adapt this thread into a public article crediting you by name with a link to the original? You can review the draft first." Record yeses in writing. Offer opt-outs: credit, anonymous credit ("a community member"), or exclusion. Respect the choice without pressure.

4. Distill. Write the asset fresh — do not concatenate posts. Structure it as problem, method, worked example, pitfalls, and links back to the thread and contributors. AI may draft from the brief, but a human rewrites for accuracy and voice. The asset must stand alone for a stranger while pointing home to the community.

5. Publish and loop back. Publish where search can find it (website hub from Lesson 69.2), announce it inside the community with contributor names first, and link the asset back into the archive so future threads cite it instead of repeating it. Track one metric per asset: search visits, inbound joins citing it, or repeat internal citations.

That final loop-back is the flywheel's first turn: community content becomes searchable content that brings traffic that can become community — the subject of Class 71.

Maintain the assets or they rot. Every published asset needs an owner, a review date, and a visible "last verified" line. Filing procedures change, tools rename features, prices move. A quarterly pass — AI drafts a staleness report listing assets with outdated references or new contradicting threads, a human verifies and updates — keeps the library trustworthy. An asset that misleads a newcomer costs more than no asset at all, because the newcomer blames the community, not the calendar. Version briefly when you update ("updated March 2026: new footnote format"), so repeat visitors see living knowledge rather than frozen guesses.

The fairness contract

Publish your reuse terms once, visibly, before anyone's work is converted: what may be reused (threads in designated categories), how credit works (name + link, always), what review contributors get (draft preview on request), and what they can veto (name use, not factual correction of their error — errors get corrected with a note). A tailor's circle version fits in three sentences: "Monthly standouts become public how-tos with your name and shop link. You see the draft first. Say no anytime and it stays inside."

This contract is also a growth tool. Contributors who have been credited fairly once bring their best work next time. Contributors who discover their words repurposed without asking leave — and tell others.

Exercise: convert one thread

Create COMMUNITY-TO-ASSET.md containing your gate (the four questions with pass thresholds), your pipeline (who nominates, verifies, asks consent, distills, publishes), and your fairness contract (reuse scope, credit rule, preview right, veto rule). Then execute it once: nominate one real thread, record consents, and ship or outline one asset with full credits and backlinks.

Finish line: a reusable pipeline document plus one asset — published or fully drafted with consents logged — that a stranger could use without joining.

Verify quickly: show the asset to a non-member with the target problem. If they can follow it and can name who taught it, both distillation and credit work.

Common failure mode: converting too early — five near-identical beginner threads rushed into five competing articles. Combine, verify, then publish once, well.

Check your understanding

1. What are the four publish-or-not questions? 2. What happens at each of the five pipeline steps? 3. Why must consent be explicit rather than assumed from participation?

Next

Class 70 turned talk into assets. Class 71 closes the loop — mapping the full flywheel, diagnosing its broken arrows, and building return loops that keep it spinning.