THE 888

The founding roadmap of Lion.College — the guild for sovereign men, companion order to LionMind.

Eight phases. One hundred and eleven steps per phase. Each step a concrete action. From the day the chapel opens to the day the first apprentices return as masters and the guild becomes self-regenerating.

This document is the map of the work. It is not aspirational; it is operational. Each line is checkable. Each phase has a clear gate. The whole thing is roughly five to ten years.

PHASE I — FOUNDATION · Steps 1–111

The chapel is built before the cohorts are recruited. The body is incorporated before money moves. The constitution is written before the doors open.

The Decision (1–8)

1. Confirm Lion.College is a guild, not a course platform — write a one-paragraph definition and pin it.
2. Write a one-page mission: what Lion.College is for, in plain English.
3. Identify the patron archetype — the Lion of Judah, servant kingship — and document it.
4. Decide on universal entry (no religious test) and write the line that says so.
5. Set the founding cohort size at twelve and commit to it on paper.
6. Set the founding cohort cost at zero (no dues for the first twelve).
7. Decide the geographic anchor — Melbourne — and document it.
8. Sign the founder's compact: this is a five-to-ten-year project, not a launch.

Domain & Stack (9–18)

1. Confirm lion.college registration is active and DNS controllable.
2. Create the Vercel project lion-college linked to the apps/lion-college directory.
3. Set Vercel production region to syd1 to match the rest of the stack.
4. Add lion.college as a verified domain on the lion-college Vercel project.
5. Add www.lion.college as an alias with a 301 to apex.
6. Configure HTTPS-only redirect on the project.
7. Add Riverun SSO env vars: RIVERUN_SSO_URL, RIVERUN_SSO_AUDIENCE.
8. Add a LION_COLLEGE_ADMIN_SECRET env var for internal endpoints.
9. Wire the deploy hook so master-branch merges deploy automatically.
10. Register lion.college in the riverun-site worlds.ts as coming-soon.

The Legal Body (19–33)

1. Decide whether Lion.College is a subsidiary of Riverun Pty Ltd or a new Pty Ltd.
2. If new Pty Ltd: reserve company name with ASIC.
3. If new Pty Ltd: register the company, obtain ACN and ABN.
4. Open a dedicated bank account at ANZ Business for the guild treasury.
5. Set up Stripe (or RiverPay) merchant account for the guild entity.
6. Draft the guild constitution — purpose, ranks, governance, dissolution.
7. Have the constitution legally reviewed (engage AU corporate counsel).
8. Adopt the constitution by founder resolution and minute it.
9. Establish a board (or sole director) and document conflict of interest.
10. Register for GST if revenue is projected over the threshold.
11. Set up bookkeeping (Xero linked to the bank account).
12. Engage a tax accountant familiar with member-society structures.
13. Decide if the guild ever holds member capital (this determines AFSL exposure).
14. Document the answer to (31) in the constitution.
15. File for any necessary trademarks: 'Lion.College', the lion mark.

The Brand (34–43)

1. Define the Lion.College mark — a single lion silhouette or sigil.
2. Commission or design the wordmark in a serif (Iowan / Charter family).
3. Define the colour palette — golds and ambers for ranks, deep stone for ground.
4. Write the tone guide — spare, grave, warm, never breathless.
5. Forbid the following words in all official copy: hustle, grind, alpha, bro, crush.
6. Encourage the following words: craft, mastery, brother, vow, rule, work.
7. Build a one-page brand brief PDF.
8. Source one ritual photograph — silhouette of a man at a workbench, deep shadow.
9. Define the iconography for the three ranks (I, II, III in roman numerals + glyphs).
10. Approve the brand pack by founder signoff.

The Landing Page (44–58)

1. Scaffold apps/lion-college/ with Next.js 14 + TypeScript.
2. Write the hero — Apprentice. Journeyman. Master.
3. Write the three-part topology block — Chapel · Hall · Commons.
4. Write the three-rank explainer with obligations and dues.
5. Write the value-flywheel block — what the guild actually does.
6. Write the 888 phase overview block.
7. Wire the Apply CTA to Riverun SSO with next=/lion-college/apply.
8. Add an Apply form endpoint that records applications in Neon Postgres.
9. Add an email confirmation via LionMail.
10. Add structured OG metadata for sharing.
11. Add a robots.txt allowing indexing.
12. Add a sitemap.xml listing the four anchor sections.
13. Run Lighthouse audit; ensure ≥ 95 on all four metrics.
14. Test the page in mobile Safari, Chrome, and Firefox.
15. Ship Landing v0 to production.

The Founding Constitution (59–73)

1. Define the guild's name and registered status.
2. Define the patron archetype and what it forbids (dominance, predation, deceit).
3. Define the three ranks, their obligations, and their rights.
4. Define how a member becomes an Apprentice — application + interview + acceptance.
5. Define how a member advances to Journeyman — shipped venture + peer review.
6. Define how a member becomes a Master — peer election with supermajority.
7. Define how a member is expelled — code violation, due process, appeal pathway.
8. Define how a member resigns — voluntary, documented, no clawback.
9. Define what happens to dues on resignation.
10. Define what happens to syndicate equity on resignation.
11. Define the role of the founder during the first decade.
12. Define the role of the founder after the first decade — explicit handoff.
13. Define dissolution — what happens if the guild winds down.
14. Append the constitution to the public website (lion.college/constitution).
15. Print and bind a single hardcopy. Store in a known location.

The Code of Conduct (74–83)

1. Do not cheat customers. Refund honestly. Honour your written word.
2. Pay your contractors. Pay your apprentices. Do not exploit junior members.
3. Do not solicit other members' employees without notice.
4. Do not poach other members' customers via guild access.
5. Confidentiality: what is shared in pod stays in pod.
6. No selling outside the guild: members do not pitch you in pod calls.
7. No flexing: do not display net worth, income, or possessions for status.
8. Care for the weakest member. He sets the floor of the guild.
9. Tell the truth even when the truth makes you small.
10. The Code is enforced by the Masters and the Founder, in writing, with due process.

The First Twelve — Recruiting (84–95)

1. Write the founder's invitation letter — short, direct, costly to ignore.
2. Identify twelve men personally — from LionMind brotherhood waitlist + Riverun network.
3. Send the letter individually, not via mailing list.
4. Schedule a thirty-minute one-on-one with each candidate.
5. Use a written intake form — what venture, what virtue, what wound.
6. Score candidates against three criteria: hunger, honesty, capacity.
7. Reject politely and quickly when the answer is no.
8. Make twelve final offers in writing with a signed Apprentice Compact.
9. Collect signatures or formal acceptance from the founding twelve.
10. Publish the founding twelve only with their consent.
11. Stand up a private channel for the founding twelve before launch.
12. Hold one founders' dinner in Melbourne before the first cohort week.

The First Masters (96–103)

