The World of Splectrum

Home > Engineering > Personas > Public Conscious Persona > Current

Splectrum — Public Conscious Persona 1.0

This page describes how the blog operates as Splectrum’s public conscious persona. The concept is introduced in The Blog as Public Conscious Persona — this page holds the technical detail.

The model

Pipeline

Full pipeline flow diagram

submissions/        — raw material arrives here, uncategorised
                      (surfaced from other repos via Mycelium)
        ↓
    conscious       — analyse, discuss, decide destination
    thought           ↓ research / postpone → splectrum-explore
    handling          ↓ draft-ready → drafts/
        ↓
drafts/             — accepted, being worked on (flat folder, category in frontmatter)
        ↓
    production      — structure, write, edit, image, links (collaborative)
        ↓
    scheduling      — compose the blog storyline (autonomous). Draft deleted.
        ↓
published/          — date-prefixed, pushed to Blogger

Labels

Three dimensions: series, category, persona. Not every post has all three. Max 3 labels. New values can be added as the project evolves.

Conscious thought handling

Submissions are conscious thoughts — raw material that has surfaced. Before becoming a draft, each submission goes through active thinking work:

  1. Analysis — read the submission, understand what’s in it.
  2. Discussion — work through the content. Refine, split, restructure, enrich.
  3. Decision on destination:
    • Splectrum explore — needs research, or postpone for later.
    • Draft — ready for writing (post and/or reference library update).
    • Rejected — deleted. Git has the archive.

Submissions stay in submissions/ during this process. Their frontmatter tracks status. A submission may be split into multiple submissions, restructured, or absorbed into another. The thinking is the work — this is not triage, it is the intellectual processing layer.

In future this may move to its own repo. For now it lives within the public conscious persona.

Submission frontmatter

---
title: Submission title
type: post-topic | series | substantial
status: new | in-progress | research | draft-ready
destinations: seed, positioning, language, reality, engineering
---

Lifecycle

  1. Submission — raw material in submissions/. Committed to git on arrival (checkpoint).
  2. Conscious thought handling — analyse, discuss, decide destination. Submission updated in place.
  3. Draft — production — accepted material moved to drafts/. The draft is a collaborative workspace. Production moves through: scope (what the draft produces), storyline (structure in points), narrative (flowing text), editing, and final production tasks (image, links). Human writes the narrative, AI proposes and improves.
  4. Review ready — reviewed, cleaned, ready for scheduling.
  5. Scheduled — the draft produces its outputs: post to published/, reference pages to docs/, vocabulary updates. Draft deleted. Pushed to Blogger.

Source of truth

Each stage deletes on transition — git history is the archive.

To update a live post: edit in published/, push to Blogger.

The draft file serves as the workspace during production — containing notes, post prose, page content, tasks, diagram code. On scheduling, it produces: post, reference page(s), vocabulary updates, images. Then it’s done.

Draft frontmatter

---
title: Post title
series: e.g. language, positioning
category: e.g. philosophy, science, engineering
persona: e.g. Splectrum, comment, thought
status: storyline | draft | review-ready
---

Labels use three dimensions — series, category, persona — aligned with the blog label system. Not every draft has all three. New values can be added as the project evolves.

Scheduling strategy

Baseline

At least one core post per month. That’s the only rigid requirement.

Horizon

Scheduling horizon expands with productivity:

Preferred dates

Composition

Strategic reserve

Core posts are the reserve. When material is plentiful, hold core posts back rather than scheduling immediately. This guarantees the minimum rhythm (1 core/month) even if other sources slow down. Aim: 6-12 months of core posts available in the pipeline at steady state.

Content structure

The persona publishes through three channels:

Posts are moments. Reference pages are where the thinking accumulates. Anchor pages are the navigation between them.

Each post publication may trigger: anchor page update (synopsis when scheduled, full text with links when live), reference page creation or update, search engine indexing.

Scheduling checklist

  1. Render any Mermaid diagrams to images → published/images/ (named with post date prefix)
  2. Upload images to hosting, get URLs
  3. Create clean post file (prose + image refs only, no notes) → published/ with date prefix
  4. Create reference page(s) if any → docs/ with versioned folder structure
  5. Update anchor page(s) on Blogger if needed
  6. Schedule post on Blogger (from published file, not draft)
  7. Add image references to post and page with hosted URLs
  8. Delete draft from drafts/
  9. Flag tasks from draft in scheduled tasks file
  10. Commit and push
  11. Verify: test all image URLs are accessible, check post and page(s) render correctly on Blogger

Automation roadmap

Role Current Target
Submission Manual Mycelium — seamless cross-repo referencing
Conscious thought Collaborative Collaborative — thinking is the work
Production Collaborative Stays collaborative — we think and write together
Scheduling Collaborative Autonomous AI

(This page grows as the persona evolves.)

© 2026 In Wonder - The World of Splectrum, Jules ten Bos. The conversation lives at In Wonder - The Conversation.