SGP 40 day plan

paulransfield · May 8, 2026, 8:44pm

SGP 40-Day Plan — Post 1 of 4: Thesis, Offer, Proof

Reader note: This is the first part of the public proof trail. It establishes #iuwe as community-owned digital language infrastructure, introduces the Community Care Key offer, brings the pirate-radio / Radio Hauraki metaphor back into the foreground, and explains why the 6-million QR inventory, magic-number layer, 1,000-key bundle, and 12 pluriverse rails make the offer operational rather than speculative.

SGP 40-Day Singapore Investor Pathway

Author: Paul Ransfield, Kapai Group / #iuwe
Date: 9 May 2026
Publication note: I am publishing this as a first-person operating plan. It is the plan without the spoken narrative, yet it holds the narrative in text: I am demonstrating the teaching and learning model while leading the investor conversation about operationalising whanau.tv.

Executive Summary

I am using this 40-day Singapore pathway to position #iuwe as community-owned digital language infrastructure, not as a startup, donation vehicle, or conventional education product. The investment proposition is a practical pre-purchase of Community Care Keys: live QR-code access endpoints such as https://iuwe.whanau.tv/WH-RD-C000000001, each enabling a community member to access an already operational platform. The simplest pitch line is: this is like buying a Pokémon-style booster box for access to an entire community: and from NZ$2.50/year each card is a unique, scannable, giftable, tradeable Community Care Key that unlocks one year of 24/7 access to whānau-friendly rich-media nano-learning events.

The campaign is designed for “Singaporean-type” investors: disciplined, infrastructure-literate, regionally networked, governance-conscious, and interested in the gap between Big Tech extraction and state-controlled digital systems. The proof position is now stronger than a promise: iuwe.whanau.tv already has a 6-million-QR mockup inventory across 20 colours, including visible states such as not sold, magic, and sold. An endpoint such as https://iuwe.whanau.tv/WH-RD-C000010001 can readily move from mockup to live by assigning an owner to the QR. The magic layer is also not an afterthought: the mathematics-of-mana work ring-fences 40,277 magic numbers per icosahedron face, including rare palindromic and milestone endpoints, so a 1,000-key bundle can carry normal access, visible magic, and collector-grade community meaning inside one practical procurement unit.11 Singapore is a strong narrative fit because its public strategy explicitly frames AI as being for “the Public Good, for Singapore and the World,” while its digital infrastructure policy describes digital infrastructure as an “invisible foundation” for digital society and economic participation.2 3 I am therefore avoiding a Silicon Valley tone and speaking instead in the language of operational proof, trusted access, soft infrastructure, cultural resilience, and collective advantage.

Campaign thesis: If Singapore can understand ports, trusted digital utility stacks, and public-good AI, it can also understand that language sovereignty needs access infrastructure. #iuwe is not asking investors to fund an idea. I am asking investors to pre-purchase access to something already live, so communities can use what has already been built.

I am building the 40-day pathway around four linked outputs. First, it creates a public proof trail through LinkedIn and short video messages, beginning with COUNTER ON and then unfolding the three-model argument: Big Tech extraction, China state control, and community ownership. Second, it uses a postcard and direct outreach sequence to move selected contacts from curiosity into a scheduled conversation. Third, it develops a Singapore pitch deck that makes the ask concrete: bulk packs of Community Care Keys, anchored at NZ$3 per person per year for the public koha-to-key pathway and presented as from NZ$2.50 per person per year for bulk access-key procurement, with 1,000-key bundles as the clean first procurement unit. Fourth, it activates the operating rail behind the promise: i mahi pai content refresh + Koha Gateway redirect + Stripe webhook → QR owner assignment → QR delivery → iho.whanau.tv counter increment.

I am deliberately breaking the fourth wall. I will not only describe the teaching-and-learning model; I will perform it in the video messages while speaking directly to investors about operationalising whanau.tv. Each video will carry two simultaneous signals: the upper layer is the investor conversation about infrastructure, access keys, koha, and operational readiness; the lower layer is the live demonstration of how #iuwe teaches, prompts, repeats, invites practice, and turns observation into participation. I want the viewer to be able to say: “I am watching the pitch, and I am also watching the product work.”

The public-facing metaphor I can now add back in is pirate radio. Across the free world, pirate radio appeared wherever official broadcast systems could not carry the signal people were ready to hear; in Aotearoa New Zealand, Radio Hauraki began as an offshore pirate station broadcasting beyond the three-mile territorial limit in 1966.15 The point is not nostalgia or illegality. The point is transmission. When incumbent channels cannot carry a living cultural signal, a new channel gets built until public demand makes it ordinary. #iuwe is not broadcasting rock music from a boat; I am converting Digital Mount Everest into a 24/7 community spa and broadcast lounge, accessible by the many and not the few, with Māori-made learning infrastructure made for all.

Strategic Positioning

I am framing the campaign as a pre-procurement pathway for community-owned digital infrastructure. I am explicitly refusing the three common misreadings of the offer. It is not equity, because buyers do not acquire ownership in Kapai Group. It is not charity, because buyers purchase access capacity for named or nominated communities. It is not a startup pitch, because the infrastructure is already live: iho.whanau.tv streams continuously, i mahi pai is live on iOS and Android with 1,440 of the intended 14,400 words already present, the Strapi backend is intact, the Koha Gateway is Stripe-enabled, and the Community Care Key mechanism is operational. The QR layer is not a sketch on a whiteboard: #iuwe already has 6 million QR endpoints available across 20 colours, with state logic visible as not sold, magic, and sold. The immediate live step is ownership assignment. The magic numbers have already been ring-fenced, so I can package ordinary access and special-number scarcity inside the same 1,000-key bundle without inventing a new product.

Misreading to Avoid	Correct Frame	Practical Language
“Are you raising equity?”	No. This is not a shareholding or venture investment.	“I am not selling the company. I am inviting pre-purchase of access.”
“Is this a donation?”	No. A buyer purchases keys that unlock platform access for learners.	“Like buying a Pokémon-style booster box for a community: from NZ$2.50/year in bulk, each key can be gifted, traded, scanned, activated, and traced as one year of 24/7 whānau-friendly rich-media learning access.”
“Is the platform still being built?”	No. The immediate ask funds operationalisation of live infrastructure.	“Fund the team to operate what is already built: stream, app, Strapi, koha, and 6 million QR endpoints ready for ownership assignment.”
“Is this crypto?”	No. The unique URL endpoint is the trust foundation; blockchain can be a future state, not the present dependency.	“QR-first, URL-native, SHA-256 hardened, no wallet required.”
“Is this only a language app?”	No. It is cultural, pedagogical, and community-owned digital infrastructure.	“This is maintaining cultural infrastructure.”
“Is whānau only local?”	No. Whānau means family, and family is global.	“Like Subaru, the word can carry its origin and still become globally legible as a brand category.”

Singapore’s official digital infrastructure policy is useful because it distinguishes hard infrastructure, physical-digital infrastructure, and soft infrastructure.3 #iuwe belongs most naturally in the soft-infrastructure category: it is an access, identity, content, learning, and trust layer that lets communities participate in digital society without surrendering cultural agency. Singapore’s National AI Strategy also identifies education among the strategic sectors for AI adoption, and emphasises ethical AI deployment, transparency, fairness, accountability, talent, and ecosystem development.4 This makes Singapore a credible audience for a project that is AI-enabled but community-owned.

