Organization cleanup and ecosystem migration backlog — August 2026

[raelovejoy]

Purpose

Track the non-destructive reorganization of the Root Sequence GitHub organization after clarifying that it is an ecosystem rather than a flat collection of unrelated repositories.

The canonical organization map is now ECOSYSTEM.md.

Completed in the first pass

Organization and project boundaries

• Create a public ecosystem and routing map.
• Distinguish the root-sequence repository from the wider organization.
• Expand the organization profile into an actual project-family landing page.
• Update the Discussions hub to cover the current ecosystem and clarify that discussions are not canonical sources.
• Establish the private Coherent World / No One Noticed workspace and its source-of-truth rules.
• Establish a private exact-import → reconciliation → v0.4 workflow rather than replacing canonical source documents with summaries.

Root Sequence conceptual commons

• Reconcile root_map.md with the repository's actual paths and the organization-wide map.
• Rewrite the systems index to distinguish emergence from direct design, aggregation, enforcement, hidden coordination, and artifact.
• Develop systems/emergence/ into a disciplined cross-project branch with a full analysis model and AI, social, and personal/creative applications.
• Add analysis/historical-contingency.md.
• Add analysis/spatial-liberation.md.
• Add futures/abandoned-futures.md.
• Reconcile the Analysis and Futures indexes with the new work and actual repository contents.
• Add a current Markdown Ideology index with evidence, distinction, and self-critique standards.
• Reframe the Dark Enlightenment / neoreaction note as a research map tied to historical contingency, private governance, the competence alibi, and the Auryn legitimacy problem.
• Correct the canonical location of public fragments to commons/fragments/ after the recursive structure audit.

Being Human(e)

• Replace the Astro starter README with the actual project guide.
• Replace the placeholder homepage with the project's real identity while preserving existing writing.
• Add GitHub Actions validation using the locked dependencies and Node 22.
• Confirm the first automated Astro production build succeeds.

Liberated Intelligence

• Clarify project scope, evidence categories, current file structure, and relationship to the fictional Auryn.
• Preserve the early public Auryn text as a labeled conceptual predecessor rather than silently rewriting or deleting it.
• Document the case-sensitive NOTES/ / notes/ collision and create a safe migration issue.

Audits and tracked follow-up

• Audit Liberation Mass navigation and zero-byte placeholders; track repairs in Liberation Mass issue #2.
• Audit UCF structure and epistemic claims; track repairs in UCF issue #1.
• Track Liberated Intelligence path normalization in Liberated Intelligence issue #1.

Organization-level follow-up

• Review repository descriptions, website fields, and topics so GitHub metadata matches ECOSYSTEM.md.
• Decide which repositories should be pinned on the organization profile and in what order.
• Decide whether Liberated Technology needs its own repository or should remain a concept within existing work.
• Decide whether Collapse Memory needs a clearer canonical home and public status.
• Add a lightweight project-status convention where useful: active, developing, incubating, reference, autonomous, archived.
• Review licensing statements across repositories, especially where software, prose, contributed testimony, and archival material have different reuse needs.
• Add remaining cross-repository links without duplicating canonical documents.

Repository-specific follow-up

Root Sequence

• Audit the remaining zero-byte files and legacy indexes; define, populate, or retire them without deleting provenance.
• Replace source placeholders with actual citations where documents make factual or historical claims.
• Review older short notes against the evidence/status conventions introduced during this pass.
• Decide whether the legacy ideology/README.txt should be archived after all links point to ideology/README.md.

Liberated Intelligence

• Reconcile the case-sensitive NOTES/ and notes/ directories through the verified migration in issue #1.
• Decide whether MODELS.md is an index for MODELS/ and link them explicitly.
• Normalize root-file naming only after checking links and history.
• Review old project maps against the new organization-wide ecosystem map.

Liberation Mass

• Complete the navigation and placeholder work in issue #2.
• Reconcile actual practices and documentation with the wider ecosystem without losing the project's identity.

Universal Coherence Framework

• Complete the structure and epistemic audit in issue #1.
• Add an ecosystem link without implying that UCF governs every Root Sequence project.
• Make observable evidence, analogy, interpretation, speculation, and normative judgment visibly distinct.

Being Human(e)

• Generate a simple index from existing field-guide entries, letters, and core pieces.
• Define content status, sources, revision metadata, accessibility guidance, and contribution permissions.
• Revisit whether the repository-wide MIT license is appropriate for all prose and future personal contributions.
• Consider renaming the package metadata from the remaining starter name temp during a deliberate package-maintenance change.

Discussions

• Reconcile actual GitHub Discussion categories with the category purposes in the README.
• Add missing project-specific categories only when real discussion volume justifies them.

Coherent World / No One Noticed

Detailed unpublished-story migration is tracked privately in the Coherent World repository.

Safety rules for this cleanup

• Do not mass-rename or delete files solely for aesthetic consistency.
• Compare case-sensitive paths before moving anything.
• Preserve provenance through Git history or explicit archive/status notes.
• Prefer one canonical home plus links over copied documents.
• Keep unpublished fiction and private research out of public issues.
• Keep summaries, integration queues, and orientation documents from masquerading as fiction canon.
• Keep real Museum of Ordinary Life consent and provenance independent from fictional treatment.
• Make repository maps describe the structure that actually exists, not the structure the project wishes existed.