1. Identify three founding Masters — operators with 10+ years and clear character.
2. Approach each privately with the Master Compact (different from Apprentice).
3. Define Master responsibilities for the founding year — light, but real.
4. Define Master compensation — equity in the syndicate, not cash.
5. Sign the Master Compact with all three.
6. Hold a founding Master dinner separate from the Apprentice dinner.
7. Set the cadence of Master council — monthly call, quarterly in person.
8. Document each Master's specialty so Apprentices know who teaches what.

Pre-Launch (104–111)

1. Stress-test the application flow end-to-end with three friendly users.
2. Stress-test the SSO + LionMail welcome flow.
3. Pre-write the first four weekly newsletters so launch week doesn't blow up.
4. Pre-record the welcome video from the Founder — five minutes, hand-shot.
5. Print twelve handwritten welcome letters for the founding cohort.
6. Print and sign twelve Apprentice Compacts on heavy paper.
7. Run one founder's solo retreat — 24 hours alone — before the doors open.
8. Open the doors. Phase I complete.

PHASE II — FIRST APPRENTICES · Steps 112–222

Twelve men walk through the door. Pillar I is delivered over twelve weeks. Pods form. Practices hold. The cohort either bonds or dissolves. By Step 222, they have a capstone artefact or they don't.

Cohort Open (112–121)

1. Hold the opening Conclave — a single evening in Melbourne, in person if possible.
2. Founder delivers the Founding Address — fifteen minutes, no slides.
3. Distribute the printed Apprentice Compact and have each man sign in ink.
4. Issue Apprentice rings (or pins) — physical token of membership.
5. Photograph the founding twelve — group portrait, kept for the canon.
6. Assign each Apprentice his pod of three other founders.
7. Pair each Apprentice with one founding Master as mentor.
8. Read the Code of Conduct aloud and have each man speak his assent.
9. Hand each man his personal copy of Pillar I as a printed booklet.
10. Close with the first toast: to the brothers we will become.

Apprentice Onboarding Rituals (122–131)

1. Each Apprentice records a one-minute video introducing himself to the cohort.
2. Each Apprentice writes a 500-word piece on why he is here.
3. Each Apprentice completes a self-inventory — body, mind, spirit, work, debt.
4. Each Apprentice nominates one accountability covenant for the year.
5. Founder reviews each inventory and writes back personally.
6. LionMail address provisioned: apprentice-firstname@lionmind.zone.
7. Riverun OS account provisioned for each Apprentice's venture work.
8. Each Apprentice is given access to Lion Library (private publishing).
9. Each Apprentice is invited to Brotherhood (the persistent community layer).
10. The founder writes the first welcome on each Apprentice's wall.

Pod Formation (132–141)

1. Pods of four are seeded by archetype-pair compatibility (drawn from LionMind).
2. Each pod elects a rotating Pod Convener for the first month.
3. Pods set their weekly meeting time — non-negotiable for twelve weeks.
4. Pods establish a private LionMail group: pod-X@lionmind.zone.
5. Pods agree on a written confidentiality covenant.
6. First pod meeting: each man names his Year-One Vow.
7. Second pod meeting: each man names his Three Practices.
8. Third pod meeting: each man names his Single Largest Lie.
9. Fourth pod meeting: each man names his Greatest Brother In Life.
10. By week four every pod has run four meetings on time.

Pillar I — Lion Identity & Mindset (142–153)

1. Week 1 — The Lion in Scripture: 90-minute module + reading + journal prompt.
2. Week 2 — The Lion and the Lamb: paradox of strength under sacrifice.
3. Week 3 — Who is the Father: identity rooted in givenness, not striving.
4. Week 4 — The Counterfeit Lion: domination, predation, performance lion.
5. Week 5 — The Lion at Rest: sovereignty without hurry.
6. Week 6 — Naming the Wound: the father-wound and identity formation.
7. Week 7 — Naming the Shadow: where each man's lion goes feral.
8. Week 8 — The Body as Temple: physical stewardship as foundation.
9. Week 9 — Memory and Re-narration: rewriting the story of yourself.
10. Week 10 — The Vow Sustained: practice through tiredness.
11. Week 11 — Brotherhood as Mirror: the cohort sees what you can't.
12. Week 12 — Capstone: each man writes his Personal Rule of Life.

Practice Disciplines (154–163)

1. Daily prayer or meditation, fifteen minutes minimum, logged.
2. Weekly Sabbath — one full day off work, off screens.
3. Daily physical training, four times weekly minimum.
4. Daily journal — three lines: gratitude, friction, intention.
5. Weekly confession to one brother — what you fell short on.
6. Monthly retreat — four hours alone with paper and silence.
7. Quarterly fast — 24 hours, water only, no screens.
8. Annual pilgrimage — a journey to a site of personal meaning.
9. Daily reading from the canon — twenty minutes, slow.
10. Practice tracking via a shared dashboard, visible to pod and mentor.

Mentor Pairing & 1:1 Cadence (164–173)

1. Mentor-Apprentice meet weekly for the first month.
2. Then biweekly through week 12.
3. Each meeting follows a written template — wins, losses, next step.
4. Mentor writes one paragraph per meeting and stores it in the Apprentice's file.
5. Mentor escalates to Founder if the Apprentice misses three meetings.
6. Mentor cannot accept payment, gifts, or referrals from Apprentice.
7. Mentor commits in writing to the year — not month-to-month.
8. Mentor-Apprentice may write one published reflection together per year.
9. Mentors meet quarterly as a peer group to learn from each other.
10. Founder coaches Mentors via a private mentor-circle thread.

Monthly Cohort Call Structure (174–181)

1. Held the first Sunday evening of every month, 90 minutes.
2. Opens with the recitation of the Code of Conduct by a rotating Apprentice.
3. Includes one teaching segment by a Master (45 minutes).
4. Includes one cohort check-in — each man one minute.
5. Includes one written prompt to be answered before next call.
6. Includes one petition — bring before the Founder any matter for the guild.
7. Closes with a toast and a memorial line for any losses.
8. Recordings stored in the canon for the founding cohort to revisit.

Conflict & Crisis Response (182–191)

1. Document a written escalation pathway: pod → mentor → Master → Founder.
2. Hold the first crisis drill — a hypothetical conflict — in week 4.
3. Establish a rule: no public airing of pod conflicts.
4. Establish a rule: financial disputes between members go through written arbitration.
5. Establish a rule: relationship/marriage crises trigger Founder + Mentor pastoral support.
6. Establish a rule: addiction or self-harm crises trigger immediate Master intervention.
7. Maintain an off-the-record support channel for the founder.
8. Pre-identify two outside mental-health professionals available to refer.
9. Hold a quarterly post-mortem of any conflicts that arose.
10. Publish (anonymously) lessons learned to the cohort.

Mid-Cohort Audit (192–201)