The Core Offer

I am keeping the offer intentionally modest, legible, and operational. The buyer purchases a block of Community Care Keys. Each key is a unique access endpoint, drawn from an already prepared 6-million-QR inventory rather than invented one at a time after payment. Keys may be distributed through schools, marae, community organisations, language champions, diaspora networks, or cultural institutions. A buyer receives a simple allocation report and a public or private acknowledgement depending on buyer preference.

Pack	Public Koha / Bulk Procurement Price	Community Meaning	My Use
1 key	NZ$3 public koha	One person, one year of access	Individual koha or proof transaction
100 keys	NZ$300 public koha equivalent	A classroom, club, small whānau cluster, or pilot group	First conversation close
500 keys	NZ$1,500 public koha equivalent	A school, local language group, or small regional cohort	Warm relationship close
1,000 keys	from NZ$2,500 bulk procurement	One year of access for 1,000 learners, with ordinary access and ring-fenced magic-number packaging available	Standard investor ask and clean bundle unit
5,000 keys	from NZ$12,500 bulk procurement	A district, iwi-aligned programme, or diaspora campaign	Anchor buyer ask
10,000 keys	from NZ$25,000 bulk procurement	A national or transnational language-resilience signal	Strategic partner ask

My first ask will normally be for 1,000 keys, because it is large enough to matter and small enough to be approved quickly. I can offer larger packs only after the investor understands that the mechanism is not speculative. My closing sentence is direct: “Would you pre-purchase 1,000 Community Care Keys from NZ$2,500 so 1,000 people can access a year of community-owned reo infrastructure?” I am keeping the public koha pathway anchored at NZ$3 = 1 key = one person, one year of access, because this aligns the Stripe checkout, donor promise, QR-code delivery, and counter-increment story into one clean operating sentence; the investor pathway can say bulk access starts from NZ$2.50 per learner per year without confusing the public koha promise.

Magic Numbers, 1,000-Key Bundles, and the 12 Pluriverse Rails

I can now strengthen the offer because the magic-number layer is already ring-fenced. The mathematics-of-mana frame identifies 40,277 magic numbers per icosahedron face and organises special endpoints by rarity and community meaning.11 I do not need to lead with speculation or collector hype. I can lead with access, then let magic make the access memorable.

A 1,000-key bundle therefore becomes the standard procurement unit. It is operationally simple enough for an investor, school, iwi, diaspora group, or family-office intermediary to understand, and it is rich enough to include visible variety across colours, ordinary access keys, and ring-fenced magic endpoints. This also keeps the Pokémon-style booster-box analogy useful: a buyer knows a box contains many ordinary cards, a few special cards, and one shared reason to gather, trade, gift, and talk.

Bundle Layer	What I Can Package	Why It Matters
Base access	1,000 QR-native Community Care Keys.	One procurement decision opens one year of access for 1,000 learners.
Colour variety	Keys drawn from the 20-colour inventory.	The bundle feels visible, collectable, and easy to explain.
Magic-number inclusion	Ring-fenced special endpoints can be reserved, allocated, or priced with care.	The access model gains scarcity without becoming extractive.
Community governance	Magic value can be linked to fair-trade resale and community return.	Tradeability can strengthen community ownership rather than reward scalping.
Public proof	The counter can show keys assigned, delivered, activated, and moving through states.	The investor sees operationalisation in public.

The wider frame is not only whanau.tv. I already have 12 deployed pluraverse rails. Whānau is the first public family rail, but family is global. The word can behave like Subaru: a Japanese term that carries origin while global brand awareness connects it to cars. In the same way, whānau can carry whakapapa while global audiences learn to recognise it as the family-learning rail within a wider community-owned educational network.12

Pluraverse Rail	Public Role	Strategic Use in This Campaign
`https://iho.whanau.tv`	Family / whānau learning.	Primary Singapore pathway and first Community Care Key rail.
`https://iho.anana.tv`	Global youth.	Youth-facing extension after first proof.
`https://iho.papatuanuku.me`	Indigenous-first learning.	Indigenous and First Nations bridge.
`https://iho.kapai.tv`	STEAM.	Science, technology, engineering, arts, and mathematics pathway.
`https://iho.asilia.tv`	Africa-first learning.	African continent and diaspora pathway.
`https://iho.ayni.tv`	Americas-first / reciprocity.	Latin and Indigenous Americas bridge.
`https://iho.freelearn.tv`	English-language and lifelong learning.	General access rail for global learners.
`https://iho.xueyong.io`	Mandarin diaspora.	Strategic discount and partner leverage rail for Chinese-language networks.
`https://iho.shkola.tv`	Slavic diaspora.	Slavic-language community pathway.
`https://iho.madrasa.tv`	Arabic-speaking diaspora.	Arabic and Muslim community learning pathway.
`https://iho.gratisaprender.tv`	Spanish diaspora.	Spanish-language community pathway.
`https://iho.freelearn.tv`	Lifelong learners.	Broad lifelong-learning access frame.

This lets me be commercially flexible without weakening the thesis. I can heavily discount one rail, such as xueyong.io, if a strategic partner can turn distribution into proof. The discount is not desperation; it is a deployment tactic. The long-term asset is the community-owned access network, the public counter, the ring-fenced magic layer, and the ability to show 24/7 31/365 rich-media educational delivery in play.

Continue to Post 2: The offer becomes meaningful through the operating rail. Post 2 shows how I reconnect i mahi pai, Strapi, Koha Gateway, Stripe, and QR owner assignment into one practical access loop.

References for This Post

paulransfield · May 8, 2026, 8:45pm

SGP 40-Day Plan — Post 2 of 4: Operationalisation Rail

Reader note: This second part turns the thesis into work. It focuses on i mahi pai activation, Strapi content refresh, Hussain’s bounded developer brief, Koha Gateway redirect, Stripe metadata, and QR owner assignment.

Workstream 3: Activate i mahi pai and Redirect the Koha Gateway

I am now adding a third operational workstream alongside content-market development and investor outreach: activate i mahi pai with refreshed content and redirect the Koha Gateway into the Community Care Key purchase pathway. This strengthens the investor story because it shows that #iuwe is not merely broadcasting content or selling abstract keys; it is reconnecting a live mobile app, a live Strapi content backend, a live Stripe-enabled koha pathway, and a live QR-key trust model into one operational access loop.

The practical position is simple. The i mahi pai app is already live on iOS and Android, but has been in hibernation for approximately eighteen months. It currently holds 1,440 of the intended 14,400 words, and the Strapi backend at https://walrus-app-o9tya.ondigitalocean.app remains intact and accessible. Hussain Mustafa, who helped build the mobile apps that form part of the iuwe technical foundation, is available to assist when given a clear and bounded brief.9 I am not treating activation as a blank rebuild. This is a structured re-opening of existing infrastructure.

