I've just completed my CMS for storing and rendering Remote-Viewing Stories

It's in Python and the code is here:

- https://github.com/DavidLyon66/Heichalot-CMS/tree/main

It's designed to work as an offline database/CMS for remote-viewing stories and History Information.

This is so cool

Thank you.

I'm going to give a demonstration of it and Ai-assisted remote-viewing in Europe next month.

In a way, I'm representing Farsight and the people of the Forum here in probably the first Public demonstration of the Farsight Ai-remote-viewing protocol.

Wish me luck !

Good luck! if you record the presentation make sure you come share the link. :)

Good Luck !

Offline Content Management System for Remote-Viewing Sessions

Heichalot-CMS is a lightweight, offline-first system designed to collect, structure, and transform remote-viewing session data into reusable, distributable content.

The core idea is simple:

Take raw inputs (transcripts, sessions, videos) → convert them into a structured narrative format offline. That can be on the computer/laptop/phone, on an SD-Card, USB-Drive or a Storage. Backed up in case they are ever removed from the Internet.

🧩 The story.md concept

Each session is stored as a single markdown file:

---
kind: story
source: youtube
source_video_id: XXXXX
---

# Session Title

""" NARRATOR
Session content appears here as a clean, readable narrative block.
"""

This format is:

- human-readable
- AI-readable
- easy to render into video, PDF, HTML (including 3D world ThreeJS)
- stable across tools and environments

📁 Core CMS Structure
cms/
entry-0000001/
story.md
assets/
entry-0000002/
story.md
assets/

Each entry represents one session.

- story.md → primary narrative
- assets/ → supporting data (original transcripts, translations, metadata)

This allows the system to scale cleanly while keeping each session self-contained.

🛠 Tools Layer

tools/
ytv2cms.py
renderpdf.py
renderhtml.py
startproduction.py
extensions/

These scripts operate on the CMS data and convert it into different forms.

🔌 Extensions Layer

tools/extensions/
registry.py
translation_google.py
translation_libre.py
translation_argos.py
ytdlp_metadata.py
diarization.py

Extensions provide optional capabilities:

- translation - translate from source language to local language, ie German->English, English->German
- metadata extraction

They are loaded dynamically and do not affect the core system if absent.

⚙️ Key Scripts

👉 ytv2cms.py

Converts a YouTube video into a structured story.md.

- extracts transcript
- formats into narrative
- optionally translates
- writes clean CMS entries

This bridges raw video → structured dataset

👉harvestcreatorcontent.py

Scans an entire creator/channel and builds a corpus. Such as Future Forecasting Group, Farsight, Bulgarian Remote-Viewers, Edward O'Riordan, Down the Rabbit Hole, David Powell.

- collects all video URLs
- builds a producer manifest
- feeds videos into the CMS pipeline

This enables bulk ingestion at scale, not just single sessions

👉 renderpdf.py

- Turns story.md into printable PDF reports.
- Converts session data into distributable documents

👉renderhtml.py

Renders sessions as web-ready HTML.

- Enables browser-based viewing and embedding

👉startproduction.py

- Prepares a production workspace from a CMS entry.

- Connects structured data to video/visual pipelines

registry.py (Extensions)

Dynamic capability loader.

- detects available extensions
- enables features without breaking core tools

👉 This allows free vs premium capability layers without changing the main system

Translation Extensions
- Google (high-quality, paid)
- Libre / Argos (free, offline-capable)

Enables multilingual session archives

👉diarization.py (future)

Speaker separation (interviewer vs viewer)

- Moves from transcripts → structured dialogue

🧭 What’s new here

This system introduces a different approach:

- sessions are treated as structured data, not just media everything is offline-capable
content is portable and reproducible.
- ingestion, transformation, and rendering are separated

The result is a pipeline that can:

- collect remote-viewing sessions at scale
- normalize them into a consistent format
- prepare them for analysis, publishing, or further processing

🔚 Summary

Heichalot-CMS is not just a storage system—it is a content transformation pipeline.

It turns scattered session recordings → structured, reusable knowledge

If there’s interest, I can share examples of generated entries or demonstrate how a full channel is converted into a CMS dataset.

I have been working on the youtube import, and made a new tool "lscms.py" that does a listing of all recent entries/remote-viewings in the cms.

For example:

dlyon@FMVS90TRD1:~/heichalot-tech$ python3 tools/lscms.py
entry-0000023 2026-04-03 13:48 YouTube Import (hgbITnYUP8M)
entry-0000024 2026-04-03 02:48 The Fire Brigade Station at Edward and Ann Street Brisbane
entry-0000022 2026-04-02 13:19 Herencia Filipinas
entry-0000021 2026-04-01 21:34 Giro Giro of Mount Isa
entry-0000007 2026-04-01 20:43 Tokyo Station Remote-Viewing
* entry-0000003 2026-04-01 20:04 Bondi Beach
entry-0000020 2026-04-01 13:12 Events Predictions
entry-0000011 2026-04-01 03:24 the proto-Kabbalistic group in Izmir
entry-0000012 2026-04-01 03:22 Remote-Viewing the name 'ostraliye'
entry-0000016 2026-04-01 03:18 Lenah Valley Synagogue

Mainly needed because I can generate so many remote-viewings that the system now needs a management tool to be able to list them.

This is before starting on a more aggressive remote-viewing video harvesting from youtube that I am about to start.

I'm now able to publish and upload remote-viewing stories to my ftp site:

dlyon@FMVS90TRD1:~/heichalot-tech$ python3 uploadcms.py --upload
CMS uploader
------------
Config file: /home/dlyon/.heichalotcms/config.ini
CMS dir: /home/dlyon/heichalot-tech/cms
publish.json: /home/dlyon/heichalot-tech/cms/publish.json
Published dir: /home/dlyon/heichalot-tech/cms/published
Zip file: /home/dlyon/heichalot-tech/cms/published/cms-2026-04-08.zip
Entries:
- entry-0000032

FTP host: ftp.xx.d
FTP port: 21
FTP remote dir: /
FTP mode: FTP
Passive mode: yes

Creating zip: /home/dlyon/heichalot-tech/cms/published/cms-2026-04-08.zip
Files added: 1

Uploading cms-2026-04-08.zip to FTP server...
Upload complete.

It's not only my remote-viewings, but for others. The system has the capacity to store, and preserve all the remote-viewings from the best remote-viewers no matter which alignment-group they are in. Ie European, American, other.

All held on a searchable system offline if you want.

A lot has happened since my last post. I have added a web front-end and now am able to publish my some of my Ai remote-viewing stories to the internet. Not everything yet because I have a backlog, but as many as I can.

I'm working on the lost Jewish History of Australia:

https://heichalot.tech/cms/tag/ljh-ostraliye

and the lost Jewish History of Asia. Including lost information on ShinTo in Japan and what it all means:

https://heichalot.tech/cms/tag/ljh-asia

and a new story about the Lost History of Humanity:

https://heichalot.tech/cms/tag/genesis-0

Great stuff David!
Thanks for sharing.
Can you do private viewing also?
I have a project I’m working on.
Mark

Thanks!