3
Posts Drafted
4
Post Templates
7
Concept Series
6
Week Calendar
5
Platforms
Publishing Pipeline
Idea
4
Draft
3
Review
0
Scheduled
0
Published
0
Measured
0

3 posts in draft. Review them in the tabs above, then move to scheduled.

Week 1 — Post Queue
Day Post Type Status Platform
MON
Declarative Intent: When the Architecture Finally Matches the Problem
Origin story + v0.1 validation. 2,000 words + 5 platform cuts.
concept_series Draft LinkedIn, Twitter, IG, Bluesky
WED
The Day We Realized Templates Couldn't Scale
350.org / Rock 'n Renew throwback. Connects to Declarative Intent thesis.
throwback Draft LinkedIn, Twitter
FRI
TIL: The Content Pipeline Is the Product Demo
Meta post — building the publishing system using the system it describes.
til Draft LinkedIn, Twitter
6-Week Content Calendar
Week Monday (Long-form) Wednesday (Short) Friday (Metric/Result)
WK 1 Declarative Intent blog 350.org throwback TIL: Pipeline is the demo
WK 2 Rock 'n Renew origin story Permaculture/systems design parallel Brand Power Score methodology
WK 3 Negative Space concept 350.org growth numbers Gap analysis result (anonymized)
WK 4 Value Flow Ontology Crypto fund provenance lesson Layered Ontology case study
WK 5 The ContentFactory (meta) Cougaar → Totem lineage Deployment stats (12+ sites)
WK 6 Trailblazer vision NYU Gallatin systems thinking Month 1 retrospective

After Week 6: Monday (long-form), Wednesday (short/throwback), Friday (current result). Rhythm continues indefinitely.

Concept Series Map

Each series connects tactical work to deeper ideas. TIL and Dev Workbench posts reference these as their conceptual backbone.

Declarative Intent

DRAFT READY — Post #1
Second-order systems stuck running on first-order logic circuitry

Negative Space

NOT STARTED — Week 3
What's missing matters more than what's present

Value Flow Ontology

NOT STARTED — Week 4
REA semantics for business intelligence

Knowledge Graphs for Everyone

NOT STARTED
Why structural analysis beats keyword search

The Palantir for Small Business

CALENDAR EXISTS
Democratizing intelligence infrastructure

Trailblazer

IDEATION — Week 6
Flow-state capture and process automation

The ContentFactory

NOT STARTED — Week 5
The content pipeline itself is the product demo

Declarative Intent: When the Architecture Finally Matches the Problem

Fact-Check Required
  • "Century-old global health NGO" — AHA founded 1924 = ~102 years. Accurate.
  • "50+ business intelligence sessions this month" — verify exact count
  • "Half a dozen major enterprise brands" — changed from Fortune 500, verify
  • "Since 2004 at NYU Gallatin" — verify start date
  • 350.org: "24 million participants across 189 countries" — verify
  • "Single largest day of environmental collective action" — verify event name
  • The 2018 workshop / fictional therapist — name, location, context
  • Wireframe sessions with David — verify timeline

This has been the most exciting month of my career.

The software framework I've been building for the better part of a decade just hit v0.1. The early results are beyond what I dared to project. Over 50 business intelligence sessions this month. Half a dozen major enterprise brands. A century-old global health NGO. Four different healthcare subcategories, from fashion brands to scrubs.

And somewhere in that sprint, a brilliant writing teacher and author gave feedback on the report writer's voice. It shook something loose. A workshop I gave in 2018 came flooding back — a fictional relationship therapist and life coach, designed as a prototype for AI agents that could actually hold space for human complexity.

I've been working on and with AI agents since 2004, first at NYU Gallatin studying complex adaptive systems, then at NYU ITP building interactive telecommunications projects, as part of what's now a two-decade research thread on collaborative sensemaking, collective intelligence, and cybernetics.

The Template That Couldn't Scale

Before any of this was software, it was field work.

Erin and I started Rock 'n Renew as a vehicle for something we could see clearly from the inside: local systems could be dramatically improved through targeted supplemental programming. Traditional science-based curriculum in schools, combined with hands-on training in permaculture design, biodynamics, ecological restoration, stormwater management, native plant installations, rain gardens, engineered wetlands.

The model put artists and musicians at the center of regional organizations. Touring artists became continuous power sources for legislation, local activism, public awareness campaigns, collective action. We worked with 350.org on the PowerShift campaigns and campus climate challenges. We partnered with NRDC, produced events with the Download Festival, Snoop Dogg, Modest Mouse, ran plastic bag ban campaigns.