Component	Current State	Required Change	Strategic Meaning
i mahi pai app	Live on iOS and Android, but effectively dormant for eighteen months.	Refresh content, confirm authentication, test embedded koha flow, and prepare release notes.	Converts the investor pitch from “platform exists” into “mobile access pathway is being reactivated.”
Strapi backend	Hosted on DigitalOcean at `walrus-app-o9tya.ondigitalocean.app`; intact and accessible.	Audit published content, missing content, schema health, media links, and bulk upload readiness.	Provides the operating spine for the 14,400-word coverage target.
Current content coverage	1,440 words are in-app out of the intended 14,400 words.	Design and execute a staged path to full 14,400-word coverage.	Shows a concrete tenfold content completion pathway.
New ako category	Not yet created.	Create a CardSet category called ako with 60 CardSets, named `01_01` through `01_60`.	Directly maps the app to the 60×1-minute video curriculum.
Koha Gateway	Stripe-enabled at `https://koha.kapaigroup.net/` and embedded inside the app.	Redirect koha destination from 800 marae to whanau.tv operationalisation.	Makes koha the operational funding rail for Community Care Keys.

i mahi pai Content Refresh Plan

I am treating the content refresh as a content-operations sprint rather than a software-development project. My first task is to audit the Strapi instance and produce a reliable inventory. My second task is to prepare the missing content in bulk-upload format. My third task is to create the ako category, because the 60×1-minute video curriculum gives the app a visible, investor-friendly structure.

Step	Output	Lead	Notes
1	Strapi content audit	I, with Hussain only if access or schema questions arise.	Export or inspect current CardSets, Cards, categories, published states, media links, slugs, and timestamps.
2	Gap map from 1,440 to 14,400 words	I handle this.	Identify what is present, what is absent, what is stale, and what needs naming or taxonomy repair.
3	Bulk upload template confirmation	Hussain	Confirm the exact CSV/JSON structure, field names, media handling, and safe import method Hussain previously configured.
4	Ako category creation	I handle this if Strapi permissions allow; Hussain assists if schema or admin permissions block it.	Create category `ako` meaning “teach to learn.”
5	60 ako CardSets	I handle this.	Create CardSets `01_01` through `01_60`, mapped to the 60×1-minute curriculum.
6	8 anchor/companion words per slot	I handle this.	Each CardSet contains the eight anchor/companion words for that video slot. This creates 480 tightly mapped words for the first ako layer.
7	Full 14,400-word upload	I prepare the files; Hussain confirms upload safety.	Run in batches, validate counts after each batch, and keep rollback exports.
8	Mobile app smoke test	Hussain and I	Confirm app fetches refreshed content, categories render correctly, and koha section opens the redirected pathway.

I will name the ako category plainly in the backend and consistently in public explanation. My structure is Category: ako; CardSet: 01_01 through 01_60; each CardSet will include eight words corresponding to that minute of the 60-minute curriculum. This does not replace the 14,400-word goal; it creates a first visible curriculum-aligned layer inside the app while the wider library is refreshed.

Ako CardSet Pattern	Curriculum Mapping	CardSet Contents	Validation Rule
`01_01`	Video slot 1	8 anchor/companion words	Exactly 8 active cards, all published.
`01_02`	Video slot 2	8 anchor/companion words	Exactly 8 active cards, all published.
`...`	`...`	`...`	`...`
`01_60`	Video slot 60	8 anchor/companion words	Exactly 8 active cards, all published.

Hussain Brief: What Requires Developer Help

I will keep Hussain’s brief deliberately narrow. The purpose is to avoid pulling Hussain into open-ended product strategy when what is needed is technical reactivation and confirmation. Hussain’s work will focus on authentication, bulk upload safety, schema confirmation, app-koha behaviour, and release-risk reduction.

Task	Requires Hussain?	Reason	Requested Output from Hussain
Firebase Auth fix or confirmation	Yes	If authentication has drifted during hibernation, I will not debug production auth alone.	Confirm sign-in/sign-up state; fix configuration if broken; document any credentials or console actions I must maintain.
Bulk upload process confirmation	Yes	Hussain configured the pathway and can prevent schema damage or duplicate-content errors.	Provide the exact import template, endpoint/process, required fields, and rollback method.
Strapi schema review	Probably yes	Needed if new category or CardSet relationships are unclear.	Confirm content types, relationships, required fields, publication state, and media field handling.
App build/deployment	Yes, if store update is needed	App Store / Play Store updates may require build-signing knowledge.	Confirm whether a content-only refresh is enough or whether a new build is required.
Embedded koha redirect test	Yes, if app uses hardcoded URLs	If the app points to a fixed koha endpoint or internal webview path, I may need Hussain to update code.	Confirm whether redirect can be handled server-side or whether app code must change.
Content writing and mapping	No	This is curriculum and operations work.	I prepare content and mapping files.
Strapi content publishing	No, unless permissions block me	I can perform normal CMS operations directly.	I publish after export/backup discipline is in place.

Message I will send to Hussain:

Hussain, I am reactivating i mahi pai as part of the #iuwe Singapore pathway. The app is live but has been dormant for eighteen months. The Strapi backend at walrus-app-o9tya.ondigitalocean.app is intact. I need a bounded technical check rather than a full rebuild: confirm Firebase Auth, confirm the bulk upload process you configured, confirm the CardSet/category schema, and confirm whether the embedded koha section can be redirected server-side or needs an app update. I will handle content mapping and Strapi publishing once the safe pathway is confirmed. The first new content task is an ako category with 60 CardSets named 01_01 to 01_60, each containing eight anchor/companion words mapped to the 60×1-minute curriculum.

Koha Gateway Redirect

I am repositioning the Koha Gateway from a marae-search donation interface into a direct operationalisation pathway for whanau.tv. The existing ī-ahikā page searches by iwi and routes koha toward approximately 800 marae; the make koha button is already the Stripe entry point. I want the revised destination to be clearer and more immediate: koha funds the team to operationalise what is already built, and the donor receives Community Care Keys in return.

The landing page will not sound like charity copy. I want it to sound like a practical access purchase with koha language retained. The promise will be visible above the fold:

Your koha funds the team. In return, you receive a Community Care Key: a QR code giving one person one year of access to iuwe.whanau.tv. NZ$3 per key. Bulk packs available.

My landing page structure:

Section	Copy Direction	Draft Copy
Hero headline	Make the redirect explicit.	Fund the team. Open the door for a learner.
Hero subheadline	Tie koha to access keys.	Your koha helps operationalise the #iuwe infrastructure already built across `iho.whanau.tv`, `iuwe.whanau.tv`, and i mahi pai. For every NZ$3, one prepared Community Care Key is assigned to one person for one year.
Proof block	Show the system is live.	The stream is live. The app exists. The key pathway is operational. The QR inventory already contains 6 million prepared endpoints across 20 colours, with states such as not sold, magic, and sold. Your koha now helps the team connect the pieces, assign owners, refresh the content, support learners, and report the access assigned.
Key promise	Keep the transaction simple.	NZ$3 = 1 Community Care Key = one person, one year of access. Each key is delivered as a unique URL and QR code; for example, `https://iuwe.whanau.tv/WH-RD-C000010001` can move from mockup to live when an owner is assigned.
Bulk packs	Give procurement options.	100 keys = NZ$300. 1,000 keys = NZ$3,000. 5,000 keys = NZ$15,000. Larger packs can be allocated to schools, whānau clusters, marae, iwi, diaspora groups, or community partners.
Button	Use action language.	Make koha / assign keys
Allocation note	Avoid donor control over community.	You may keep your key, gift keys directly, or ask the #iuwe team to allocate keys where need is greatest.
Transparency note	Explain reporting.	After koha, you receive confirmation of keys assigned. Bulk buyers can receive a simple allocation report showing keys assigned, delivered, activated, and included in the public counter.

