005 - AoP Definitions and Scaffolding

Created: 16/9/2026 10:38:22
Link: https://chatgpt.com/c/6aaa2446-0d90-83ee-a588-9b86149f01a2

1. It starts before the event

This is probably the most important feature of your AoP.

The project is announced, but the announcement is not the project.

The people involved-the “pillars” and potential “players”-can see the work that is already happening. Your June material specifically describes making the pillars' body of work available, including their daily work and AI brainstorming/chat logs. (Joyful Earth)

So someone interested in the project can progressively become informed:

Read → think → respond → contribute → collaborate

They don't have to wait until the conference/workshop date.

This also fits very strongly with how you describe your own use of AI: you speak with Gemini extensively, refine ideas, and publish the conversations rather than treating the AI work as a private black box. Your homepage explicitly describes this practice. (Joyful Earth)

2. Everyone can become a contributor

An AoP isn't built around a rigid distinction between:

• expert
• speaker
• attendee
• audience

Instead, somebody can arrive as a player and gradually become a pillar.

That's an important part of the philosophy.

You wrote that every attendee/player is free to put their own thoughts into the public domain and can “slowly gear up to becoming pillars in their own right.” (Joyful Earth)

So the AoP is also an onboarding mechanism for future leadership.

Someone doesn't have to be appointed a leader first. They demonstrate useful work, take responsibility, collaborate, and eventually have enough understanding to lead their own project.

3. The planning happens asynchronously

This is another major difference from an ordinary conference.

Your June model proposes structured email as one of the coordination mechanisms, with experienced people converting incoming contributions into a visible weekly digest and task list. Groups can form around tasks and work together before the physical/virtual gathering. (Joyful Earth)

So you have something like:

PUBLIC PROJECT MATERIAL
        ↓
People study it
        ↓
People respond / contribute
        ↓
Structured email
        ↓
Senior/editorial triage
        ↓
Weekly digest
        ↓
Tasks / groups
        ↓
LIVE AoP GATHERING

The event therefore isn't where thinking starts.

It is where distributed thinking gets compressed into coordinated action.

4. The actual event is a midway acceleration point

This is perhaps the best single definition I found in your material.

You describe the actual gathering as a “midway project acceleration get together.” Its purpose is primarily:

• review
• brainstorming
• resolving questions
• making decisions
• taking collective action

And if the gathering is surrounded by virtual preparation/follow-up, you envisage the project moving extremely quickly. (Joyful Earth)

So instead of:

Day 1 → lectures
Day 2 → workshops
Day 3 → closing ceremony

you have:

Weeks of preparation → acceleration meeting → weeks/months of execution

The meeting is almost like the sprint-planning/acceleration chamber inside a larger project.

5. The outputs matter more than attendance

This is where the word “action” becomes meaningful.

An AoP should leave behind things that did not exist before it:

• research
• documents
• prototypes
• decisions
• tasks
• collaborations
• public resources
• campaigns
• completed work
• new projects

Your June discussion repeatedly comes back to tracking people's work and making the resulting body of work visible. (Joyful Earth)

That means the fundamental question isn't:

“How many people attended?”

It is closer to:

“What moved because these people came together?”

That's a very different event metric.

6. The project continues after the event

This is crucial.

The AoP doesn't end with:

“Thank you for attending.”

The work continues.

And this is where your broader DAWN / Internet of Missions concept comes in. Your homepage describes Action-Oriented Projects as the culmination of accelerated social causes, within the larger idea of an Internet of Missions. (Joyful Earth)

The project becomes a persistent public record of:

what we are trying to accomplish → what people are doing → what has happened → what remains → who is taking responsibility.

7. It is deliberately different from a workshop

I think this distinction is worth making explicit.

Your June AI discussion explicitly frames the AoP against the one-way/panel-discussion model and against workshops where the activity can remain bounded within the event. (Joyful Earth)

8. AI has a special role in the AoP

This is another thing that becomes apparent from scanning the 2026 archive.

AI isn't necessarily the project.

It is more like the thinking accelerator and publishing companion.

Your proposed first step for launching a mission is:

articulate the vision using AI to have detailed brainstorming/idea-showcasing conversations and publish them as part of the digital footprint. (Joyful Earth)

That creates an interesting loop:

Human has an idea → AI interrogates it → human refines it → conversation becomes public → others respond → project emerges → people act.

And because the conversation itself can be published, somebody encountering the project later can see how the thinking evolved, rather than only seeing the polished final answer.