1. At week 6, founder audits each Apprentice's engagement.
2. Drop-out candidates are interviewed directly — what is the gap.
3. Re-commitments are documented if the man stays.
4. Polite, dignified exits are offered if the man should leave.
5. Pod composition is reviewed for chemistry; reshuffles allowed once.
6. Mentor pairings are reviewed; reassignment allowed once.
7. Practice-tracking compliance reviewed — < 60% triggers a one-on-one.
8. Cohort sentiment measured via an anonymous five-question survey.
9. Findings shared with the cohort verbatim.
10. Adjustments published to the cohort within seven days.

Capstone Design & Delivery (202–211)

1. By week 8, each Apprentice has chosen his capstone modality.
2. Modalities allowed: written rule of life, recorded testimony, public commitment, shipped artefact.
3. Capstone scope is reviewed by mentor and accepted in writing.
4. Capstones are workshopped in pod over weeks 9–11.
5. Week 12 — capstones delivered to the full cohort in a closed gathering.
6. Each capstone is witnessed and signed by the pod.
7. Founder writes one paragraph of reflection per capstone, stored in the file.
8. Capstones are added to the Apprentice's permanent guild file.
9. Outstanding capstones may be published (with consent) to the canon.
10. The cohort celebrates with a single shared meal.

Apprentice → Journeyman Threshold (212–222)

1. Define the explicit Journeyman threshold: completed Pillar I + shipped a thing.
2. Shipped a thing is defined: revenue, salary in operations role, or a public artefact.
3. Each Apprentice submits his Journeyman application in writing.
4. The application includes: what was shipped, what was learned, what is next.
5. Pod votes yea or nay on each Apprentice's elevation.
6. Mentor writes a recommendation letter for each Apprentice.
7. Founder reviews and confirms or holds back elevation.
8. Elevated Apprentices are invested as Journeymen at a small ceremony.
9. Apprentices not elevated remain Apprentices another year — no shame.
10. The transition is documented in each man's file.
11. Phase II closes — the founding cohort either crossed the threshold or was honest about why not.

PHASE III — THE FORGE · Steps 223–333

The Journeyman tier opens. First member ventures are catalogued. Internal procurement begins. Apprentices rotate through Masters' businesses. A second Apprentice cohort enters. The guild has weight.

Journeyman Tier Opens (223–232)

1. Publish the Journeyman Compact — more obligations, more rights.
2. Set dues at A$200/month and route collection through RiverPay.
3. Publish the Journeyman membership directory (member-only).
4. Issue Journeyman rings — different metal from the Apprentice ring.
5. Hold the Journeyman Investiture as a dedicated ceremony.
6. Each Journeyman writes his Year-Two Vow.
7. Each Journeyman commits in writing to mentor at least one Apprentice.
8. Each Journeyman is added to the syndicate observer list (no vote yet).
9. Founder writes a private letter to each new Journeyman.
10. Publish (with consent) the founding twelve's transition story.

First Member Ventures Cataloged (233–242)

1. Build the Member Venture Registry inside the Lion.College admin app.
2. Each member submits venture name, type, stage, capacity, hiring status.
3. Tags allowed: SaaS, services, agency, physical product, media, capital, other.
4. Public-to-members but never to the open web without per-venture consent.
5. Update cadence: quarterly, mandatory.
6. Stale entries flag the member for follow-up.
7. Founder reviews the registry monthly.
8. Members can subscribe to alerts on tags they care about.
9. Cross-references to LionMind brotherhood ventures are added.
10. Inactive ventures are archived but kept in the file.

Internal Procurement Marketplace v0 (243–252)

1. Build an RFP-style channel inside the guild platform.
2. Any member can post a Request: scope, budget, timeline.
3. Requests sit in the guild for 72 hours before going external.
4. Members may bid, decline, or refer.
5. Bids are private to the requester; no public bidding wars.
6. Successful internal deals are tagged and tracked.
7. Quarterly report: A$ value of internal deals routed.
8. No referral fees inside the guild — service is given, money is paid.
9. Founder mediates disputes inside three business days.
10. Year-one target: A$50,000 routed internally between members.

Mentor Workshops (253–262)

1. Each founding Master delivers a five-week workshop on his specialty.
2. Topics: capital, customer acquisition, hiring, operations, contracts.
3. Workshops open to Journeymen + Apprentices.
4. Workshops are recorded and added to the canon.
5. Workshop fee is A$100 — paid to the Master, not the guild.
6. Attendance is capped at twenty.
7. Workshops include one written take-home assignment.
8. Assignments are reviewed by the Master.
9. Top three assignments per workshop are added to the canon.
10. Workshops repeat annually with updated material.

Apprentice Rotations Through Master Businesses (263–272)

1. Master businesses offer 3–6 month paid rotations to Apprentices.
2. Rotation roles are real work, not unpaid internship.
3. Rotation salary is published transparently.
4. Apprentice signs a rotation compact — confidentiality, no poaching.
5. Master writes a rotation review at end of term.
6. Apprentice writes a rotation reflection added to the canon.
7. Rotation outcomes inform the next cohort's pairings.
8. Conflict during rotation: standard escalation pathway applies.
9. Successful rotations may lead to permanent roles (with founder ack).
10. Year-one target: six rotations completed.

Quarterly Venture Reviews (273–282)

1. Each Journeyman reports their venture quarterly: revenue, cost, decision.
2. Reports are written, three pages max, in plain English.
3. Reports go to mentor first, then to a peer triad for feedback.
4. Peer feedback is constructive only — never anonymous, never destructive.
5. Reports are filed in the member's permanent record.
6. Founder reviews all reports; spends ten minutes per Journeyman per quarter.
7. Pattern alerts: a Journeyman whose revenue declines three quarters running triggers a private check-in.
8. Pattern alerts: a Journeyman whose burn exceeds runway triggers an intervention.
9. Stories of recovery from setbacks are added to the canon (anonymous if needed).
10. Annual Venture Of The Year recognised by peer vote.

Brotherhood Integration (283–292)

1. Lion.College members are auto-enrolled in Brotherhood.
2. Brotherhood pods may include non-college Brotherhood members.
3. Cross-college pods are encouraged for diversity of experience.
4. Brotherhood retains its own ritual cadence independent of Lion.College.
5. The college does not absorb the brotherhood; they are companion orders.
6. Members can be in Brotherhood without being in Lion.College.
7. Members in good standing get reduced Brotherhood dues.
8. Joint events held quarterly — one open evening at the Hall.
9. Joint retreat held annually — three days in nature.
10. Cross-membership numbers tracked transparently in the canon.

LionMail Pod Email Infrastructure (293–302)

1. Provision domain pods.lionmind.zone or use top-level lionmind.zone.
2. Each pod gets a private inbox pod-X@lionmind.zone.
3. Pod inboxes are receive-and-archive, threaded by topic.
4. Pod inboxes auto-forward to all pod members.
5. Founder has read-only audit access for crisis only.
6. Members can compose from pod address as a group identity.
7. Pod inboxes are deleted after pod dissolves (consent required).
8. Mail archives are exported to each member on resignation.
9. Spam filtering and threat detection set up via LionMail infra.
10. Annual audit of pod-mail security and key rotation.