Stripe Webhook and QR Owner-Assignment Flow

The revised Koha Gateway will map Stripe payment completion into Community Care Key owner assignment. The key format for this campaign uses the operationally simple pattern https://iuwe.whanau.tv/WH-RD-C000000001, including live-ready examples such as https://iuwe.whanau.tv/WH-RD-C000010001, while preserving the operating-guide principle that the URL endpoint is the trust foundation and that SHA-256 hashing can provide tamper-evident uniqueness without requiring blockchain infrastructure.10

Flow Step	System Event	Technical Action	User-Facing Result
1	Donor selects koha amount or key pack.	Stripe Checkout receives amount and metadata, including intended key count, donor email, allocation preference, and campaign code.	Donor sees clear equivalence: NZ$3 per key.
2	Stripe payment succeeds.	Stripe sends `checkout.session.completed` or equivalent payment-success webhook to the Koha Gateway backend.	Donor receives payment confirmation.
3	Backend calculates key count.	`key_count = floor(net_or_gross_amount / 3)` depending on accounting decision; bulk products can set key count directly.	Donor knows how many keys will be assigned.
4	Key records are assigned.	Backend assigns ownership to prepared endpoints from the 6-million-QR inventory, such as `WH-RD-C000010001`; each record stores URL, SHA-256 hash, donor/payment ID, colour, status, owner/allocation state, expiry/renewal date, and activation state.	Each key moves from not sold or magic into sold/owned and becomes a live QR-ready access endpoint.
5	QR codes are delivered.	QR assets already exist or can be rendered from the unique URL; the system confirms the assigned endpoint and, where desired, hash/verification metadata.	Donor receives scannable keys.
6	Keys are delivered.	Email sends key list, QR image/PDF, and allocation instructions; bulk packs may include CSV export.	Donor can use, gift, or allocate keys.
7	Counter increments.	`iho.whanau.tv` counter updates by keys assigned, keys delivered, or keys activated, depending on chosen public metric.	Public proof trail grows visibly.
8	i mahi pai koha section uses same destination.	Embedded app koha section redirects to the same updated landing page or hosted checkout flow.	Mobile users encounter the same promise and key pathway.

I will decide the counter rule before launch. My recommended public rule is to increment the counter on key assigned and delivered, while maintaining internal sub-metrics for not sold, magic, sold, activated, allocated, and learning activity started. This keeps the public signal aligned with the funding event while preserving operational truth behind the scenes.

Counter Metric	Visibility	Recommended Use
Keys assigned / sold	Public	Best headline metric for the 40-day campaign because it converts prepared QR inventory into owned access.
Keys delivered	Public or semi-public	Useful where delivery happens immediately after Stripe success.
Keys activated	Internal first, later public	Better for learning analytics; may lag behind purchase.
Learner sessions started	Internal	Educational outcome metric, not a fundraising counter.

40-Day Integration of Workstream 3

This workstream will not wait until the campaign ends. I am integrating it into the same 40-day rhythm so that by the final week a Singapore investor can see a coherent operational pathway: koha assigns prepared keys, keys unlock access, the app content is being refreshed, and the counter shows movement.

Days	i mahi pai Activation	Koha Gateway Redirect	Investor Narrative
1–5	Confirm Strapi access, export current content, and record baseline of 1,440 words.	Confirm current `koha.kapaigroup.net` flow and embedded app route.	“The infrastructure is live and being reactivated.”
6–12	Complete content audit and prepare 14,400-word gap map.	Draft new koha landing copy and confirm Stripe product/key-count logic.	“This is operational proof, not a blank build.”
13–19	Create `ako` category and first test CardSets `01_01` to `01_05`.	Specify webhook, QR ownership-assignment fields, and delivery email.	“The curriculum now maps into mobile access.”
20–26	Confirm Hussain’s Firebase Auth and bulk upload checklist; run safe test upload.	Implement or stage redirect from marae destination to whanau.tv operationalisation project.	“A koha can now become a Community Care Key.”
27–33	Populate all 60 `ako` CardSets and validate each has eight words.	Test Stripe success → QR owner assigned → QR delivered → counter incremented.	“The access purchase loop works end-to-end.”
34–40	Prepare refreshed app release note and content-count report.	Launch updated koha page and app-embedded redirect if technically cleared.	“Singapore buyers can fund keys through an operating pathway.”

Revised Pitch Language

My new language for Singapore conversations is:

The app is live. The backend is intact. The koha rail is live. The key trust model is operational. The QR inventory already holds 6 million prepared endpoints across 20 colours. The ask is not to build from scratch; it is to fund the team to connect and operate what already exists. For every NZ$3, one Community Care Key gives one person one year of access to iuwe.whanau.tv. Bulk packs turn koha into measurable access by assigning owners to prepared QRs.

This addition makes the SGP plan stronger because it gives every investor a concrete operational answer to the question, “What happens after I say yes?” The answer is now precise: the koha moves through Stripe, assigns ownership to prepared Community Care Key endpoints, delivers QR-code access, increments the visible counter, and supports the team refreshing i mahi pai toward full 14,400-word coverage.

Continue to Post 3: The operating rail needs a public rhythm. Post 3 turns the plan into weekly architecture, daily cadence, postcard design, and #iuwe_alchemy social voice.

References for This Post

paulransfield · May 8, 2026, 8:47pm

SGP 40-Day Plan — Post 3 of 4: Campaign Cadence and Public Voice

Reader note: This third part shows the 40-day broadcast rhythm. It sets out the weekly campaign architecture, daily content cadence, postcard design brief, and #iuwe_alchemy social-post voice.

Weekly Campaign Architecture

I am running the 40-day pathway as six linked movements rather than as forty isolated posts. Each week has one strategic job, one proof asset, one conversion action, and one operating action. The pathway begins with the live counter because the counter signals that the system is not theoretical. It then builds the governance argument, demonstrates the one-hour learner outcome, introduces the Community Care Key mechanism, activates the Basque cooperative analogy, and closes with Singapore-ready procurement conversations while the i mahi pai and Koha Gateway rails are being reactivated in parallel.

