ShurIQ Content Flywheel — Launch Review

Lessons

Ready Monday

Pathways

Workshops

Pages Built

Domains

Publishing pipeline

Idea

›

Draft

›

Review

›

Ready

›

Published

›

Measured

Three Monday-launch lessons are ready. The other 27 are drafted with full frontmatter — platform cuts to be expanded as each enters its slot.

Live deployment

The flywheel is live as a published website built from the same vault YAML/MD via the Ruby builder. All artifacts deployed under the jonny@weareshur.com Cloudflare account.

Series hub https://content-series-b6l.pages.dev/series/shuriq-concept-flywheel

Series listing https://content-series-b6l.pages.dev/

Review site https://flywheel-review.pages.dev/

Monday window — three ready lessons

Slot	Lesson	Cuts
10:00	Discourse has weather ~1820 words. Fronts, saturation, dispersion as discourse vocabulary.	LinkedIn Article + 1300 + 7-thread + Bluesky 300 + IG
10:20	The spiral, not the pipeline ~1740 words. Holling Panarchy adaptive cycle as strategy lens.	LinkedIn Article + 1300 + 7-thread + Bluesky 300 + IG
10:40	Abstract enumerations hide the lede ~380 words. Named-story headlines vs. listicles — craft post.	LinkedIn short + Twitter 280 + Bluesky 300 + Threads

Calendar event: bfq2f62ul194l3mtc23ne5muis · America/New_York · 10:00–11:00 EST · 2026-04-27.

Project intent

Build a daily concept-snapshot publishing system. Each post captures one named concept anchoring ShurIQ, Totem Protocol, or Perceptagon thinking — written first-person, with named-story headlines, anti-slop reflexive, IP-firewalled to public-facing layers (1–2) only.

The goal is twofold: demonstrate the thesis in public — concepts that defend public health, public benefit, and shared-resource value flows, explained at the level of named stakeholders, not abstract enumerations — and build a durable concept pool as seed material for workshops, livestreams, and longer-form work.

Lesson distribution by pathway

Pathway	Lessons	Status	Domain
01-monday-launch	3	Ready	cognitive_ecology + content_craft
02-cognitive-ecology	7	Draft	cognitive_ecology
03-content-craft	1	Draft	content_craft
04-perceptagon	7	Draft	perceptagon
05-totem-protocol	6	Draft	totem_protocol
06-shuriq	3	Draft	shuriq
07-value-flow	3	Draft	value_flow
Total	30	—	—

01 · Monday Launch

3 ready · cognitive_ecology + content_craft

The launch trio that opens the public-facing thesis.

Discourse has weather — ready
The spiral, not the pipeline — ready
Abstract enumerations hide the lede — ready

02 · Cognitive Ecology

7 drafts · cognitive_ecology

Reading discourse as weather, sequencing intervention, declaring intent.

Tool calls as cycle phases
Symmetry shift: listener as sensor
Six states of discourse
Bridging before intervention
Declarative intent declared
Diversified, not productive
How to get unstuck

03 · Content Craft

1 draft · content_craft

Vocabulary as infrastructure for thinking.

Vocabulary is infrastructure

04 · Perceptagon

7 drafts · Public Lab lineage

Citizen sensing in public space — community measurement before centralized narrative.

Polluter shows up in thermal
Kite-mapping as infrastructure
Sensing before narrating
Restoration is a sensing loop
Citizen sensor mesh
Creative coding as field tool
Hot-air balloon public sky

05 · Totem Protocol

6 drafts · totem_protocol

Encoding intent as the primitive — identity, surfaces, and trails.

Encoding intent is the primitive
Multi-surface, not multi-platform
Associative trails over hierarchy
Agentic proxy: signal vs. implication
Identity primitives before integrations
Stakeholder intent is dynamic

06 · ShurIQ

3 drafts · shuriq

Rubrics, ranks, and observations against an articulated ideal state.

A rubric, not a dashboard
Stack rank is the argument
Observation against ideal state

07 · Value Flow

3 drafts · value_flow

Friction, proxy agents, and the preferred state — making public benefit computable.

Friction is a representation problem
Proxy agents defend watersheds
Preferred state made explicit

IP firewall — what stays public

ip_level: 1 — public phenomena, named published tools, cited public frameworks.
ip_level: 2 — named concepts we have framed.
Anything higher (methodology, tool chains, scoring weights, prompt templates) stays internal.
No client names. Anonymize to "a toy company," "a financial-services client," "a micro-drama studio."
Internal framework names (Totem Protocol, SBPI, Sense Collective framework) stay out of client-facing framing.

Workshop slate — seven sessions seeded by the queue

The 30 concepts cluster naturally into seven workshops and livestreams. Already in the queue — no net-new content required to run any of them. Pricing reflects audience and depth.

Reading discourse weather

Group · 90 min · 4 concepts

$249

Discourse, six states, bridging, vocabulary. Turn shoulder-feel into craft you can teach.

Content operators, strategists

Spiral strategy livestream

Livestream · 60 min · 4 concepts

Free

Holling Panarchy as strategy. Spiral, tool calls as cycle phases, diversified vs. productive, getting unstuck.

Strategy-curious public

Citizen sensing in public space

Group · 2 hrs · 5 concepts (Public Lab lineage)

$499