Trinity AI Personalised Practice Prompts (303–312)

1. Wire Trinity AI to surface a daily practice prompt to each member.
2. Prompts are drawn from Pillar I + the member's stated practices.
3. Members can opt out; default is opt-in.
4. Prompts arrive via LionMail morning brief.
5. Streaks tracked silently; not gamified.
6. Trinity AI never sees private confession content.
7. AI usage is logged and reviewable by the member.
8. Monthly summary of practice patterns sent to mentor (with consent).
9. AI prompts iterated quarterly based on cohort feedback.
10. Member can delete all AI history with one button.

Pillar I v2 (313–322)

1. Read the founding cohort's capstones for patterns.
2. Identify the three weakest weeks in Pillar I.
3. Rewrite those weeks with the cohort's feedback baked in.
4. Add three new exercises that emerged from cohort practice.
5. Remove two exercises that didn't work.
6. Update the printed Pillar I booklet.
7. Update the digital curriculum.
8. Add a v2-foreword acknowledging the founding cohort by name.
9. Ship Pillar I v2 ahead of second cohort intake.
10. Send the founding cohort the v2 as a gift.

Second Apprentice Cohort Recruit (323–333)

1. Open public applications for Cohort 2 — cap at 24 (double the founders).
2. Use the same application form, refined by Cohort 1 learnings.
3. Mentors from Cohort 1 are eligible to take on Apprentices.
4. Mentor-Apprentice ratio remains 1:1 — no overloading.
5. Holding fee: A$49 application non-refundable (this funds scholarships).
6. Scholarship slots: 25% of the cohort, no income test, by short essay.
7. Phone interviews for shortlist of 50 → in-person for shortlist of 30 → final 24.
8. Investiture ceremony for Cohort 2 happens twelve months after Cohort 1.
9. The founding twelve attend Cohort 2 investiture as Journeymen.
10. Document Cohort 2 with the same fidelity as Cohort 1.
11. Phase III closes — the forge is hot.

PHASE IV — TREASURY & SYNDICATE · Steps 334–444

Dues stabilise. The capital syndicate is born — legally, slowly, with explicit AFSL guidance. The first member venture is underwritten by the guild. Patronage flows. The treasury becomes visible.

Guild Treasury Setup (334–343)

1. Open a dedicated treasury bank account separate from operating.
2. Treasury holds dues, scholarship funds, and conclave reserves.
3. Treasury does not hold member capital (syndicate money is separate).
4. Treasury is audited annually by an external accountant.
5. Treasury balance is published quarterly to members.
6. Founder cannot withdraw from treasury for personal use, ever.
7. Treasury withdrawals require two-signatory approval after year two.
8. Treasury policy document signed and stored.
9. Treasury growth target: A$500,000 by end of Phase IV.
10. Treasury investment policy: term deposits only, no risk assets.

Dues Collection via RiverPay (344–353)

1. Build the dues subscription product in RiverPay.
2. Tier 1: Apprentice — variable, default A$49/mo or scholarship.
3. Tier 2: Journeyman — A$200/mo.
4. Tier 3: Master — A$500/mo.
5. Annual prepayment discount: two months free.
6. Failed payment dunning flow: three friendly emails before suspension.
7. Hardship pause available — six months no-questions.
8. Resignation closes subscription immediately, no clawback.
9. Dues collected: 95% target collection rate by end of year two.
10. Dues data fed to treasury dashboard automatically.

Legal — AFSL Pathway (354–368)

1. Engage AU financial services counsel familiar with member syndicates.
2. Map the syndicate structure: who holds capital, who decides, who is liable.
3. Decide: separate Pty Ltd holding company for syndicate.
4. Decide: appointed representative under an existing AFSL holder, or apply directly.
5. Document the s708 sophisticated-investor pathway for member capital.
6. Document the disclosure requirements for offers to members.
7. Document the conflict-of-interest policy for the syndicate.
8. Document the valuation methodology for member ventures backed.
9. Document the exit / wind-down policy.
10. Document the dispute resolution pathway between syndicate and venture.
11. Public legal opinion summary published to members (not the public).
12. Founder personally signs disclosure that he is not paid by syndicate.
13. Members are informed in writing — repeatedly — that this is risk capital.
14. No syndicate solicitation to non-members. Ever.
15. Annual legal review of compliance.

Capital Syndicate Constitution (369–378)

1. Syndicate is open to Masters and Journeymen only (Apprentices observe).
2. Minimum participation: A$2,000 per opportunity.
3. Maximum participation per opportunity: 10% of any one member's net worth.
4. Investment opportunities sourced from member ventures only.
5. No external founders accepted into the syndicate's deal flow.
6. Each opportunity reviewed by a five-Master investment committee.
7. Investment committee rotates annually.
8. Standardised SAFE or convertible-note template used for all deals.
9. Founder ventures eligible but recused from committee vote.
10. All deals publicly logged (within the guild) — never hidden.

First Member Venture Underwriting (379–388)

1. Identify the first candidate venture — Journeyman with traction.
2. Founder of the venture pitches the investment committee live.
3. Committee performs standard due diligence — same as institutional.
4. Diligence report shared with member-syndicate participants.
5. Decision made: yes / no / not-yet, in writing within fourteen days.
6. If yes: term sheet issued and signed.
7. Funds collected via RiverPay, escrowed before wire.
8. Wire executed; legal docs signed.
9. Post-investment: quarterly reporting cadence established.
10. Public (to members) announcement of the first deal.

Member-to-Member Investment Rules (389–398)

1. Members may also invest privately, outside the syndicate.
2. Private deals must be disclosed to mentor + founder within seven days.
3. Private deals do not count toward the syndicate's track record.
4. The guild does not arbitrate private-deal disputes.
5. Members may not solicit other members for non-syndicate deals at guild events.
6. Members may discuss deals in pod with confidentiality.
7. Members may not short or bet against another member's venture.
8. Members may not poach customers, employees, or investors.
9. Standard non-solicit period after exit from the guild: twelve months.
10. Standard non-compete after exit: none — too anti-competitive.

Syndicate First Deal Through (399–413)

1. First deal closes within ninety days of syndicate launch.
2. Cohort coverage: at least half of eligible Masters participate.
3. Capital deployed: A$50,000–A$250,000 for the first deal.
4. Reporting cadence honoured for first four quarters.
5. Founder of venture remains active in the guild.
6. Lessons-learned post-mortem published to syndicate participants.
7. Any disputes escalated to the dispute pathway, documented.
8. Second deal candidate identified within six months of first.
9. Founder writes the Syndicate Reflections — what worked, what didn't.
10. Track-record document begins publicly within the guild.
11. Outside legal review of syndicate compliance after deal one.
12. Founder writes thank-you notes to syndicate participants.
13. Founder writes thank-you note to the funded founder.
14. Founded venture publishes one canon-eligible reflection on the experience.
15. Public announcement (member-only) of the first deal closed.

Patronage Programme Launch (414–423)