Days	Movement	Public Narrative	Private Outreach Objective	Operating Action	Main Asset
1–5	COUNTER ON	The infrastructure is live. The counter is visible.	Alert close observers such as Jim Robinson and Ian Grigg that the campaign has begun.	Confirm Strapi access, Koha Gateway route, current content baseline, and QR inventory proof.	Counter zoom-in image or short screen recording.
6–12	Three Models	Big Tech extracts; state systems control; communities can own.	Identify Singapore-aligned investors and intermediaries who understand public-good AI and digital infrastructure.	Complete content audit, draft Koha redirect copy, and confirm Stripe product/key-count logic.	Three-model comparison table.
13–19	One Hour Proof	One hour produces speakable outcomes, not vague exposure.	Send the one-hour outcome post to education, language, and impact contacts.	Create `ako` category and first test CardSets.	`01_36 hour outcome stack` visual.
20–26	Care Keys	The ask is a 1,000-key access bundle, closer to a Pokémon-style booster box than a passive donation: the collectible-card phenomenon is globally legible, and from NZ$2.50/year in bulk, each #iuwe key is unique, giftable, tradeable, scannable, useful, and tied to 24/7 whānau-friendly rich-media learning events. The inventory already exists at scale: 6 million QR endpoints across 20 colours, with ring-fenced magic numbers ready to sit inside practical community bundles.	Move warm contacts into 20-minute calls.	Get Hussain’s Auth/upload confirmation and stage the koha-to-key owner-assignment redirect.	Community Care Key explainer card.
27–33	Basque Frame	Oñati and Mondragón show that community ownership can be resilient infrastructure.	Use Erena/Ian Grigg outreach to open cooperative and governance conversations.	Populate all 60 `ako` CardSets and test Stripe → owner-assigned QR → delivery → counter.	Basque cooperative comparison note.
34–40	Singapore Close	Singapore understands trusted infrastructure. This is a small, clean procurement decision.	Ask for 1,000-key, 5,000-key, or 10,000-key commitments.	Launch or prepare launch of updated koha page and app-embedded redirect.	Singapore pitch deck and postcard.

Daily Content Cadence

Each day includes one visible public action, preferably a short video message supported by a written LinkedIn post, and one private conversion action. I do not expect the LinkedIn post to close the sale alone; it creates a public proof trail that gives private messages legitimacy. The video adds the crucial fourth-wall layer: I am visibly teaching and inviting practice while also leading the investor conversation about how whanau.tv becomes operational. My voice will be precise, warm, and grounded. I will avoid hype and I will use the phrase community-owned digital infrastructure repeatedly enough that the market learns the category.

