Sprint 63 · Open Decisions Log

What the founders need to decide (surfaced by S63)

Governance decisions surfaced while building the founder-witness scaffolds. Each has a proposed default (my recommendation as delegated-authority editor), a decision-owner, and a priority. None of these blocks S63 core progress, but every one of them will need to be answered before founder-witness locks at G5.

Decision 1 · Domain identity (HIGH)

Is LWD's public identity lifewithoutdebt.org.au or cosailifewithoutdebt.org?

HIGHS63-DEC-01

The facts (three candidates now in play):

  • cosailifewithoutdebt.orgthe live production domain. Registered, DNS-active, bound to the Cloudflare Pages project, HTTPS certificate valid. Reads awkwardly in donor comms ("Co-Sai Life Without Debt"). Every public URL today is served from here.
  • lifewithoutdebt.org.aureferenced 43 times across 16 files (email signatures, referrer MOUs, donor materials, Christmas Appeal). NOT registered · no DNS · not in LWD's Cloudflare zones. Two files already self-flag it as [placeholder, domain pending]. Australian-charity-preferred namespace, reads naturally.
  • lwd.orgSprint 63 turn-4 placeholder (2026-08-11): user assigned [email protected] and [email protected] as founder return-emails on the brief forms. This is a third candidate, short, clean, but also NOT registered (checked Cloudflare zones: not owned). The @lwd.org address on the forms is a placeholder pending the wider domain decision below.