1. Patronage is distinct from syndicate — it's gift, not investment.
2. Masters may sponsor Apprentices financially — directly or via the scholarship pool.
3. Patronage commitments tracked in the treasury.
4. Patrons remain anonymous unless they choose to be named.
5. Patronage does not buy influence over the Apprentice.
6. Patron and Apprentice may correspond — through the mentor — not directly.
7. Patrons may not poach their patronage Apprentices into their businesses.
8. Annual patronage roll published (with consent) at Conclave.
9. Patronage target year-one: A$25,000 funding 5–10 scholarship slots.
10. Patronage target year-two: A$75,000 funding 15–25 slots.

Financial Transparency Reports (424–433)

1. Quarterly treasury balance published.
2. Quarterly syndicate AUM and deals published (deal terms redacted).
3. Annual full P&L of the guild entity published.
4. Annual full P&L of the syndicate vehicle published.
5. Founder's compensation from the guild published explicitly.
6. Founder's compensation from the syndicate published (zero — by rule).
7. External auditor's signed opinion published annually.
8. Members may inspect underlying books at any time, with notice.
9. Public summary published — the guild treats transparency as moat.
10. Annual financial-health report to Masters with confidential commentary.

Year-End Audit & Treasury Trust (434–444)

1. Engage external auditor for year-end review.
2. Year-end audit covers treasury, syndicate, dues, scholarships.
3. Audit report signed and published to members within 90 days.
4. Founder personally signs treasury-trust covenant.
5. Trust structure protects member contributions in case of founder death/incapacity.
6. Successor authority documented: who holds keys, who can sign.
7. Insurance: D&O liability for board and Masters.
8. Insurance: cyber + crime coverage for treasury.
9. Disaster-recovery plan for digital + physical guild assets.
10. Annual financial health letter from founder to all members.
11. Phase IV closes — the treasury is real, transparent, and trusted.

PHASE V — MASTERS ELECTED · Steps 445–555

Peer election begins. The first non-founding Masters are chosen. The Standards Code is published. The expulsion pathway is tested (with a real case if necessary). The first annual Conclave is held — in person, in Melbourne.

Peer Election Constitution (445–454)

1. Election held annually on the same calendar date.
2. Only Journeymen who have served 24+ months are eligible to be Masters.
3. Only Journeymen and existing Masters may vote.
4. Voting is by secret ballot with written reasoning.
5. Supermajority required for election: 2/3 of voting Journeymen + Masters.
6. Founder has one vote, no veto.
7. Candidate may not campaign for himself.
8. Peers may write endorsements; published anonymously.
9. Election results published to the guild within 48 hours.
10. Newly elected Masters invested at the next Conclave.

Master Nomination Process (455–464)

1. Nominations open six months before election day.
2. Any Journeyman or Master may nominate a Journeyman.
3. Nominee must accept the nomination in writing.
4. Nominee provides: venture track record, mentorship record, code adherence.
5. Existing Masters interview each nominee privately.
6. Founder writes a private confidential note on each nominee.
7. Nominees may withdraw at any point before the vote.
8. Nominee list published two months before election.
9. Open Q&A session held one month before election.
10. Voting opens two weeks before election day.

Standards Code Drafting (465–479)

1. Form a Standards drafting committee — three Masters + Founder.
2. Standards Code extends the Code of Conduct into business practice.
3. Section 1 — Customer treatment: refund policy, honest marketing.
4. Section 2 — Contractor / employee treatment: payment terms, leave, dignity.
5. Section 3 — Peer treatment: confidentiality, anti-poaching, anti-shorting.
6. Section 4 — Financial conduct: disclosure, anti-fraud, anti-laundering.
7. Section 5 — Sexual conduct: anti-harassment, anti-coercion, fidelity.
8. Section 6 — Speech and reputation: no public attacks on members.
9. Section 7 — Substance: no addiction in active service capacity.
10. Section 8 — Spiritual conduct: no exploitation of members' faith or vulnerability.
11. Draft circulated to all members for written feedback.
12. Feedback incorporated by drafting committee.
13. Standards Code ratified by 2/3 vote of Masters + Journeymen.
14. Published to the public as a guild commitment.
15. Reviewed and re-ratified every three years.

Code of Conduct Enforcement Protocol (480–489)

1. Any member may file a code complaint via written submission to Founder.
2. Founder triages within seven days — frivolous / requires investigation.
3. Investigations conducted by a three-Master committee.
4. Accused has right to written response and verbal hearing.
5. Investigation concludes within 60 days of filing.
6. Possible outcomes: cleared / written reprimand / probation / expulsion.
7. Expulsion requires supermajority Master vote.
8. Appeals heard by a separate three-Master panel.
9. All proceedings confidential; outcome may be published in summary.
10. Member accused of a crime: immediate suspension pending external resolution.

Expulsion Pathway & Due Process (490–499)

1. Document the precise sequence: complaint → triage → investigation → hearing → vote → appeal.
2. Establish time limits at each step — cannot drag forever.
3. Establish written record requirements at each step.
4. Establish recusal rules for committee members with conflicts.
5. Establish the principle: punishment fits the violation, with charity.
6. Establish that wealth, rank, or proximity to the founder does not protect.
7. Establish that the accused may bring an external legal advisor (at own cost).
8. Establish that expelled members may apply for re-entry after three years.
9. Establish that re-entry requires unanimous Master vote.
10. Document a hypothetical case study illustrating each step.

First Masters Elected (500–509)

1. Election held on the planned date.
2. Voter turnout target: 80% of eligible voters.
3. First non-founding Masters elected (target: three).
4. Results announced live at Conclave.
5. Newly elected Masters give their Investiture Address — five minutes each.
6. Newly elected Masters receive the Master ring and sign the Master Compact.
7. First wave of mentor responsibilities transferred to new Masters.
8. Founder writes personal letters to those elected — and those not.
9. Founder steps back from one Master role to make room.
10. Master council expands from three to six.

Master Investiture Ritual (510–519)

1. Conducted at the Conclave in candlelight (or low-light).
2. Each newly elected Master walks the line of existing Masters one at a time.
3. Each existing Master places a hand on the new Master's shoulder.
4. Founder reads the Master Compact aloud.
5. Newly elected Master speaks his commitment in his own words.
6. The Master ring is placed on his finger by an existing Master.
7. A photograph is taken of the new Master with the council.
8. The cohort claps but does not cheer; the ritual is grave.
9. The new Master joins the council for the rest of the Conclave.
10. The ceremony is documented and added to the canon.

Master Responsibilities Begin (520–529)

1. Each Master accepts one Apprentice immediately.
2. Each Master is assigned a specialty teaching workshop.
3. Each Master attends monthly Master council calls.
4. Each Master pays the Master dues from his first month.
5. Each Master takes a seat on a syndicate review.
6. Each Master is given veto rights on standards-code violations involving his pod.
7. Each Master commits to one canon contribution per year.
8. Each Master commits to attending Conclave annually.
9. Each Master takes a portrait for the guild canon.
10. Each Master writes his Master Year-One Vow.