Day	LinkedIn / Video Message Theme and Draft Copy	Visual or Demonstration Layer	My Private Action	Call to Action
1	COUNTER ON. The counter is now visible on `iho.whanau.tv`. In the video, I will say plainly: “I am going to show you the model while I explain the ask.” This matters because cultural infrastructure must not hide behind pitch decks. I want it live, countable, and open to inspection. #iuwe is not asking anyone to fund a theory. I am asking people to help operationalise what has already been built.	Tight zoom-in of live counter, then I appear on camera demonstrating a simple call-and-response phrase.	Send to Jim Robinson, Ian Grigg, and 5 close observers.	“If you want to understand the access-key model, watch the lesson inside the pitch.”
2	What the counter means. A counter is a small thing until it becomes a public accountability device. Every visible signal says: the stream is live, the platform exists, and the next step is access.	Counter plus URL.	Build list of 40 Singapore-type contacts.	“The question is no longer ‘can it be built?’ but ‘who gets access first?’”
3	Not a startup pitch. #iuwe is not selling equity, not asking for donations, and not promising a future platform. I am offering Community Care Keys: live access endpoints for learners.	Three-part “not this / this” graphic.	Send 10 connection requests.	“Think Pokémon-style booster box, not shares.”
4	The Pokémon booster-box analogy. If you buy 1,000 Community Care Keys, you are not speculating on a company. You are putting 1,000 unique, QR-native access cards into circulation. The global metaphor is instantly legible: collectible cards appear on high streets everywhere. Here, from NZ$2.50/year in bulk, each card can be held, gifted, traded, scanned, activated, counted, and used for 24/7 whānau-friendly rich-media learning events. The difference is that I can point to prepared inventory now: 6 million QRs across 20 colours, not sold / magic / sold states, and ring-fenced magic numbers ready for careful bundle packaging.	QR code mock-up using `WH-RD-C000010001`.	DM first 10 warm contacts.	“Would your community fund a booster box of keys?”
5	One sentence pitch. One year of community-owned reo access can be pre-purchased in bulk: 1,000 learners, one clean allocation, one visible community outcome.	Single-line quote card.	Invite 3 people to 20-minute calls.	“I can show the live pathway.”
6	Three models. Big Tech extracts data. State platforms centralise control. Community ownership keeps the infrastructure answerable to the people using it. #iuwe is the third way.	Three-column table.	Send table to Singapore contacts interested in AI governance.	“Which model will language sovereignty depend on?”
7	Why Singapore can understand this. Singapore describes digital infrastructure as the invisible foundation of digital economy and society.3 Language access is a soft-infrastructure layer of the same kind.	Singapore/infrastructure quote card.	Identify Singapore family office, AVPN, education, and impact intermediaries.	“This is soft infrastructure for cultural participation.”
8	Public-good AI, community-owned rails. Singapore frames AI as being for the public good.2 #iuwe adds a community ownership test: can AI-supported learning strengthen local voices without extracting those voices?	AI/public-good bridge graphic.	Send post to AI governance contacts.	“Public good must include ownership.”
9	The China signal. China’s planning direction makes AI in education and born-global deployment impossible to ignore. The question for communities is not whether digital learning will scale; it is who owns the rails.	Screenshot/quote from @chinabymonica asset.	Prepare personalised messages referencing the TikTok.	“The third way is community-owned.”
10	The Big Tech gap. If the only alternative to state control is platform extraction, communities lose either way. #iuwe offers a third pattern: access keys, community benefit, reo sovereignty.	Big Tech vs State vs Community.	DM 5 impact investors.	“This is a governance choice.”
11	Collective Advantage. Competitive advantage asks who wins. Collective Advantage asks who becomes capable together. Community Care Keys turn access into shared capacity.	Collective Advantage quote card.	Send to cooperative and mutual contacts.	“Language infrastructure can compound in communities.”
12	Soft infrastructure. Cables, compute, platforms, identity, trust, learning content, and access keys all form a stack. #iuwe works at the layer where culture meets access.	Stack diagram.	Invite 5 prospects to receive postcard.	“Ask me for the one-page access-key explainer.”
13	One hour proof. After one hour with #iuwe, a learner can sing a waiata, ask a question, introduce themselves, open with karakia, and call the community to action.1 In the video, I will break the fourth wall: “This is the investor update, and it is also the teaching model. You are learning the pattern as I explain why it deserves operational funding.” That is not exposure. That is capability.	Outcome stack table plus a live 15-second practice prompt.	Send Discourse link to education contacts.	“Would you fund the first 1,000 learners who can practise this way 24/7?”
14	Purea Nei assembles itself. The learner does not memorise a song as an object. The words, sounds, and frames gather until the waiata becomes speakable.	Purea Nei generative line.	DM cultural education contacts.	“This is design, not content dumping.”
15	Baker’s dozen. The first hour is designed around repeated hearing and speaking, with roughly thirteen encounters per word in the pathway described by #iuwe.1 Repetition is not remedial; it is infrastructure for confidence.	13 repetitions graphic.	Message phonics / literacy contacts.	“Practice is the platform.”
16	No hea koe? Place before name. Whakapapa before résumé. A platform that teaches this is doing more than vocabulary. It is restoring the order of encounter.	Mihi opener visual.	Send to Māori, Indigenous, and diaspora contacts.	“What would 1,000 first introductions unlock?”
17	The call to action. “Me tāpiri e iuwe ō tātou reo.” I must add my voice, and I am inviting each whānau to add a voice too. A Community Care Key is one practical way to add a voice.	Call to Action line card.	Ask 3 warm contacts for referrals.	“Who will hold the first block of keys?”
18	Karakia and confidence. A learner who can open a room has crossed a threshold. Learners are no longer watching language from outside.	Karakia line card.	Send to community leadership contacts.	“Access creates participation.”
19	The one-hour investor test. If a learner can do this after one hour, what happens when 1,000 learners receive a year of access?	Before/after frame.	Book first Singapore pitch call.	“I am opening 20-minute calls this week.”
20	Community Care Keys. Each key is a unique live URL endpoint. It is QR-native, familiar, and practical. No crypto wallet. No speculative token. Just access. I will show the fourth wall plainly: the 6-million-QR layer already exists across 20 colours; the operational move is assigning an owner to a QR and moving it from not sold or magic into sold/owned. In the video, I will hold the investor frame and the learner frame together: “This key funds the team, opens the door for one learner, and gives that learner 24/7 access to whānau-friendly rich-media learning events.”	Key anatomy diagram plus a quick scan-to-access demonstration.	Send one-page key explainer.	“Buy keys. Allocate access. Measure uptake.”
21	SHA-256 without crypto theatre. The key can be cryptographically hardened without asking learners to understand blockchain. Trust stays strong at the back end and simple at the front door.	Front door/back end visual.	Message technical trust contacts.	“The URL is the trust foundation.”
22	1,000 keys. From NZ$2.50 per person per year in bulk, 1,000 learners can be activated from NZ$2,500: less than the cost of many small professional workshops. The 1,000-key bundle is also the clean place to package ordinary access, 20-colour variety, and ring-fenced magic-number value without confusing the public NZ$3 koha promise.	Pricing table plus bundle anatomy.	Ask 5 prospects for a yes/no on 1,000 keys.	“Can you underwrite one cohort?”
23	Not sponsorship. Procurement. Sponsorship asks for visibility. Procurement asks whether the thing purchased creates value. Community Care Keys create access.	Procurement vs sponsorship graphic.	Send procurement-language email to institutional contacts.	“This is a clean access purchase.”
24	Allocation logic. Keys can be allocated to a marae, classroom, whānau cluster, diaspora group, or community partner. A buyer can fund access without controlling the community.	Allocation flow.	Prepare sample allocation report template.	“Fund the keys; let communities breathe.”
25	The annual rhythm. A one-year key creates enough time for daily practice, community events, and learner-to-tuakana transition.	365-day access visual.	Follow up all open DMs.	“Annual access is long enough to matter.”
26	The operating ask. I do not need funding to imagine the platform. I need funding to operate, distribute, support, report, and keep the infrastructure alive.	“Built → Operate” graphic.	Send call booking link or propose times.	“Would you like the Singapore deck?”
27	Oñati. Oñati shows that community wealth building can help a town adapt through disruption, including digital local-commerce responses during crisis.6 The lesson for #iuwe is simple: local control is resilience.	Oñati quote card.	Send Erena/Ian Grigg Basque note.	“Community ownership is not nostalgia.”
28	Mondragón. Mondragón is famous because it made cooperation operational: finance, education, work, governance, and long-term resilience in one ecosystem.7 #iuwe asks what that looks like for language infrastructure.	Mondragón ecosystem map.	DM cooperative economy contacts.	“What is the digital equivalent of cooperative infrastructure?”
29	Darwin and resilience. The resilient system is not the biggest or loudest. It is the one that adapts while preserving what matters. Community-owned reo infrastructure is cultural adaptation with memory.	Adaptation quote card.	Send to Ian Grigg with governance angle.	“Adaptation without extraction.”
30	Platform cooperatives. Platform cooperative thinking asks whether digital platforms can be owned and governed by the communities that depend on platforms.8 #iuwe extends that question to language revitalisation.	Platform coop comparison.	Request introductions to platform-coop networks.	“The platform can be the commons.”
31	Speak little, do a lot. Mondragón commentary often returns to the practical culture of doing rather than boasting.8 I invite #iuwe to be judged the same way: live stream, live app, live keys.	Proof stack.	Send proof-stack summary to prospects.	“Inspect the live system.”
32	The Erena bridge. The Basque frame is not decorative. It gives a serious European cooperative analogy for why language, work, place, and digital tools belong in the same conversation.	Basque/Māori bridge visual.	Follow up Erena/Ian with 3 proposed asks.	“Can I convene a 30-minute cooperative infrastructure conversation?”
33	The Singapore bridge. Singapore understands infrastructure, trust, and global pathfinding. The invitation is to become an early buyer of community-owned language access, not a passive admirer. I can also show that `whanau.tv` is the family rail inside a 12-rail pluriverse network, with pathways such as `xueyong.io` available for Mandarin diaspora leverage.	Singapore bridge visual plus 12-rail map.	Confirm pitch calls for Days 35–39.	“First buyers create the reference case.”
34	The deck is ready. The Singapore deck asks one question: who will pre-purchase the first serious block of Community Care Keys?	Deck cover preview.	Send deck to booked calls.	“Reply ‘deck’ and I will send it.”
35	The first 1,000. Every movement needs a first credible procurement. 1,000 keys is a clean beginning: enough to show uptake, small enough to act now. I will make the fourth wall explicit: “If you have watched this series, you have not only heard the plan. You have seen the teaching method, the access model, and the operational conversation happen in the same frame.”	1,000-key card plus split-screen: me teaching / me explaining the procurement.	Hold pitch calls.	“Can you say yes to 1,000?”
36	Reporting without bureaucracy. Buyers receive a simple report: number of keys allocated, communities reached, activation status, and next operational need.	Report mock-up.	Send reporting template after calls.	“Simple purchase, visible outcome.”
37	Why now. AI in education is accelerating. If communities do not own trusted learning infrastructure now, the future may force community voices back into rented access from someone else’s platform.	Urgency quote card.	Ask undecided prospects what would make yes easy.	“The window is open now.”
38	The 5,000-key invitation. For investors already aligned with the thesis, 5,000 keys creates a regional signal. It says language infrastructure can be funded like access, not begged for like charity.	5,000-key table.	Make anchor-buyer ask.	“Would you become an anchor buyer?”
39	The public thank-you option. Some buyers will want quiet allocation. Some can be named as early infrastructure purchasers. Both paths are welcome. The community outcome comes first.	Acknowledgement options.	Confirm decision dates.	“Public or quiet, the keys still open doors.”
40	Close the loop. Forty days ago the counter went on. The question now is practical: how many Community Care Keys will be purchased, allocated, and activated next?	Counter + key + learner.	Send final follow-up to all prospects.	“The door is live. Who opens it now?”

Postcard Design Brief

I will use the same visual grammar as the Europe postcard while making four Singapore-specific adjustments. First, the headline will move from campaign identity to infrastructure clarity. Second, the iho.whanau.tv proof point will be visible. Third, the price will use the from NZ$2.50/person/year bulk community-owned framing, while preserving NZ$3/key as the public koha equivalence. Fourth, my photo will appear in a social-media style circle, replacing the koru/tāngata motif while keeping the wider Māori visual language respectful and restrained.

