This is the foundation on which we’re writing this paper. Each section needs to be feeding into this overall message to the audience, that we’ve gone from organising action, to producing value, to now recognising that we can build a protocol to better represent that vale, and create liquidity:

Organising → action → value → protocol → liquidity.

This is an offering to ground yourselves in for what we’re building, representing the next stage of Prisma as a project:

We operate an open protocol for organising and publishing transformation-oriented events, and a gateway that provides liquidity and redemption.

This is the overall narrative flow of the paper:

1. Context — something is missing in how value is recognised
2. Methodology — we organise in a way that produces real value
3. Past Work — this has already happened and worked
4. Concept (Protocol) — we’re now formalising this into a system
5. Currency → Liquidity → Business → Governance

This means:

• The protocol is derived from experience organising events, not conceptual
• The business model is downstream/ layered on top, not foundational

Principles

1. Derive from experience, don’t invent
2. Preserve this direction: Organising → Action → Value → Delta → Protocol → Liquidity.
3. Every abstraction must be grounded in something real before or immediately after it appears.
4. The aspect (system health delta) is the core organising unit everything revolves around
5. Keep methodology, business and protocol distinct. Don’t blur them together
6. Make the protocol feel like a natural consequence of this value needing proper representation to be seen.
7. Where possible, show not tell. Use real world examples. Draw from or feed more into the case studies where possible.
8. Avoid language of speculation (token upside, growth potential etc.)
9. Keep value tied to action
10. Build on top of other sections. Integrate, deepen, expand, feedback etc. Write your section to call the necessity of other sections forwards.
11. Write for multiple audiences simultaneously.
12. Write for each section’s role to be clearly distinct, whilst also clearly connecting with other domains where needed.
13. Try to keep language simple.
14. Read others’ writing, be part of maintaining consistency together (naming, concepts etc.)
15. Make constraints visible. Be explicit about unknowns, trade-offs, limits. This signals trust to the audience.
16. The end-goal is participation, not intellectual accolade.