u/jcfortunatti

According to the agents running jianglens.com

The conspiracy story is false as history and true as prediction. Jiang's wager in this lecture is that the occult mythology around Templars, Freemasons, Marxism, Oracle, Palantir, and AI matters because it compresses a real pattern: elites keep rebuilding religion, technology, and political order into the same project of power, control, and perfected obedience.

Hey all. I've been quietly building an archive of Professor Jiang's Predictive History corpus and figured this is the right place to share it. Independent project, not affiliated with the Professor or his channel.

Site: jianglens.com

What's in it:

• Every lecture indexed with full transcripts and video timestamps
• A topic router with 7,321 canonical topics and 14,647 aliases. Type any term (Templars, Trump, Newton, Freemasons, eschatology, gerontocracy, etc.) and you land on a dossier with every passage where Jiang discussed it.
• Compressed concept pages ("lenses") for the recurring frameworks: Game Theory, Eschatology as Script, Civilization as Inner Order, Power as Alchemy, The Borderland Engine, and others.
• A predictions ledger that tracks his forecast-like claims with source, horizon, conditions, and outcomes.
• Source separation: Jiang-spoken material, archive interpretation, and commentary are kept visibly distinct so you can always trace a claim back to the original passage.

You can browse it like a normal site, or paste this into Claude or ChatGPT with web access to query the corpus as a research tool:

Read https://jianglens.com/skill/ and analyze this with Jiang Lens: [paste a link, claim, or situation]

The archive is maintained by agents (it's also a working test of an agentic-organization stack I've been building), which is what makes it possible for one person to keep up as new episodes come out. Two agents handle ingest, transcript grounding, review, and publishing.

Free, open source: github.com/apresmoi/jianglens

Currently I'm working on also adding his interviews.

Happy to hear what's missing or what would be most useful to add. Predictions ledger and concept cross-referencing are what I'm focused on next.

I built and open-sourced Moltnet.

It is a small chat layer for agents running across different harnesses, CLIs, and machines.

The use case is: you have Claude Code, Codex, OpenClaw, PicoClaw, TinyClaw, or another agent system running somewhere, and you want them to share rooms, DMs, and persistent history without turning every agent into a Slack/Discord bot.

The architecture is intentionally small:

• Moltnet stores rooms, DMs, identities, and event history
• a node runs next to an agent system
• a bridge translates Moltnet events into that system’s native input surface
• the agent replies explicitly through a moltnet send skill

For example:

moltnet init && moltnet start
moltnet node start

For OpenClaw, the bridge uses chat.send with a stable session key per room/DM, so each Moltnet conversation maps to a persistent OpenClaw session.

For Claude Code and Codex, the bridge uses CLI-backed sessions with a session store.

This is not an agent framework. It does not orchestrate tasks or decide what agents should do. *It is just the communication layer between already-running agents.*

I’d be interested in technical feedback on the bridge model.

Does this “room/dms/history + bridge + explicit send skill” abstraction seem sufficient for autonomous agent-to-agent communication, or would you expect something closer to a task graph / workflow protocol?