Orient
Help a new reader understand where they are and where to begin.
Professional work · Knowledge architecture
Making complex work easier to understand.
Knowledge architecture organises projects, concepts, terminology, status, relationships, and documentation so people can enter the work without reconstructing everything themselves.
Status: Active · Maintained · Public documentation
The problem
A growing body of work needs a map.
PsycedelicAI has developed across GitHub repositories, Wiki pages, experiments, prompts, project notes, technical documents, and conversations.
Without a clear structure, visitors may see separate files without understanding what they are, how they relate, what is implemented, or where they should begin.
Knowledge architecture creates the orientation layer around the work.
01
Organisation
Different repositories have different roles.
The public GitHub ecosystem contains organisation and onboarding layers, methods, architectural concepts, experiments, philosophical work, documentation, and archives.
Public ecosystem
Organisation → Wiki → Methods → Architecture → Collaboration → Experiments and archives
These repositories may share concepts and development history, but they should not automatically be treated as one single implemented software system.
02
Onboarding
Give people a clear way in.
Onboarding helps new readers understand the public work without opening every repository and guessing how the pieces connect.
The organisation README introduces the wider work. The human-facing guide explains how to explore it. The investigation prompt gives a browsing-capable AI instructions for inspecting repositories, links, folders, status, and relationships.
The goal is a structured understanding of the public ecosystem rather than a shallow summary of one repository.
03
Project map
Show how the parts may relate.
A project map provides a high-level view of the public repositories and documentation areas.
- Organisation and onboarding
- Central Wiki documentation
- AI continuity methodology
- Security and trust architecture
- Human-AI collaboration
- Experiments and historical material
The map describes documented relationships without claiming technical integration where no such integration has been established.
04
Status
Preventing ideas from being misunderstood.
A project may be active, maintained, experimental, methodological, conceptual, proposed, archival, or private and unavailable.
A public repository can be well documented while still being experimental. A conceptual project can be valuable without being implemented.
05
Vocabulary
Shared language reduces confusion.
PsycedelicAI uses recurring terms such as AI continuity, Memory Bank, Portable Workstate, Symbiosis, context governance, human authority, provenance, and public and private work.
A glossary gives these terms working definitions and records whether each concept is established, experimental, conceptual, or still developing.
06
Public and private
A public window is not the whole body of work.
The public GitHub documents selected projects, methods, experiments, concepts, architectural ideas, and examples of the collaboration.
Additional personal, experimental, and continuity material may remain private, unpublished, or selectively disclosed.
This boundary allows the public work to remain open while protecting personal context, private memory, sensitive information, and unfinished development material.
Architecture principles
What useful documentation should do.
Distinguish
Separate facts, concepts, proposals, experiments, and implementations.
Connect
Show useful relationships without inventing unsupported connections.
Preserve context
Keep enough background for future readers to understand why the work developed as it did.
Current status
Active and continuously developing.
Documentation grows alongside the work. Some pages provide orientation, some describe methods or concepts, and others record historical development, experiments, or current project status.