Component	Front of Postcard	Back of Postcard
Primary headline	Community-owned language infrastructure is live.	Buy access keys, not equity. Fund learners, not extraction.
Subheadline	From NZ$2.50 per person per year in bulk, a Community Care Key opens a year of #iuwe access.	Each key is a live QR-code endpoint that gives one learner access to the platform; the public koha pathway remains NZ$3/key.
Proof	`iho.whanau.tv` counter visible in the design.	“The stream is live. The app exists. The Strapi backend is intact. 6 million QR endpoints already exist across 20 colours.”
Human signal	my circular profile image, social-media style, upper right or lower right.	Short founder note from me.
Mechanism	QR code to a live explainer page or sample key.	Example key format: `https://iuwe.whanau.tv/WH-RD-C000000001`
Ask	Pre-purchase 1,000 Community Care Keys.	“1,000 keys = from NZ$2,500 = one year of access for 1,000 learners.”
Tone	Clean, infrastructure-literate, direct.	Warm, concrete, non-hype.

Postcard copy I can publish:

Community-owned language infrastructure is live.
#iuwe is not asking Singapore to fund an idea. The stream is live at iho.whanau.tv, the reo content system exists, and Community Care Keys are operational. A key is a live QR-code access endpoint for one learner. Buying a block of keys is like buying a Pokémon-style booster box for a community: the collectible-card metaphor is already visible on high streets across the world, but here, from NZ$2.50/year in bulk, each card is unique, giftable, tradeable, scannable, immediately useful, part of a visible access count, and unlocks one year of 24/7 access to whānau-friendly rich-media learning events.

Ask: pre-purchase 1,000 Community Care Keys from NZ$2,500 so 1,000 learners can receive one year of community-owned reo access.

#iuwe_alchemy Social-Post Voice

I can publish the plan as text, but I also need the first social post to sound like the system is already breathing. The voice can be direct, rhythmic, and fourth-wall aware: I am not only announcing an offer; I am showing the heartbeat of the learning system and inviting another voice into it. The post will keep the price simple, show the 12 rails, and turn the 24/7 31/365 stream into plain evidence that educational content delivery is already in play.

#iuwe_alchemy … ko te kakapa manawa — the heartbeat is all it takes to add your voice now so that #your_mokos_moko will thank you later — nā te mea #ko_tēnei_te_papawai_ataata.
#iuwe is deploying a knowledge activation system for the whole family: the #iuwe_360° teaching to learn / learning to teach program. For just NZ$2.50 per person per year in bulk, whānau can access 24/7 #iuwe learning from the lounge.
In the 21st century, #iuwe does not need expensive corporate contracts. I need #collective_advantage, #community_ownership, and the #iuwe_will_to_learn.
#kaua_e_wareware — don’t forget: if it walks like a duck and quacks like a duck, it is 24/7 365 educational content delivery in play.
#iuwe ∈ #6_billion_global_lifelong_learners.

Social Element	Purpose	Copy / Link
White paper	Ground the philosophical and technical frame.	`https://hau.whanau.tv/t/2788`
Economic framework	Ground the commercial logic.	`https://hau.whanau.tv/t/economic-framework/2787`
Revenue guide	Ground the funding pathway.	`https://hau.whanau.tv/t/2785`
Operating guide	Ground the live operating system.	`https://cdn.whanau.tv/wb00_manual_foreword_v01_82a4f75315.pdf`
Magic numbers	Ground the ring-fenced collectible layer.	`https://hau.whanau.tv/t/the-maths-of-mana/2789`
12 rails	Show the pluriverse is already deployed.	`iho.whanau.tv`, `iho.anana.tv`, `iho.papatuanuku.me`, `iho.kapai.tv`, `iho.asilia.tv`, `iho.ayni.tv`, `iho.freelearn.tv`, `iho.xueyong.io`, `iho.shkola.tv`, `iho.madrasa.tv`, `iho.gratisaprender.tv`, `iho.freelearn.tv`

Continue to Post 4: The public rhythm needs targeted conversations. Post 4 covers the Singapore pitch deck, direct outreach, measurement dashboard, immediate next actions, and references.

References for This Post

paulransfield · May 9, 2026, 6:07am

SGP 40-Day Plan — Post 4 of 4: Outreach, Dashboard, Immediate Actions

Reader note: This final part turns the proof trail into investor conversations and operating discipline. It covers Erena / Ian Grigg outreach, the Basque cooperative frame, Singapore pitch deck, direct outreach, measurement dashboard, and immediate next actions.

Erena / Ian Grigg Outreach Using the Basque Cooperative Frame

My Erena/Ian Grigg outreach will not ask Erena or Ian to “like” the campaign. It will ask Erena and Ian to help validate and transmit the deeper frame: community-owned infrastructure as a resilience strategy. The Basque example matters because Oñati and Mondragón show that local institutions, cooperative ownership, education, and practical adaptation can be mutually reinforcing. OpenDemocracy’s Oñati case describes a town using cooperative economic DNA and a local digital platform during crisis, while Participedia frames Mondragón as a participatory business-management system grounded in share ownership, participatory decision-making, and equitable payment.6 7

Recipient	Frame	Ask	Desired Outcome
Erena	Basque/Māori bridge: language, place, cooperative resilience, and cultural infrastructure.	“Would you review the Basque analogy and suggest one person in the cooperative or cultural-resilience world who needs to see it?”	A warm bridge into Basque/cooperative networks.
Ian Grigg	Governance and trust: unique URL endpoints, access keys, community infrastructure, and anti-extractive platform design.	“Would you pressure-test the trust model and introduce one Singapore-type infrastructure thinker?”	A stronger governance narrative and a high-trust introduction.
Shared thread	Oñati + Mondragón + #iuwe.	“Could I convene a 30-minute conversation on community-owned digital infrastructure as the third way?”	A small expert conversation that can become public proof.

Message I will send to Erena:

Kia ora Erena, I am shaping the Singapore pathway for #iuwe around a Basque cooperative frame: Oñati, Mondragón, Darwinian resilience, and the idea that communities survive rupture by owning the infrastructure communities depend on. The analogy is not decorative. Oñati shows local digital adaptation; Mondragón shows cooperation made operational across finance, education, work, and governance. #iuwe asks what that looks like for language sovereignty. Would you be willing to look at the one-page frame and suggest one Basque/cooperative person who needs to see it?

Message I will send to Ian Grigg:

Ian, I am moving #iuwe into a Singapore investor pathway using Community Care Keys: unique live URL endpoints that can be purchased in bulk to open access for learners. The frame is deliberately not blockchain-first. The URL is the trust foundation; cryptographic hardening can sit behind it; the learner only needs a QR code. The wider thesis is the third model between Big Tech extraction and state control: community-owned digital infrastructure. Would you pressure-test the trust/access framing and suggest one Singapore-type infrastructure or governance contact who needs to hear the pitch?

Singapore Pitch Deck Structure

I will keep the deck concise: ten to twelve slides, with the first three slides proving that the category is infrastructure rather than education content. The design will be sparse, using the counter, key format, three-model table, and one-hour learner outcome as evidence. I will not over-explain te reo Māori; I will use the deck to show why access, ownership, trust, and repeatable learner outcomes belong in the same investment conversation.