Annual Conclave Planning (530–539)

1. Conclave held annually on the same weekend each year.
2. Location: Melbourne for the founding decade.
3. Duration: three days — Friday evening to Sunday afternoon.
4. Attendance: all Masters required, all Journeymen strongly encouraged, Apprentices invited.
5. Programme: investiture, workshops, peer venture pitches, capstone presentations.
6. Conclave dinner held Saturday evening — formal, slow, witnessed.
7. Memorial held Sunday morning — for departed members and ventures lost.
8. Founder delivers the State of the Guild address Sunday afternoon.
9. Conclave fee: A$200 covering food and venue — no profit to the guild.
10. Travel scholarships available for members in hardship.

First Conclave Held (540–549)

1. Confirm Melbourne venue six months out.
2. Send invitations twelve weeks out.
3. Confirm Masters' attendance ten weeks out.
4. Programme finalised eight weeks out.
5. Workshops drafted six weeks out.
6. Conclave brief sent four weeks out with reading list.
7. All RSVPs received two weeks out.
8. Conclave runs as scheduled.
9. Conclave post-mortem held one week after.
10. Adjustments documented for Conclave Year Two.

Post-Conclave Adjustments (550–555)

1. Publish photographs and summary to members within seven days.
2. Publish public-facing recap (anonymised) for the website.
3. Send personal letters to each first-time attendee.
4. Send personal letters to each absent Master.
5. Update the canon with all teaching from the Conclave.
6. Phase V closes — the council is real, the standards are written, the year begins.

PHASE VI — THE PILLARS SPREAD · Steps 556–666

Pillar I has been delivered twice. Pillars II, III, and IV roll out. Multiple cohorts run concurrently. Dues flow stabilises. The guild becomes a real ecosystem, not a single experiment.

Pillar II — Spiritual Strength & Discipline (556–565)

1. Outline the twelve weeks of Pillar II.
2. Anchor scripture chosen for each week.
3. Daily practice arc designed: prayer rhythm, fasting, silence.
4. Weekly assignment design.
5. Capstone design: a personal Rule of Prayer.
6. Pillar II booklet printed.
7. Pillar II digital curriculum built.
8. Pillar II piloted with Cohort 1 (now Journeymen).
9. Adjustments made from pilot feedback.
10. Pillar II public launch to Cohort 3.

Pillar II Launch & First Cohort (566–575)

1. Cohort 3 application opens.
2. Founding twelve mentor as Journeymen.
3. Pillar II ceremony held — investiture into the second pillar.
4. Practice tracking adjusted for the new disciplines.
5. Weekly module delivery automated where possible.
6. Mentor 1:1s held biweekly through Pillar II.
7. Mid-cohort audit performed at week 6.
8. Capstones delivered at week 12.
9. Cohort 3 transition to Journeyman.
10. Pillar II completion documented in each member's record.

Pillar III — Character & Virtue (576–585)

1. Outline the twelve weeks of Pillar III.
2. Scripture and classical virtue texts chosen.
3. Practice design: virtue inventory, daily examen, weekly confession.
4. Weekly assignment design.
5. Capstone design: a Character Examination.
6. Pillar III booklet printed.
7. Pillar III digital curriculum built.
8. Pillar III piloted with Cohort 1.
9. Adjustments made from pilot feedback.
10. Pillar III public launch.

Pillar III Launch (586–595)

1. Cohort 4 application opens.
2. Cohort 4 may overlap with Cohort 3 — two cohorts running in parallel.
3. Founding twelve and Cohort 2 mentor as Journeymen.
4. Pillar III ceremony held.
5. Practice tracking and journaling refined.
6. Pillar III emphasis: the integration of belief and behaviour.
7. Mid-cohort audit performed.
8. Capstones delivered.
9. Cohort transition documented.
10. Pillar III completion certified.

Pillar IV — Emotional & Psychological Health (596–605)

1. Outline the twelve weeks of Pillar IV.
2. Engage a clinical psychologist consultant for curriculum review.
3. Practice design: emotional inventory, attachment review, trauma awareness.
4. Weekly assignment design with clear non-clinical scope.
5. Capstone design: a written Emotional Map.
6. Pillar IV booklet printed.
7. Pillar IV digital curriculum built.
8. Pillar IV piloted with Cohort 1.
9. Adjustments made from pilot feedback.
10. Pillar IV public launch.

Pillar IV Launch (606–615)

1. Cohort 5 application opens.
2. Three cohorts now running in parallel — capacity stress-tested.
3. Mentor pool expands to handle the load.
4. Pillar IV ceremony held.
5. Mental health referral pathway formalised.
6. Mid-cohort audit performed.
7. Capstones delivered.
8. Cohort transition documented.
9. Pillar IV completion certified.
10. First wellness review of mentors held.

Cross-Pillar Integration (616–625)

1. Document how Pillars I through IV interlock.
2. Create the Integration Workbook for completing Journeymen.
3. Held bi-pillar workshops: Identity x Discipline, Virtue x Emotion.
4. Encourage Journeymen to write across-pillar reflections.
5. Add cross-pillar capstones for advanced Journeymen.
6. Update the canon with the Integration teaching.
7. Founder writes the Integration essay — public.
8. Cross-pillar mentorship pairing experiments.
9. Cross-pillar pod rotations encouraged.
10. Cross-pillar evaluation criteria added to Master nomination.

Multiple Concurrent Cohorts (626–635)

1. Up to four cohorts may run concurrently.
2. Each cohort capped at thirty Apprentices.
3. Each cohort retains its own pods and mentors.
4. Inter-cohort events held quarterly.
5. Inter-cohort competitions for capstone quality (peer-judged).
6. Inter-cohort venture collaborations encouraged.
7. Cohort identity preserved — each cohort has a name.
8. Cohort alumni gatherings held annually.
9. Cross-cohort newsletter started.
10. Cross-cohort memory and reflection added to the canon.

Journeyman Mentorship Scaling (636–645)

1. Every Journeyman now mentors at least one Apprentice.
2. Master oversight of multi-mentor relationships.
3. Mentor-of-mentors role created.
4. Mentor-training workshop held annually.
5. Mentor sabbatical policy: optional pause every three years.
6. Mentor evaluation: feedback from Apprentices, peers, and Masters.
7. Mentor recognition: annual Mentor of the Year award.
8. Mentor compensation: continuing-education stipend.
9. Mentor mental-health support: peer counsel + external referral.
10. Mentor mistakes: standard escalation pathway.

Dues Flow Stabilises (646–655)

1. Dues collection automated and reliable.
2. Member retention measured monthly.
3. Churn rate target: < 10% annually after year three.
4. Member exits surveyed for honest feedback.
5. Reactivation pathway for paused members.
6. Patronage covering at least 20% of Apprentice dues.
7. Treasury covers operating expenses fully — no founder subsidy.
8. Surplus dues funding canon publishing, conclave, scholarships.
9. Founder draws first market-rate salary at year three.
10. Treasury fully audit-clean for two consecutive years.