The gaps were obvious. Working through the various layers of each system, we sought to perfect a model we could then scale through a kind of template that included all the administration and governance.

The tools were not there.

I tried, many times over 15 years, and found the same bottleneck. The points in the system where the resource requirements and administrative work simply didn't scale. Too much work for the artists. Too much reliance on trust and not enough oversight. Successful programs dependent on individuals who just made it work but couldn't train their replacement or hand off the reins when they were ready to move on.

Templates couldn't hold the amount of human innovation, intuition, social networking and regular networking. Network effects were dependent on fragile, sensitive, and distinct relationships that had no parallel elsewhere.

The Matchmaking Problem

Matchmaking between stakeholders — to share the massive amount of local knowledge that accrues with each successful project, event, or campaign — was nowhere close to accurately capturing the value flows between stakeholders. The conditional logic which acts as circuitry between value flow channels — marketing, advertising, public will, intent — was invisible to the systems that needed it most.

Second-order systems stuck running on first-order logic circuitry.

The raw signal log of transactions which represent the moving parts of a system, as it broadcasts the ongoing enactment of its world model, includes dynamic conditional logic. If/and, OR statements, graphs of arrays of associative trails. These signals are barely registering by the observers and network participants who attempt to search for examples of successful circuit design for their particular problem.

They have no reliable database to search. No consistent query language. No search terms they can wield in repeatable, programmatic fashion.

Instead, people scroll Reddit forums, clicking "next" through pages of results, searching for the needle-in-a-haystack information that is actually buried in the community they participate in every day. Occasionally, a rare keeper-of-keys person, a networking wizard, the unicorn known as the spoke-maker, comes along. They just know everyone you should know when you have this kind of problem.

You mention that you're preparing to hire a wetland engineer for a groundwater sampling project on the local river. They remember that the town next door did a study of that river last year. It has the information you need. You don't need to spend any money to get it.

The Wireframe Sessions

Seeing this problem play out across dozens of perspectives and industries over the last decade led to many wireframe sessions with David Muller, where we had a strong intuition about what the solution would look like.

There's seeing it first in your mind's eye. Then you scribble it on a notepad. Then you mock it up in a design program. Get a wireframe going. Even get the backend to populate data.

But the problem was never at that level.

We've had the technical systems to solve this at the database, server, and front-end design level for decades. The problem has always been at the individual knowledge worker level. The day-to-day notetaking. The emailing. The Slack and Telegram and Discord server-hopping.

  • information capture.
  • information storage.
  • information retrieval.
  • information traversal.
  • querying and search.
  • networking across social networks and identities.
  • Identity management. Preference and intent management. Declarative logic. Coordination. Sensemaking. Collective intelligence.

What the Crypto Boom Left Behind

Crypto and blockchain opened a lot of doors into the viable problem space.

Some of those doors led off a cliff.

A lot of poisonous substances came from the crypto boom. But some trace amounts of gold and silver have been accruing amid the noise.

Self-sovereignty. Cryptographically guaranteed provenance. Intent. A ledger of all transactions. Finality.

All of these can be invisible. No tokens required to achieve the goals of the original vision. Token economics are supplemental — they provide affordances for a diverse stream of interests. We can satisfy those interests without any tradeoffs with conventional systems.

No visible trace of crypto need appear for those not interested. We don't elaborate as to whether Uber's app is written in TypeScript or Ruby on Rails. There's no reason to highlight that Totem Protocol provides the means for fully decentralized operation via onchain-first network routing.

It's a function of menu settings and configuration at the project level for any project using Totem Protocol's schema.

v0.1

ShurIQ. Totem Protocol. Perceptagon Interactive Design.

Fifty sessions this month. Major enterprise brands, a century-old NGO, four healthcare verticals, and the feedback from every one of them confirming what we drew on napkins a decade ago: the system works.

Not because the technology is new. Because the architecture finally matches the problem.

The sprint continues. Framework v0.1 ships by July 4. The content pipeline that produces this post is itself running on the system it describes. If that sounds circular, you're getting the idea.

More to come.


Jonny Dubowsky is co-founder of Sense Collective and architect of Totem Protocol. He has been designing multi-agent systems and collective intelligence frameworks since 2004.

Platform Cuts