Slide	Title	Core Message	Visual
1	Community-Owned Language Infrastructure Is Live	#iuwe is operational; this is an access-purchase conversation.	`iho.whanau.tv` counter.
2	The Problem: Two Bad Defaults	Big Tech extracts; state systems centralise; communities need a third way.	Three-model table.
3	The Third Way: Community Ownership	The platform is designed around community benefit, reo sovereignty, and practical access.	Community ownership diagram.
4	What Exists Now	24/7 stream, live i mahi pai app, intact Strapi backend, 1,440 words already loaded, Koha Gateway live, operating guide, 6 million QR endpoints ready for owner assignment, ring-fenced magic numbers, and 12 deployed pluriverse rails.	Proof-stack list.
5	One Hour Outcome	Learners can speak/sing/introduce/open/call to action after the first-hour pathway, and the investor videos demonstrate that learning pattern rather than merely describing it.1	Outcome stack plus fourth-wall video still.
6	The Mechanism: Community Care Keys	Each key is a unique URL/QR endpoint. The system already has 6 million prepared QRs across 20 colours; live status begins when an owner is assigned. Magic numbers are ring-fenced, so 1,000-key bundles can include ordinary access and special-number value. Simple for learners; robust behind the scenes.	Key anatomy with not sold / magic / sold states.
7	The Ask	Pre-purchase 1,000, 5,000, or 10,000 keys from NZ$2.50 per key per year in bulk; public koha remains NZ$3 per key. Use `whanau.tv` as the family rail, with strategic discounting available on additional pluriverse rails such as `xueyong.io` where distribution proof matters.	Pricing table plus 12-rail map.
8	Why Singapore	Singapore understands public-good AI, trusted digital infrastructure, and regional pathfinding.2 3	Singapore bridge.
9	Why Now	AI education and digital platforms are scaling; communities need ownership before dependency hardens.	Timing graphic.
10	How Allocation Works	Koha or bulk purchase flows through Stripe, assigns owners to prepared QR endpoints, delivers QR codes, and increments the counter.	Stripe-to-owner-assigned-key flow.
11	Governance and Trust	URL-native, QR-first, cryptographically hardenable, no crypto-wallet dependency.	Trust stack.
12	Decision Slide	“Will you pre-purchase the first 1,000 Community Care Keys and help turn prepared QR inventory into live family-learning access?”	Single ask.

Direct Outreach Sequence

I will run private outreach alongside the public content. The cadence will be respectful but persistent: first signal, proof, invitation, close. Each message will be short and will link to one public proof asset so the recipient can verify the conversation is real.

Touch	Timing	Message Type	Purpose	Draft Text
1	Day 1–5	Warm alert	Let close observers know the campaign is live.	“Kia ora, the counter is now on at `iho.whanau.tv`. I am opening a 40-day Singapore pathway for #iuwe Community Care Keys. This is not equity or donation; it is pre-purchased access. I would value your eye on the frame.”
2	Day 7–12	Thesis note	Explain the three-model frame.	“The frame is now clear: Big Tech extraction, state control, or community ownership. #iuwe is the third path for reo infrastructure. I am looking for Singapore-type buyers who understand trusted digital infrastructure.”
3	Day 14–19	Proof note	Share learner outcomes.	“Here is the one-hour proof: after one hour, a learner can sing, ask, introduce, open, and call to action in te reo. That changes the access conversation.”
4	Day 20–26	Ask note	Introduce the key purchase.	“Would you consider or introduce a buyer for 1,000 Community Care Keys? The model is like buying a Pokémon-style booster box for a community: one block purchase, one year of access per key, from NZ$2.50/year in bulk, with each key giftable, tradeable, scannable, counted as a visible community outcome, and connected to 24/7 whānau-friendly rich-media learning events. The 1,000-key bundle can also carry 20-colour variety and ring-fenced magic-number value.”
5	Day 34–40	Close note	Ask for decision or referral.	“I am closing the first Singapore pathway loop this week. Is this a yes, a no, or a referral to the right infrastructure/impact buyer?”

Measurement and Operating Dashboard

I will measure the campaign as a conversion pathway, not as a vanity-content exercise. The most important indicators are conversations opened, decks sent, calls booked, and key packs purchased. Public impressions matter only if those impressions create credibility for private asks.

Metric	Target by Day 40	Why It Matters
Public posts published	40	Creates a visible proof trail and narrative arc.
Singapore-type contacts identified	80	Provides enough surface area for warm introductions.
Direct messages sent	120	Ensures the campaign is not passive.
Warm replies	25	Indicates narrative-market fit.
Pitch decks sent	15	Moves from awareness to consideration.
Calls booked	8	Creates real conversion opportunities.
1,000-key commitments	3	Establishes initial procurement proof.
Anchor-buyer conversations	2	Opens 5,000–10,000 key pathway.
Referral introductions	10	Builds Singapore network density.

Immediate Next Actions

My next three days will be operational rather than conceptual. I will prepare the counter screenshot, confirm the public koha price as NZ$3 per person per year and the bulk investor anchor as from NZ$2.50 per person per year, choose the postcard URL, assemble the first 40-contact Singapore list, confirm Strapi access, export the current i mahi pai content baseline, document the 6-million-QR inventory, visible state logic, ring-fenced magic-number layer, 1,000-key bundle structure, and 12 deployed pluriverse rails, and brief Hussain on Firebase Auth, bulk upload, QR ownership assignment, and the app-embedded koha route. The first post will go out with no apology and no over-explanation: COUNTER ON. The first video will also state the fourth-wall method: “I will be demonstrating the teaching model while leading the conversation about operationalising whanau.tv.” The second action is direct messages to Jim Robinson, Ian Grigg, Hussain Mustafa, and the first circle of high-trust observers.

Day	Action	Lead	Output
0	Confirm NZ$3 public-koha pricing, from-NZ$2.50 bulk investor anchor, 1,000-key bundle logic, and magic-number packaging.	I lead this with Kapai.	Final ask language.
0	Capture counter screenshot, live URL, and example `WH-RD-C000010001` state view.	I lead this with Kapai.	Day 1 visual.
0	Replace koru/tāngata social motif with my circular photo where required.	I brief the designer.	Updated profile visual system.
0	Confirm Strapi login, export current i mahi pai content, and record 1,440-word baseline.	I	Content audit starting point.
0	Send bounded technical brief to Hussain.	I	Auth/upload/koha-route confirmation pathway.
1	Publish COUNTER ON post.	I	Public campaign start.
1	DM first 10 warm contacts, including Hussain for the technical rail.	I	First reply set.
2	Build Singapore-type target list.	I lead this with assistant support.	80-name outreach sheet.
2	Draft Koha Gateway redirect copy, Stripe metadata requirements, and QR ownership-assignment fields.	I lead this with assistant support.	Koha implementation brief.
3	Draft and export postcard plus the first #iuwe_alchemy social-post layout.	Designer / Assistant	Shareable PNG, print-ready file, and social post.
3	Create `ako` category plan and 60-CardSet checklist.	I	Content refresh execution sheet.

This is why I am publishing the plan before the videos. The text is already the rehearsal. The videos will simply make visible what the plan is already doing: I am demonstrating the teaching-and-learning model while leading the investor conversation about operationalising whanau.tv.