Polluter, kite-mapping, citizen mesh, hot-air balloon, restoration. Hands-on community sensing.

Makers, environmental advocates

Encoding intent — Totem primitives

Group · 90 min · 4 concepts

$399

Encoding intent, identity primitives, multi-surface, stakeholder intent. The technical case.

Technical builders, agent designers

Agentic proxies that defend value flows

Livestream · 60 min · 4 concepts

Free

Proxy agents defend watersheds, signal vs. implication, friction as representation, preferred state explicit.

Public-benefit orgs, watershed advocates

Rubrics, ranks, observations — ShurIQ

Group · 60 min · 3 concepts

$799

Rubric not dashboard, stack rank as argument, observation against ideal state. The brand-intel discipline.

Brand intel clients, strategists

Craft and listening

Livestream · 60 min · 3 concepts

Free

Abstract enumerations, symmetry shift, sensing before narrating. For makers and writers.

Writers, makers, creators

Sequencing

W1 is a candidate to run mid-week paired with the Monday launch posts — same audience, immediately relevant. W2 and W7 are the public-free livestreams that lift discovery without depleting the paid slate. W3, W4, W6 are the paid sessions where craft is taught. W5 (free) is the public-benefit invitation that anchors the value-flow thesis.

Build pipeline

One source of truth. The vault YAML/MD is rendered to static HTML by a Ruby builder and deployed to Cloudflare Pages.

Stage	What	Where
Source	vault YAML/MD	`content/series/shuriq-concept-flywheel/`
Builder	Ruby + ERB + Tailwind	`content/build.rb`
Output	94 static HTML pages	`content/_site/`
Deploy	`wrangler pages deploy`	project: `content-series`
CDN	Cloudflare Pages	jonny@weareshur.com

$ wrangler whoami
👋 Logged in as jonny@weareshur.com
$ ruby content/build.rb
✓ 94 pages built
$ wrangler pages deploy content/_site --project-name content-series --branch main
✓ https://content-series-b6l.pages.dev (HTTP 200)

Cloudflare account migration

This deploy is the first artifact under the jonny@weareshur.com Cloudflare account. Older artifacts on claude.shur.agent@gmail.com and getsteady@gmail.com remain live until explicit migration — none of them are torn down without sign-off (live client sites may carry external links).

Account	Status	Action
jonny@weareshur.com	Active — primary going forward	All new deploys land here
claude.shur.agent@gmail.com	Live legacy	Inventory pending; do not delete
getsteady@gmail.com	Live legacy	Inventory pending; do not delete

Source taxonomy

Nine-dimension folksonomy schema applied to every concept. Backward-compatible extension of the existing content_post type.

#	Dimension	Values
1	domain	cognitive_ecology · perceptagon · totem_protocol · shuriq · content_craft · value_flow
2	stage_in_spiral	release · reorganization · growth · saturation
3	audience_signal	technical · strategic · narrative · philosophical
4	ip_level	1 (public phenomena) · 2 (named concepts)
5	use_case_context	public_health · public_benefit · shared_resources · personal_agency · …
6	capability_uplift	one-sentence: what the stakeholder can now do
7	friction_pattern	intent_representation · keyword_alert_only · dashboard_not_rubric · …
8	source_vault	totem_terminal · totemvault_focused · external_import
9	canonical_precedent	public lineage / cited framework (required if ip_level: 1)

Cross-vault agent architecture (approved)

Agent	Activation	Role
VaultScanner	@VaultScanner / nightly	Read-only scan of both vaults. Writes candidate manifest with proposed tags + migration recommendations.
FolksonomyTagger	@FolksonomyTagger	Apply 9-dimension tags in-place to `totem-terminal`; sidecar previews for `totemvault-focused`.
VaultMigrator	@VaultMigrator (per-note, explicit)	Copy approved notes from `totemvault-focused` → `totem-terminal/imported/` with provenance frontmatter.

Scan manifest: 60 candidate notes. Triaged P1 (12 migrate) · P2 (24 tag-only) · P3 (24 hold for human review) · 4 already migrated this cycle.

Next steps — Monday 2026-04-27

Publish the three W1 lessons to LinkedIn at the 10:00 EST window.
Cross-link from LinkedIn back to the live pathway page on content-series-b6l.pages.dev.
Begin scheduling W2–W7 workshops. W1 (Reading discourse weather) is the candidate to run mid-week paired with the launch posts.
Use the 27 drafted lessons as the publishing queue for week 2 onwards. Promote to status: ready and add scheduled_for dates as the week is planned.
Expand platform_cuts (LinkedIn, Twitter, Bluesky) on each draft as it approaches its publication slot.

Pre-publish fact-check

Re-read each LinkedIn Article — voice consistency, no banned anti-slop words.
Verify all named entities are public companies / public projects.
Run IP Check checklist one more time on each ready lesson.
Set published_url to null until publish; update published_date after.
Auto-session-capture at end-of-day Monday.

Open questions for the review block

Workshop pricing — does the W3/W6 split ($499/$799) feel right for the audience tiers, or do we lift W3?
Should W1 (Reading discourse weather) ship on the launch week, or wait until lessons 1–3 have a week of engagement data?
Migration of legacy Cloudflare accounts — appetite to inventory in a single sitting, or roll up per-project?
Are the three Monday cuts the right opening trio, or do we lead with "Abstract enumerations" as the meta-craft frame?