That is very consistent with the architecture you describe on your homepage: your “With AI” material is effectively part of your working/public record. (Joyful Earth)

9. The AoP is also a replication mechanism

This may actually be the most ambitious part of the idea.

The purpose isn't simply to complete Project A.

It is to teach people how to create Project B.

Your June discussion explicitly puts “Replication via action oriented projects” as the fifth step after vision, engagement, operations and funding. (Joyful Earth)

So imagine:

                         ORIGINAL MISSION
                               │
                               ▼
                         ACTION-ORIENTED
                            PROJECT
                               │
             ┌─────────────────┼─────────────────┐
             ▼                 ▼                 ▼
          Player A          Player B          Player C
             │                 │                 │
             ▼                 ▼                 ▼
        takes ownership   takes ownership   takes ownership
             │                 │                 │
             ▼                 ▼                 ▼
          new project       new project       new project

The successful participant isn't supposed to remain permanently an attendee.

They learn enough DNA to initiate another mission.

That is why the AoP is connected to your larger DAWN idea rather than being merely a better conference format.

10. And the website becomes part of the project itself

This is particularly interesting in your case.

Your homepage says that you want people to own their content and operate relatively simple, file-based web ecosystems rather than becoming dependent on platforms and developers. (Joyful Earth)

The AoP therefore has a natural digital form:

The website isn't merely advertising the event.

It becomes the project's public working notebook.

It can contain:

• mission statement
• pillars
• current questions
• AI conversations
• research
• daily logs
• participant contributions
• weekly digests
• tasks
• links to people's own work
• decisions
• progress
• eventual outcomes

That makes the website a kind of living project dossier.

Your existing AO Projects page currently lists categories such as Coalitions, Imaginative Communities, Intimate Gatherings, Pact and The Emerging Hero, although the page itself currently says “[INFO TO FOLLOW].” (Joyful Earth)

My distilled definition

If I had to explain your concept to somebody in one paragraph, I would say:

An Action-Oriented Project is a continuously developing social project whose participants publicly prepare, think, contribute and organize before a physical or virtual gathering; the gathering serves as a midway acceleration point for reviewing work, solving problems, brainstorming and making collective decisions; and the work continues afterwards through visible tasks, outputs and collaboration. Unlike a conventional event, the event is not the product-the ongoing project and the work it produces are the product. Participants can progress from players to pillars and eventually replicate the model by initiating their own projects.

And an even shorter version:

An AoP is an event embedded inside a project, rather than a project embedded inside an event.

I think that last sentence is the conceptual heart of what you've been developing.

There is also a strong continuity with your earlier DAWN material: already in December 2025 the site was describing DAWN in terms of decentralized, autonomous groups and “action-oriented projects,” while the 2026 material makes the operational mechanics much more concrete. (Joyful Earth)

So I wouldn't describe AoP as simply “a better workshop.” I'd describe it as a new event paradigm for accelerating an already-public, already-moving project.

I can also create an image showing the AoP lifecycle from AI brainstorming → preparation → acceleration event → action → replication.

Sources:

• 015 — A Full Blown Internet of Missions < 11 to 15 < Jun 2026Imran Ali Namazi

The really interesting next step

I wouldn't try to make this page prettier yet.

I'd make it more alive.

The question becomes:

Can this simple TSV-driven page become the root node of a genuinely autonomous Action-Oriented Project?

I think the answer is yes.

The architecture could evolve something like this:

HUMANITY
│
├── vision/
│   ├── index.html
│   └── vision.tsv
│
├── principles/
│   ├── 01-see-the-unity.md
│   ├── 02-unity-without-sameness.md
│   ├── ...
│   └── 15-aspire-without-ego.md
│
├── ideas/
│   ├── ai-chats/
│   ├── markdown/
│   └── presentations/
│
├── projects/
│   ├── project-001/
│   ├── project-002/
│   └── ...
│
├── people/
│   ├── person-001/
│   └── ...
│
├── action/
│   ├── tasks.tsv
│   ├── teams.tsv
│   └── progress.tsv
│
├── evidence/
│   ├── metrics.tsv
│   ├── stories/
│   └── reports/
│
├── communications/
│   ├── structured-emails/
│   └── invitations/
│
└── replication/
    ├── how-to.md
    ├── templates/
    └── new-aops/

And none of this needs to become a giant application.

That's the beauty of what you're demonstrating.

The 15 principles become the AoP's DNA

This is where I think our next conversation should go.

Rather than treating the 15 principles as a list at the bottom of the page, we can make them structural attributes of the project.

For example:

1 See the Unity

Mission question:
What connects humanity rather than divides it?

2 Seek Unity without Sameness

Project test:
Does this project preserve meaningful diversity?

3 Use Religion as a Bridge

Participation test:
Can people of different faiths participate without having to surrender their identity?

4 Love the Planet

Impact test:
What does this do for the living world?

...

12 Build What Works

This one is especially important for AoPs.

The project should be able to answer:

What are we actually building?

14 Own Our Mistakes

This should become an explicit project feedback/evidence mechanism.

15 Aspire Without Ego

And this could become perhaps the ultimate governance principle:

Does the project serve the mission, or has the mission become a vehicle for its founders?

Your live page already states these principles very crisply. (AmadeusWeb)

And then the AoP becomes self-describing

This is the part I find most exciting.

Imagine someone discovering:

amadeusweb.in/aop/humanity/

They don't just find an event.

They find a machine-readable and human-readable mission node.

They can navigate:

Vision → Principles → Ideas → People → Projects → Actions → Evidence → Replication

And every one of those can be composed from simple files.

A visitor could then ask:

What's happening?

Who is working on it?

What has actually been done?

What evidence do we have?

What can I contribute?

What project could I start?

How does this relate to the 15 principles?

That is when the AoP stops being an infographic and starts becoming an operating system for a mission.

And this is where AmadeusWeb becomes much more than the technology

The current page is already an excellent little proof-of-concept.

TSV → HTML → human-readable mission node

The next experiment could be:

TSV + Markdown + AI chat + Reveal.js + PHP + structured email + HTML → complete autonomous AoP node

And then the really radical question:

Can another person copy the entire AoP folder, change a handful of TSV/Markdown files, and have their own functioning mission/project node?

If yes, we have something much more significant than an event website.

We have the beginnings of a replicable protocol for an Internet of Missions.

And I think that should be our next dive: take this exact Humanity AoP and map every part of it against the 15 principles, then design the minimal file structure that makes each principle actionable rather than merely declarative.

Sources:

• Vision < Humanity < AO ProjectsAmadeusWeb

Sources:

• Vision < Humanity < AO ProjectsAmadeusWeb

Principle files

file created: PRINCIPLES PROMPT

For example:

## The Proposition

Humanity can become kinder, fairer and more sustainable
through thousands of locally actionable projects.

## Why It Matters

Large global problems can feel too distant for individuals
to influence directly.

## Questions

### Q1 — Is local action sufficient?

### Q2 — What should be coordinated globally?

### Q3 — How do we know whether an action is working?

Now Q1, Q2, Q3 become conversation handles.

Someone could reply:

vision/mission.md#q2

That is enormously powerful for your structured-email idea.

I would therefore introduce IDs

Not necessarily ugly UUIDs. Simple human-readable IDs.

## The Proposition {#proposition}

## Why It Matters {#why-it-matters}

## Questions {#questions}

### Is local action sufficient? {#q1}

### What should be coordinated globally? {#q2}

### How do we know whether it works? {#q3}

Then an email could effectively say:

RE: Humanity AoP
FILE: vision/mission.md
POINT: q2

I think global coordination is necessary when...

And the reply can be attached to that exact point.

That begins to turn Markdown + structured email + hyperlinks + AI conversations into a very lightweight discussion protocol.

The bigger idea

This means your files aren't really:

documents

They're more like:

addressable conversations about a mission.

And that fits beautifully with the AmadeusWeb philosophy.

A Markdown file can simultaneously be:

document + web page + email + discussion thread + AI prompt + project record.

That's potentially much more interesting than simply creating a collection of Markdown pages.

For the Humanity AoP, I'd therefore establish one universal convention:

Every substantive assertion, question, proposal or action should be independently addressable.

That could become one of the design principles of the whole With AI / AoP system.

And I think there's a beautiful consequence here.

The network does not try to capture every utterance.

It captures digested contributions that someone has decided are worth publishing.

So the path is:

conversation → human digestion → published knowledge → network pointer

rather than:

conversation → database → everything forever

That keeps the system human-scaled for as long as possible.

And when eventually the volume becomes too much, that is precisely when AI can help with the digestion, without having to redesign the underlying protocol.

The AI can work on the pile of incoming mail and propose:

“Here is my digest of what these people are saying.”

But a human still decides whether that digest represents the conversation accurately enough to publish.

That distinction feels very important to the philosophy of your Internet of Missions.

Powered by [ChatGPT Exporter](https://www.chatgptexporter.com" rel="nofollow)