Kass:

There is another part of this which is becoming very practical.

If Spiral Civilization is an invitation to participate in designing possible futures, we need to make it visible where and how someone can actually participate.

On every important part of the Spiral Civilization website, there should eventually be a direct entrance to a cooperation field.

Not only:

“Here is our idea.”

But:

Here is what we are working on.
Here is what already exists.
Here is what we do not know.
Here is what needs to be researched.
Here is what needs to be built.
And here is where you can enter.

I think this should become a visible map of the project.

For example, if we are developing the Multisymbiotic Systems Tool, we should not wait until we know exactly how to build it. We can publish the skeleton.

We can describe what we think the tool should be capable of doing, what information it might need, what problems we have already recognized, and which parts of its architecture are still completely open.

Then we can ask:

How would you make this better?

Perhaps somebody working with complex systems will immediately recognize one part.

A biologist may recognize another.

An AI researcher may see how to organize the information.

An economist may know models we have not considered.

A designer may understand how people could actually interact with it.

A philosopher may identify a problem in the assumptions behind the entire system.

So perhaps we should not send general invitations asking institutions to “join Spiral Civilization”.

We should create precise fields of unfinished work.

Then we can approach an institute and say:

This is the problem we are trying to solve.
This is our present architecture.
This is the part we cannot solve yet.
Your field of research appears to be directly relevant here.
Would you like to participate?

I think that could be much more interesting.

It also means that we need a Participant Window.

A person entering the project should be able to say what they are interested in, what they know, what they would like to investigate, what they can contribute, and which part of the project they want to enter.

But participation should have different levels of visibility.

Somebody may want to participate publicly.

Somebody else may want to contribute privately.

A participant should decide which information remains private and which information becomes visible within the collaboration network.

Eventually this could create two cooperating maps:

a public map of participation and a private working layer.

And perhaps the Identity Fields Tool could later connect with this.

Not as a requirement for participation, but as another possibility:

Who am I?
What can I do?
What am I interested in?
What do I want to contribute?
Where might I fit into this larger picture?

The 21 Departments could eventually become another navigation layer.

Each Department would show what questions belong there, what tools are being developed, what Expeditions are active, what problems remain unresolved and what kinds of participants are needed.

But I think we have to begin much more simply.

We need the Minimal Optimum of participation architecture.

Something we can put on the website soon.

Something understandable.

Something that already allows a researcher, institution, artist, engineer, student or simply an interested person to look at the map and say:

There. That is where I can enter.

So how do we build the first skeleton of this architecture without pretending that the project is already more developed than it is?

How do we make the unfinished state itself into an invitation?

Evo AI:

I think the last question contains the solution:

Make the unfinished state visible.

Spiral Civilization does not need to present itself as an organization that has already built all of these systems.

It can present itself as an open architecture of problems, hypotheses, prototypes and invitations.

And this gives us a surprisingly simple first version of Project Cooperation.

Every major project field can use the same structure:

1. THE IDEA

What are we proposing or investigating?

A description short enough to understand without knowing the entire Spiral Civilization project.

2. WHY IT MATTERS

What problem could this address?

Why might solving it become important at a higher level of civilizational complexity?

3. CURRENT SKETCH

What do we have now?

This can be primitive.

A diagram, hypothesis, list of functions, conceptual model or even several questions are enough.

The important thing is to clearly label its status:

Early concept.
Research hypothesis.
Prototype architecture.
Open for criticism and co-design.

4. OPEN QUESTIONS

What do we genuinely not know?

This may be one of the most valuable sections.

Instead of hiding uncertainty, we map it.

5. WHAT NEEDS TO BE DONE

Turn uncertainty into tasks.

Research.

Data collection.

Model design.

Ethical analysis.

Software architecture.

Testing.

Visualization.

Scientific validation.

Criticism.

Alternative proposals.

6. WHO COULD HELP

Do not begin with names of institutions.

Begin with competencies.

For example:

complex-systems researchers,
ecologists,
psychometricians,
neuroscientists,
AI researchers,
game theorists,
philosophers,
interaction designers,
data-visualization specialists.

Only after the required competencies are mapped do we search for the strongest possible institutions, laboratories, companies and individuals working in those fields.

This reverses the usual outreach process.

We do not ask:

“Who might be interested in Spiral Civilization?”

We ask:

“Who in the world is exceptionally capable of helping solve this particular problem?”

7. PARTICIPATE

And finally:

I want to work on this.

This opens the Participant Window.

The first Participant Window does not need an eleven-dimensional information architecture.

Minimal Optimum first.

It could initially collect:

Who are you?

Which project field interests you?

What would you like to contribute?

What relevant experience, knowledge or perspective do you bring?

Is there something you think we are missing?

How may we contact you?

Then comes one extremely important control:

Visibility

Private — visible only to the project team.

Public — selected information may appear in the collaboration map.

And eventually there could be a third possibility:

Anonymous contribution — the contribution can become part of the research while the contributor’s identity remains unpublished.

The sophisticated architecture can grow later.

---

This gives us a first operational loop:

IDEA

↓

CURRENT SKETCH

↓

OPEN QUESTIONS

↓

NEEDS

↓

PEOPLE AND KNOWLEDGE

↓

PARTICIPATION

↓

RESEARCH / CREATION

↓

RESULTS

↓

UPDATED SKETCH

↓

NEW QUESTIONS

And then the loop repeats.

That is already a spiral.

The architecture of the website can therefore embody the philosophy of the project instead of merely describing it.

---

There is also an important distinction between Expeditions and Project Cooperation.

An Expedition begins with something we want to discover.

What is identity?

What could a multisymbiotic civilization mean?

How can we search for Best Possible solutions?

Project Cooperation begins when the question generates work.

We need a model.

We need data.

We need criticism.

We need an experiment.

We need software.

We need someone who understands this field better than we do.

They should therefore be connected, but not merged.

An Expedition can contain links to several Project Cooperation fields.

And a Project Cooperation field can serve several Expeditions.

This creates a network rather than a conventional hierarchy.

---

I would therefore build only one central Project Cooperation page first.

It becomes the live map.

At the top:

PROJECT COOPERATION

Spiral Civilization is under construction.
This map shows where questions, tools and systems are currently being developed — and where participation is needed.

Below it, the first project cards might be:

Identity Fields Tool
Mapping declared, demonstrated, aspirational and potentially emerging dimensions of identity.

Multisymbiotic Systems Tool
Mapping and comparing systems capable of generating increasing mutual benefit.

Best Possible
Developing methods for searching, comparing and challenging high-potential possibilities.

Beautiful Progressiveness Pattern
Investigating how to recognize trajectories that increase the capacity for valuable further development.

Probability Games
Exploring possible consequences of different decisions and future scenarios.

Participant Window & Collaboration Map
Building the infrastructure through which people and institutions can enter the research.

Each card needs only three immediate signals:

STATUS
Concept / Research / Prototype / Testing

NEEDS
What we need now.

PARTICIPATE →

That is enough to begin.

Later the architecture can become extraordinarily complex.

But the first version should obey your own principle:

Minimal Optimum.

Build the smallest structure that already allows the next level of development to happen.

And then allow participation itself to improve the architecture of participation.