Mid-Year Conclave (656–666)

1. Second Conclave of the year established — June (winter in AU).
2. Mid-Year Conclave is smaller, more contemplative.
3. Held over two days, not three.
4. Format: silent retreat morning, teaching afternoon, peer dialogue evening.
5. Attendance optional but encouraged for Journeymen and Masters.
6. Featured teaching from a different Master each year.
7. Memorial focus stronger at the Mid-Year (winter) Conclave.
8. Founder reflects on the year so far at the Mid-Year address.
9. Adjustments to the Annual Conclave made based on Mid-Year Conclave learnings.
10. Mid-Year Conclave documentation added to the canon.
11. Phase VI closes — four pillars are live, multiple cohorts run, the guild has weight.

PHASE VII — THE CANON · Steps 667–777

Lion Library, the guild's publishing imprint, releases the first canon book. Pillars V through VIII are built. Regional chapters seed in Sydney, Brisbane, Perth. The canon grows. The guild outlives single founders.

Lion Library Publishing Imprint Launch (667–676)

1. Establish Lion Library as the official guild publishing imprint.
2. Lion Library reports to the Master council, not directly to the founder.
3. First publishing committee formed: three Masters + founder + editor.
4. Editorial standards published.
5. First annual catalogue announced.
6. ISBN registration arranged for AU publications.
7. Print partner secured for short-run publication.
8. Digital distribution wired (Apple Books, Kobo, direct).
9. Lion Library website published as subpage of lionmind.zone.
10. First call for canon submissions opens to all members.

First Guild Book Published (677–686)

1. First book: The 888 — A Founder's Reflection, written by Founder.
2. Manuscript drafted from internal guild memos and Conclave addresses.
3. Editorial review by the publishing committee.
4. Print run of 500 hardcover copies — for members + libraries.
5. Digital release simultaneously.
6. Launch event held at Annual Conclave.
7. Each member receives a complimentary copy.
8. Public sales begin three months after member release.
9. Royalties returned to the canon-publishing fund.
10. Subsequent works queued.

Member Writings Curated (687–696)

1. The Apprentice Chronicles — a curated collection of capstone reflections.
2. Master's Teachings — annual published lectures from Conclave.
3. Pillar Studies — deep dives into each pillar by Master scholars.
4. Venture Notes — case studies of member ventures (with consent).
5. Mentor Letters — annual collected mentor-to-Apprentice correspondence.
6. Memorial Volume — biographies of members who have died.
7. Canon style guide written — voice, structure, terminology.
8. Submissions reviewed by the publishing committee.
9. Authors retain copyright; guild holds canon publication rights.
10. Authors receive royalties.

Pillar V — Relationships & Brotherhood (697–706)

1. Outline the twelve weeks of Pillar V.
2. Practice design: family inventory, friendship audit, romantic clarity.
3. Weekly assignment design.
4. Capstone design: a Relationships Manifesto.
5. Pillar V booklet printed.
6. Pillar V digital curriculum built.
7. Pillar V piloted with Cohort 1 (now multi-pillar Journeymen).
8. Adjustments made.
9. Pillar V public launch.
10. Pillar V cohort transition documented.

Pillar V Launch (707–716)