Decision needed
Pick ONE canonical charity domain from the three candidates (or a fourth). Every downstream artefact, email addresses, footer signatures, referrer MOUs, donor materials, normalises to it in a single site-wide sweep.
Proposed default
Register lifewithoutdebt.org.au as first choice (charity-preferred namespace, matches 43 existing references, most natural donor read). Fallback: lwd.org if .org.au is blocked (short + memorable, matches the founders' colloquial usage of "LWD"). Last resort: normalise everything to the already-live cosailifewithoutdebt.org and remove the placeholder disclaimers. In every case: register email at the chosen domain (Google Workspace or equivalent) so lisa@… and laurence@… actually receive mail.
Decision owner
Founders (Board decision)
Trigger
Blocks any external send (donor mailouts, referrer MOU dispatch) that includes an @lifewithoutdebt.org.au email address, that address does not currently receive mail.
Est. effort
Registration: ~1 hour. Site-wide edit if defaulted to .org: ~30 mins.

Decision 2 · Lisa Hugo role-label (HIGH)

Which single role-label does Lisa carry across all LWD artefacts?

HIGHS63-DEC-02

The site currently uses six distinct labels for Lisa. Occurrence audit:

Label variantOccurrencesWhere used
Co-founder & Head of Philanthropy48Governance docs, donor deck, most public pages
Business Development Director & Co-founder14Constitution, Board resolutions, ASIC-facing docs
Community & Medical Liaison22Structure page, financial projections (as employed role)
Beneficiary Liaison Officer6Board minutes, employment offer terms
BD-team lead2Standing Order #6 language (Sprint 32)
Founding Member1Business Development Director framing

The tension: "Head of Philanthropy" is donor-facing and reads well externally. "Business Development Director" is what the Constitution names. "Community & Medical Liaison" is her employed role under the funding model. All three are true, but the site treats them as interchangeable, which they are not.

Decision needed
Adopt a hierarchy: e.g. Constitutional title / Public role / Employed role / Voice-authority rolewith one primary label used at first mention and the others as clarifying context. And: does the 30-yr medical BD/S&M professional history change any of the above?
Proposed default
Adopt this pattern at first mention on any page: "Lisa Hugo (Co-founder & Business Development Director; donor-facing role: Head of Philanthropy; employed role from Y1: Community & Medical Liaison; 30 years medical-industry BD/S&M)". Subsequent mentions on the same page use just "Lisa Hugo". Post-decision, do a site-wide normalisation sweep.
Decision owner
Lisa Hugo (label is about her); Board approval
Trigger
Any founder-witness content that names Lisa's role. Effectively every downstream artefact.

Decision 3 · Laurence Hugo role-label (HIGH)

Same question for Laurence, which single primary label?

HIGHS63-DEC-03

Four labels in circulation:

Label variantOccurrencesWhere used
CEO48Most operational and marketing docs
co-founder25Alongside CEO in most first-mentions
Founding Director14Constitution, Board resolutions
CEO Director10Governance-adjacent docs
Technical Negotiator8Two-entity model / CMS-relationship context

Not captured in the current label set: ACL 387398 holder (10 occurrences), CMS founder, 30 years consumer credit mediation practice. These are the credibility anchors that S63's whole thesis rests on, and they're currently secondary in every label.

Decision needed
Should the professional-practice framing (ACL 387398 / CMS founder / 30 years) be part of the primary label, or should it stay as post-name context?
Proposed default
Adopt at first mention on any page: "Laurence Hugo (Co-founder & CEO Director; ACL 387398 holder; founder of Credit Mediation Services Pty Ltd; 30 years consumer credit mediation practice)". Subsequent mentions on the same page use just "Laurence Hugo". Constitutional/Board docs may prefer "Founding Director" over "CEO Director", treat that as a per-context override, not a rewrite.
Decision owner
Laurence Hugo; Board approval
Trigger
Same as Decision 2, every downstream artefact.

Decision 4 · Return-email address for the brief forms (MEDIUM)

Which email address should the Q&A forms auto-populate as the "To:" when a founder hits Send?

MEDIUMS63-DEC-04

Status: Sprint 63 turn 4, placeholder set. Lisa's form → [email protected]. Laurence's form → [email protected]. Each founder's answers now email to their own placeholder address on hitting Send.

Open sub-decisions:

  • Final domain@lwd.org is a placeholder pending DEC-01 above. Whatever DEC-01 resolves to, these addresses migrate to ([email protected] · or the fallback).
  • Send-to patternright now each founder's form sends to their own address, meaning they hold their own copy and forward it manually to whoever needs it. Alternative: both forms send to a single project-sponsor address (e.g. [email protected]) so answers land in one inbox automatically. Both patterns are defensible; the current pattern gives founders more control.
  • Mailbox provisioningeven after DEC-01 resolves, someone has to actually create the mailbox (Google Workspace / equivalent). Until then, [email protected] and [email protected] are non-receiving addresses. If a founder hits Send today, the answers go to /dev/null.
Decision needed
(a) Final domain (chained to DEC-01) · (b) Send-to pattern (per-founder vs single sponsor inbox) · (c) Mailbox provisioning trigger date.
Proposed default
Keep current per-founder placeholder pattern. Both founders have long-running personal/business inboxes, until the LWD domain is live, ask them to forward their form-sent answers from their own mail to the project sponsor manually. When DEC-01 resolves, both addresses migrate to the chosen domain and a briefs@… CC is added.
Decision owner
Founders (this is about their inboxes)
Est. effort
Placeholder patch: DONE (Sprint 63 turn 4). Full resolution: gated on DEC-01.

Decision 5 · S55.2 voice-capture rescope timing (LOW)

Rescope S55.2 held items now, or after founder-witness locks at G5?

LOWS63-DEC-05

Three Christmas-Appeal items are currently held as voice-capture gaps: Email E2, LinkedIn LI-LM-L2 (Lisa 2 Dec), LinkedIn LI-LM-L3 (Laurence 3 Dec). All three were held pending founder voice. When founder-witness locks, these three should be rescoped and either drafted (if witness content covers them) or requeued as separate voice-capture asks.

Decision needed
Trigger the rescope automatically at G5-lock, or hold for a discrete conversation?
Proposed default
Auto-trigger at G5-lock; the rescope pass is FRAME-09 (mandatory downstream sweep). No separate ceremony required.
Decision owner
Delegated-authority editor (default: proceed as proposed)

Decision 6 · Advisor welcome-brief format (LOW)

Should Deen and Carla receive equivalent Q&A briefs to Lisa & Laurence's?

LOWS63-DEC-06

Board-Appointed Advisors under clause 27A are not founders, they don't populate the professional-witness doc. But the Board-Advisor Charter needs their input on their own scope at G2 (Deen) and G3 (Carla). That input could be captured (a) via a shorter Q&A brief similar to Lisa/Laurence's, or (b) via a document review with tracked-changes, or (c) via a Board-minute discussion.

Decision needed
Which capture format for advisor input on the Board-Advisor Charter?
Proposed default
Wait until Laurence's Part 6 answers are in, then draft the charter and send it to Deen and Carla as document-review-with-tracked-changes. Their edits become the G2 and G3 sign-offs. No separate Q&A brief needed.
Decision owner
Delegated-authority editor (default: proceed as proposed)