Orient
Help a new visitor understand where they are and where they can begin.
Professional work · Documentation
Making complex work easier to enter.
Documentation turns scattered ideas, projects, methods, and decisions into something people can read, understand, question, and continue.
Status: Active · Maintained · Public
The purpose
A project should not require a treasure map.
When a body of work grows across repositories, conversations, experiments, and unfinished ideas, it becomes difficult for new people to understand where to begin.
Documentation creates an entry point. It explains vocabulary, shows how projects relate, describes current status, and makes complex ideas easier to approach without removing their depth.
01
Onboarding
Give people a way in.
New visitors should not need to open every repository and guess how the pieces connect.
Onboarding material provides a recommended starting point and a readable explanation of the larger ecosystem. It can guide a person or a browsing-capable AI through the public work.
Recommended path
Organisation README → Onboarding guide → Project map → Project status → Relevant documentation
02
Project maps
Show how the pieces relate.
A project map helps distinguish between technical systems, conceptual work, experiments, documentation, archives, and related areas.
It does not force everything into one architecture. Its job is to show relationships supported by the available work and documentation.
03
Shared language
Definitions prevent ideas from drifting.
Projects often develop their own vocabulary. Terms such as continuity, workstate, symbiosis, authority, context, and governance can mean different things in different settings.
A glossary helps keep important concepts understandable and makes it easier to identify when ideas are related, different, or uncertain.
04
Status
Ideas and implementations are not the same.
Good documentation should say whether something is active, experimental, conceptual, proposed, maintained, archived, or unfinished.
This prevents a concept from being mistaken for a working product and makes it easier to understand what can currently be used, tested, or only discussed.
05
Public communication
Make the work readable without making it shallow.
Documentation is not only technical reference material. It can also bridge complex internal thinking and people encountering the ideas for the first time.
The challenge is to make the work clear enough to enter while keeping uncertainty, limitations, and unfinished parts visible.
Documentation principles
What useful documentation should do.
Distinguish
Separate facts, concepts, proposals, experiments, and completed implementations.
Connect
Show useful relationships without inventing connections that have not been established.
Preserve context
Keep enough background for future readers to understand why the work developed in a particular direction.
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.