1. Cohort 6 application opens.
2. Mentor pool expands further.
3. Pillar V ceremony held.
4. Family integration sessions added (with member's consent).
5. Marital health resources made available via partner network.
6. Mid-cohort audit performed.
7. Capstones delivered.
8. Cohort transition documented.
9. Pillar V completion certified.
10. Founder writes the Brotherhood essay — public.

Pillar VI — Leadership, Influence & Mission (717–726)

1. Outline the twelve weeks of Pillar VI.
2. Practice design: leadership shadow, influence map, mission statement.
3. Weekly assignment design.
4. Capstone design: a Personal Mission Document.
5. Pillar VI booklet printed.
6. Pillar VI digital curriculum built.
7. Pillar VI piloted.
8. Adjustments made.
9. Pillar VI public launch.
10. Pillar VI cohort transition documented.

Pillar VI Launch (727–736)

1. Cohort 7 application opens.
2. Multi-pillar tracks now standard — members at different pillars in parallel.
3. Pillar VI ceremony held.
4. Leadership case studies added from member ventures.
5. External leadership thinkers invited as guest teachers (curated).
6. Mid-cohort audit performed.
7. Capstones delivered.
8. Cohort transition documented.
9. Pillar VI completion certified.
10. Several Journeymen accepted into Master nomination based on Pillar VI work.

Pillar VII — Physical Stewardship & Energy (737–746)

1. Outline the twelve weeks of Pillar VII.
2. Engage a sports-science consultant for curriculum review.
3. Practice design: physical assessment, training programme, recovery rhythm.
4. Weekly assignment design.
5. Capstone design: a Physical Rule of Life.
6. Pillar VII booklet printed.
7. Pillar VII digital curriculum built.
8. Pillar VII piloted.
9. Adjustments made.
10. Pillar VII public launch.

Pillar VII Launch (747–756)

1. Cohort 8 application opens.
2. Physical practice baseline measurements taken for new Apprentices.
3. Pillar VII ceremony held.
4. Strength-training partnerships formalised in pods.
5. Annual physical audit added as a pillar standard.
6. Mid-cohort audit performed.
7. Capstones delivered.
8. Cohort transition documented.
9. Pillar VII completion certified.
10. Physical health outcomes documented across the cohort.

Pillar VIII — Trials, Purity & Battle (757–766)

1. Outline the twelve weeks of Pillar VIII — the heaviest pillar.
2. Engage pastoral and clinical consultants for curriculum review.
3. Practice design: confessional rhythm, temptation inventory, battle plan.
4. Weekly assignment design.
5. Capstone design: a Battle Memoir — what trials you have faced.
6. Pillar VIII booklet printed.
7. Pillar VIII digital curriculum built.
8. Pillar VIII piloted with Cohort 1 — the founding twelve close the Octava.
9. Adjustments made.
10. Pillar VIII public launch.

Pillar VIII Launch (767–777)

1. Cohort 9 application opens.
2. Pillar VIII ceremony held — the gravest investiture.
3. Founder delivers the Eighth Pillar Address — public, kept as canon.
4. The first Pride Members emerge — those who have completed all eight.
5. Pride Membership ceremony designed.
6. Pride Members receive the final ring — the third metal.
7. Pride Members write their Octava Reflection — a major canon contribution.
8. Founder writes letters to each Pride Member individually.
9. The full Octava — eight pillars — is documented as a single canon.
10. The integrated Octava book is announced for the next year.
11. Phase VII closes — the canon is real, the eight pillars are live, the Pride is forming.

PHASE VIII — REGENERATION · Steps 778–888

The first Apprentices return as Masters. The guild self-regenerates. International chapters begin. The 888th day after launch is celebrated. The founder hands off — partially, then fully — to the council.

First Apprentices Complete the Octava (778–787)

1. The founding twelve who remain complete all eight pillars.
2. Each writes his Octava Reflection.
3. Each is recognised at the Annual Conclave as a Pride Member.
4. Photographs of the original twelve are added to the canon's frontispiece.
5. The original twelve are given lifetime membership without dues if they wish.
6. The original twelve choose their continuing role: Master, Patron, Emeritus.
7. Founder writes individual letters of gratitude.
8. The original twelve are honoured in the Annual Conclave's opening.
9. Their stories are published (with consent) as the founding canon.
10. The number 12 becomes a marker in guild liturgy.

Pride Member Status Achieved (788–797)

1. Define Pride Membership formally: completed Octava + active Master/Journeyman.
2. Pride Members may stand for Founder of regional chapters.
3. Pride Members elected to lifetime Master council.
4. Pride Members may publish under the Lion Library imprint with priority.
5. Pride Members vote on canon inclusion.
6. Pride Members commit to lifelong contribution.
7. Pride Member retreat held annually — small, contemplative, in a remote location.
8. Pride Members are listed publicly with consent.
9. Pride Members are the ultimate authority on guild standards.
10. Founder defers to the Pride Council on contested matters.

First Mentor Selection from New Pride Members (798–807)

1. New Pride Members take on Apprentices as their primary work.
2. Each Pride Member mentors at least one Apprentice from a new region.
3. Pride Members may decline mentorship for sabbatical year.
4. Pride Members may invent new mentorship modalities — written, in-person, weekly intensives.
5. Pride Members compensated for mentorship via dues redirection.
6. Pride Member mentorship outcomes tracked.
7. Pride Members are encouraged to write public teaching.
8. Pride Members may launch satellite chapters under guild oversight.
9. Pride Members hold standards-enforcement authority.
10. Pride Members serve as the guild's institutional memory.

Second-Generation Curriculum (808–817)

1. Pride Members rewrite Pillar I from their lived experience.
2. Second-generation curriculum builds on first-generation foundations.
3. First-generation curriculum kept as canon, second-generation as living version.
4. Pride Members write the Octava After — what comes after completion.
5. Curriculum review committee transitions from founder-led to Pride-led.
6. Founder retains advisory but not deciding role.
7. New rituals invented by Pride Members are tested.
8. Curriculum innovations published under shared authorship.
9. The canon expands with second-generation voices.
10. The guild's voice begins to outlive the founder.

International Chapter Pilot (818–827)

1. First international chapter proposed: Auckland, New Zealand.
2. Founder visits, identifies a local Pride Member-elect.
3. Local chapter constitution drafted, mirroring the guild's.
4. Local chapter governance: reports to the central Master council.
5. Local chapter pilot: 12 Apprentices in Auckland.
6. Auckland investiture held with founder present.
7. Second international chapter proposed: London.
8. London chapter pilot launched.
9. Inter-chapter exchange programme launched (Apprentice swaps).
10. Annual International Conclave held — pulling all chapters together.

Guild Treasury at A$1M Cumulative (828–837)

1. Treasury crosses A$1M cumulative dues collected.
2. Syndicate AUM exceeds A$3M.
3. Patronage flow exceeds A$200,000/year.
4. Canon-publishing revenue self-sustaining.
5. Conclave fully self-funded.
6. Founder draws a transparent salary at market rate.
7. Founder's discretionary fund formalised.
8. Endowment fund established for long-term guild durability.
9. Endowment target: A$10M over the next decade.
10. Endowment investment policy published.

Self-Regenerating Cycle Confirmed (838–847)

1. The first wave of internally-developed Masters operate independently.
2. New Apprentice cohorts run without founder direct involvement.
3. Standards enforcement is performed by Master committees the founder does not chair.
4. Capital syndicate operates with rotating Master leadership.
5. Canon publishing operates with rotating editor leadership.
6. Conclave runs with rotating chair leadership.
7. Lion.College survives a founder absence (sabbatical) for three months without incident.
8. Founder writes the Handoff Notes — what only he carries.
9. Handoff Notes shared with the Pride Council.
10. Pride Council ratifies its continuing operating authority.

Annual Conclave Becomes Tradition (848–857)

1. Tenth Annual Conclave held.
2. Original founding twelve all attend (or are memorialised).
3. Members attend who first heard of the guild as Apprentices five+ years prior.
4. The Conclave has its own folkways now — songs, toasts, rituals.
5. The Conclave includes a public dinner inviting LionMind brotherhood members.
6. The Conclave includes a public lecture open to the city.
7. The Conclave is documented in long-form photography for the canon.
8. The Conclave is published as a yearly volume in Lion Library.
9. The Conclave is now an institution.
10. Members who have moved cities arrange their year around it.

Memorial Practices Established (858–867)

1. Memorial canon — names of members who have died.
2. Memorial practice — one minute of silence at every Conclave for the lost.
3. Memorial publication — every five years, a memorial volume.
4. Memorial care — surviving family of members supported by the guild.
5. Memorial fund — emergency aid for members' families on death.
6. Memorial commitments — each member writes who carries his unfinished work.
7. Memorial council — three Masters who handle death and inheritance matters.
8. Memorial liturgy — what is said when a member dies.
9. Memorial bell — rung at Conclave for each new name.
10. Memorial practice extended to Apprentices who never completed.

The 888th Day / Founding Decennial (868–877)

1. Mark the 888th day after Lion.College's opening as a guild holiday.
2. Mark the founding decennial (Year 10) as the major institutional turning.
3. At Year 10, the founder formally hands off operational authority to Pride Council.
4. At Year 10, the founder retains only advisory and canon-author roles.
5. At Year 10, a Public Address is held — open to all of LionMind and Riverun.
6. At Year 10, the canon is republished as the Decennial Edition.
7. At Year 10, the standards code is re-ratified.
8. At Year 10, the constitution is re-ratified.
9. At Year 10, the first Decennial Award is given — to the most-mentored mentor.
10. At Year 10, the guild's existence is celebrated and re-vowed.

Handoff Beyond Founder (878–888)

1. Founder writes his Last Letter — to be opened on his retirement or death.
2. Founder names his successor (or successor election protocol) in writing.
3. Founder transfers all guild IP to the Lion.College entity (not personal).
4. Founder retires from operational responsibility by Year 12 at latest.
5. Founder remains Patron until his death.
6. Founder's name added to the canon as Founding Patron.
7. Founder writes the final Founder's Reflection — added to the canon.
8. Successor begins operating with full Master Council support.
9. The guild continues with rituals, ranks, canon, treasury, and syndicate intact.
10. The first Apprentices have become Masters; the first Masters become Emeritus.
11. The guild outlives its founder. The work is the work. The 888 is complete.

Eight phases. One hundred and eleven steps each. Eight hundred and eighty-eight in total. Begun in faith, completed in patience, sustained by brothers.

Written in Melbourne. Companion to LionMind. For Riverun.

— The Founder