LinkedIn — Long Post ~1,300 char
I've been building this system for 15 years. It started with Rock 'n Renew — artists and musicians at the center of regional organizations, powering legislation, activism, and public awareness. We helped grow 350.org from 3,000 members to 24 million across 189 countries. The model worked. But it couldn't scale. Too much reliance on individuals who just made it work. Templates couldn't hold the human intuition. The conditional logic between value flow channels — marketing, intent, public will — was invisible to the systems that needed it. This month, the framework I've been designing since my NYU days finally hit v0.1. Over 50 business intelligence sessions. Major enterprise brands. A century-old global health NGO. Four healthcare verticals. The feedback confirms what we drew on napkins a decade ago: the architecture finally matches the problem. It's not a new technology. It's what happens when you combine collective intelligence research, cybernetics, and systems engineering — then hand it the right tools. ShurIQ. Totem Protocol. Fifteen years to v0.1. #SystemsThinking #CollectiveIntelligence #AI #BusinessIntelligence
LinkedIn — Short Post ~700 char
Second-order systems stuck running on first-order logic circuitry. That's been the problem for 15 years. People scrolling Reddit forums clicking "next" through pages of results, searching for information buried in the community they participate in every day. This month I ran 50+ business intelligence sessions with major enterprise brands, a global health NGO, and four healthcare verticals — all on a framework I've been building since my time at NYU. The architecture finally matches the problem. #TotemProtocol #ShurIQ #CollectiveIntelligence
Twitter/X — Thread (7 posts) 7 × 280 char
1/ I've been designing AI agent systems since 2004. Before ChatGPT. Before transformers. This month, the framework hit v0.1. Thread on what I learned. 2/ Started at NYU studying complex adaptive systems. The question: how do groups make sense of complexity together? 3/ Built Rock 'n Renew with my wife Erin. Artists + musicians powering environmental programs. Helped grow 350.org from 3K to 24M across 189 countries. 4/ The model worked locally. But it couldn't scale. Templates couldn't hold the human innovation. Network effects depended on fragile relationships with no parallel elsewhere. 5/ The bottleneck was never the database or the front end. It was information capture, storage, retrieval, traversal, and search at the individual knowledge worker level. 6/ Crypto opened doors — some led off cliffs. But self-sovereignty, provenance, intent ledgers, and finality? Those are load-bearing concepts. They don't need tokens to work. 7/ This month: v0.1. 50+ BI sessions. Major enterprise brands. The feedback confirms what we drew on napkins a decade ago. The architecture finally matches the problem.
Instagram Caption ~400 char
15 years of building. This month. 50+ business intelligence sessions. Major enterprise brands. A 100-year-old health NGO. Four healthcare verticals. Started with artists and musicians running environmental programs. Ended up building the AI systems that make collective intelligence actually work at scale. The architecture finally matches the problem. Link in bio for the full story. #SystemsDesign #AI #CollectiveIntelligence #FromTheGround
Bluesky ~300 char
Been building multi-agent AI systems since before ChatGPT existed. This month: 50+ BI sessions, major enterprise clients, framework at v0.1. Not new tech. Just 15 years of collective intelligence research meeting the right moment.

Throwback: The Day We Realized Templates Couldn't Scale

In 2009, Erin and I were running Rock 'n Renew — artists and musicians at the center of regional environmental organizations. Permaculture design, rain gardens, engineered wetlands, campus climate challenges. We partnered with 350.org, NRDC, ran events with Download Festival, Snoop Dogg, Modest Mouse.

It worked. We helped grow 350.org from 3,000 members at 8 colleges to millions of participants across 189 countries. Part of the single largest day of environmental collective action in history.

Then the scaling question hit. The programs that worked depended on people who just made it work. They couldn't train replacements or hand off the reins. The administrative template we built to capture the model was always incomplete — templates couldn't hold the amount of human innovation, intuition, and local relationship knowledge.

That problem drove the next 15 years of research. The bottleneck was never the database or the front end. It was information capture, storage, and retrieval at the individual knowledge worker level. The conditional logic between value flow channels was invisible to the systems that needed it most.

Today that research is ShurIQ and Totem Protocol. The architecture that makes collective intelligence operational at scale. The same problem, finally matched to the right tools.

Platform Cuts

LinkedIn — Medium Post ~900 char
In 2009, Erin and I were running Rock 'n Renew — artists and musicians powering environmental programs. Permaculture, rain gardens, campus climate challenges. We partnered with 350.org, NRDC, ran events with Download Festival and Snoop Dogg. It worked. 350.org grew from 3,000 members to millions worldwide. Then the scaling question hit. Programs depended on people who just made it work. They couldn't train replacements. Our admin templates couldn't hold the human innovation and relationship knowledge. That bottleneck drove the next 15 years. Today it's ShurIQ and Totem Protocol — the same problem, finally matched to the right architecture. #ThrowbackThursday #CollectiveIntelligence #SystemsDesign
Twitter/X ~250 char
2009: We helped grow 350.org from 3K to millions. The programs worked. But they couldn't scale — templates couldn't hold the human intuition. That bottleneck drove 15 years of research. Today it's ShurIQ.

TIL: The Content Pipeline Is the Product Demo

Today I set up the publishing system for my LinkedIn content launch. Four post types. A vault-native pipeline that tracks posts from idea through published. Templates with frontmatter that connects every post to the feature it showcases and the concept series it feeds.

The system I used to build this is the same system I sell. Session records from today's work become tomorrow's TIL posts. The gap analysis that identified what to write about runs on the same engine that analyzes Fortune 500 brands.

Every post I publish is a live demo of the product. That's not a marketing gimmick — it's the architecture working as designed.

Platform Cuts

LinkedIn ~500 char
TIL: The best product demo is using the product in public. Today I built the publishing pipeline for this LinkedIn initiative. Four post types. Vault-native tracking. Templates that connect every post to the feature it showcases. The system I used to build this is the same system I sell. Session records become TIL posts. The gap analysis that finds what to write about runs on the same engine that analyzes enterprise brands. Every post is a live demo. That's the architecture working as designed. #TIL #BuildInPublic #ShurIQ
Twitter/X ~250 char
TIL: The best product demo is using the product in public. Built a publishing pipeline today. The system that produces the posts is the same system I sell to enterprise clients. Every post = live demo. That's the architecture.
Post-Type Templates

Four templates. Each connects a tactical action to a feature showcase to a concept series. Every post is structured, trackable, and feeds the next one.

Today I Learned

300–600 char · 2-3x/week

Quick-hit insight from a session. Approachable, human, establishes daily learning cadence.

1. Hook line (the surprise) 2. Context (what I was doing) 3. The insight (concrete) 4. So what (why it matters)

Developer Workbench

800–1,500 char · 1x/week

Show what I'm building. Code/context engineering angle. Showcases a specific product feature in action.

1. What I'm working on 2. Problem it solves 3. How the feature works 4. Pointer to concept series 5. Call to action

Concept Series

1,500–2,500 words · 1x/week

Deep dives into the ideas behind the tools. Intellectual foundation. SEO-friendly, linkable, persistent.

1. Opening hook (question/tension) 2. Historical context 3. How we implement it 4. What it enables (real results) 5. What's next (open question)

Throwback / Origin

600–1,200 char · 1x/week

Establish credibility by connecting current work to 15+ years of building. Not nostalgia — provenance.

1. The moment (specific, dated) 2. What I was solving 3. What I built or learned 4. How it connects to now 5. The through-line
Infrastructure Status
Component Status Location
ContentFactory Agent Spec Approved v1.0.0 Totem-framework/agents/
Content Factory Skill Operational ~/.dotfiles/ai/skills/
Showrunner CLI Production-ready ~/projects/content-factory/
Anti-Slop Detector 16 checks active showrunner/slop_detector.py
LinkedIn Formatter Operational showrunner/linkedin_formatter.py
Post-Type Templates (4) Created today system/templates/content-post-*.md
Content Folder Structure Created today sense-collective/content/
Content-Briefs.base Active Totem-framework/
Publishing-Pipeline.base Spec written, needs creation in Obsidian PUBLISHING-PIPELINE-BASE-SPEC.md
LinkedIn Profile Overhaul Draft ready linkedin-overhaul-draft.md
Content Hub Website Not started
Session-to-Content Bridge Not started
Frontmatter Schema: content_post
type: content_post
post_type: til | dev_workbench | concept_series | throwback
status: idea | draft | review | scheduled | published | measured
series_name: ""          # concept series this belongs to
feature_showcase: ""     # ShurIQ feature demonstrated
source_path: ""          # wikilink to origin document
platform: linkedin       # primary platform target
scheduled_date: null
published_url: ""
published_date: null
engagement:
  impressions: 0
  reactions: 0
  comments: 0
  shares: 0
Connection Pattern

Every post connects three layers. This is the content architecture.

Tactical Action
What I built today
TIL / Dev Workbench
Feature Showcase
What it demonstrates
ShurIQ / Totem capability
Concept Series
Why it matters
Deep dive / SEO / persistent