Life Itself Roadmap — September–December 2026

Status: shaping

Purpose

Create a single place of truth for the projects Life Itself intends to undertake between September and December 2026, the material that already exists for them, and the relationships between them. The immediate result should be an agreed graph of work and a rough execution sequence. Individual tasks may later be managed in Asana or GitHub, but this repository is currently the consolidated project-level view.

Situation

Life Itself has several active and prospective projects to coordinate. A central initiative is the rebrand and relaunch of 2R as Seeds of Renaissance, but not all current work is part of that launch. Content capability, project-management infrastructure, and wider operations also need to progress, sometimes in parallel with the launch work.

Complication

The boundaries, relationships, and sequencing of these projects are not yet clear. The team does not have a shared view of what genuinely gates the Seeds of Renaissance launch, what can happen independently or incrementally, and what should happen first. Relevant plans, questions, decisions, and tasks are also distributed across Google Docs, diagrams, GitHub issues, Asana, and other locations, making the work difficult to coordinate, delegate, and track.

Primary question

What are our projects, how should they be sequenced, and which should we focus on now?

Issue tree

• What projects do we have?
  • Have we identified an initial project list? ✅ Yes — see the project-portfolio hypothesis below; its boundaries remain under review.
  • Are the proposed projects correctly bounded?
  • Is anything missing?
  • Which activities are independent projects rather than deliverables within another project?
• What is the sequence of work?
  • Do we do an announcement/launch? ✅ Yes — we will do a launch.
  • What precisely counts as launched? ✅ Seeds of Renaissance is launched when the new brand is publicly visible on its core channels and small web presence, the main calls to action and email capture work, the launch announcement has been sent, community outreach has begun, and the first content is published with follow-up content ready.
  • What is the target launch date? ✅ Launch no later than 1 November 2026, with an earlier launch possible if the minimum credible launch package—especially the website component—is ready sooner.
  • Do we gate the rebrand on the launch, so that rollout and launch happen together? ✅ No — we can rebrand and begin the rollout before the formal launch.
  • How polished must the design system and website be before rollout or launch? ✅ Current preference: use a credible “good enough” first pass rather than waiting for the perfect version.
  • Is the full website part of the lightweight brand rollout? ✅ No — rollout may include a small website update, while the fuller website is a distinct project.
  • Which overall sequencing approach do we prefer? ✅ Currently Option 1: staged and parallel delivery.
  • What needs to be completed before launch? ✅ The minimum credible launch package defined in the Seeds of Renaissance launch project.
  • What are the hard dependencies?
  • What can proceed in parallel?
  • What is desirable before launch, but not required?
  • What is the minimum viable website and launch package? ✅ A small, credible web presence and the agreed minimum launch package; neither the full website nor the complete supporting infrastructure is required.
• Which projects should we focus on now?
  • Which work is most urgent?
  • Which work unlocks other projects?
  • Which work can ship quickly?
  • What should explicitly wait?
• What is the planning status of each project?
  • Which projects have clear outcomes and scope?
  • Which already have plans, issue trees, tasks, or source material?
  • Which are ready to execute?
  • Which still require major decisions or decomposition?

Project-portfolio hypothesis

Seeds of Renaissance launch programme

• Seeds of Renaissance rebrand — define the brand narrative, identity, manifesto, and consumer journey.
• Seeds of Renaissance brand rollout — apply the brand across public channels and templates, including a small website update where needed.
• Seeds of Renaissance website — design and build the fuller website and its user journeys and integrations.
• Seeds of Renaissance launch — announce the updated brand and activate the public launch and community outreach.
• Seeds of Renaissance Global Connection Call — First Iteration — relaunch the community calls on a Thursday in October, with Petronella Tyson leading the first iteration; 15 October is the likely first date.

These projects are related but distinct. In particular, defining the brand and publicly launching it should not be collapsed into one project.

Content capability

Content publishing — strategy and delivery is the overarching initiative, connecting two distinct projects:

• Content strategy and plan — determine the content strategy and the course, event, and publishing calendar.
• Content production and marketing pipeline — establish how to finish, publish, and effectively promote content at a sustainable quality and pace.

These projects concern ongoing publishing, independently of the rebrand and launch. Strategy determines what we publish, for whom, and to what end; pipeline improvement determines how we deliver it. The launch can draw on these capabilities but does not define their purpose.

Organisational capability

• Project-management infrastructure — establish a workable system for planning, ownership, coordination, and delivery across Life Itself.
• Operations — capture and coordinate wider operational work that does not belong inside the launch or content projects.
• AI training and integration — build practical AI capability across Life Itself, including Fae’s onboarding, while coordinating with operations and delivery work.

Sequencing hypotheses

There are two live approaches. We currently prefer the first: ship a credible rebrand rollout and launch without waiting for every supporting capability to be complete.

Option 1 — staged and parallel delivery (currently preferred)

Once the brand foundation is ready, a lightweight rollout—including a small website update—can lead to launch. The detailed design system and full website can continue separately. Content strategy and the content pipeline also progress in parallel rather than acting as hard launch gates.

flowchart LR
    foundation["Brand narrative, name and logo"]
    rollout["Brand rollout<br/>including small website update"]
    launch["Launch"]
    detailed["Detailed design system and brand"]
    website["Full website"]
    strategy["Content strategy"]
    pipeline["Content pipeline"]

    foundation --> rollout --> launch
    foundation --> detailed --> website
    rollout --> website
    foundation --> strategy --> pipeline

This option favours momentum and avoids making a perfect website or fully developed content operation a prerequisite for public launch. It still requires us to define the minimum credible rollout and launch package.

Option 2 — integrated launch after full preparation

In this approach, launch waits until the fuller brand rollout and website are complete and the content pipeline is sufficiently operational to sustain good content after launch.

flowchart LR
    strategy["Content strategy"]
    brand["Brand"]
    rollout["Full brand rollout<br/>including good website"]
    pipeline["Content pipeline humming"]
    launch["Launch"]

    strategy --> brand --> rollout --> launch
    strategy --> pipeline --> launch
    rollout --> pipeline

This option creates a more complete and coordinated public launch, but delays visible progress and makes launch dependent on a larger body of work.

Earlier phase plan

The current Seeds of Renaissance source plan proposes:

1. August–September: define the brand and streamline content operations.
2. September–October: build the website and content plan.
3. November: launch the brand.

This is an input to the roadmap, not an agreed sequence. It assumes connections between the rebrand, content pipeline, website, content plan, and launch that now need to be tested. The roadmap should identify hard dependencies, looser sequencing preferences, and work that can proceed in parallel.

Recommended next move

Do one bounded meta-planning pass to confirm the launch date, define the minimum credible Seeds of Renaissance launch package, and identify its genuine blockers. Then make the Seeds of Renaissance brand rollout and launch the primary delivery focus.

Run only the content-strategy and content-pipeline work needed to support that launch in parallel. Do not make the full website, complete content infrastructure, comprehensive operations work, AI integration, or a perfected project-management system prerequisites for beginning delivery. Use the live rollout to reveal and improve the wider planning and delivery infrastructure.

The immediate outcome of the planning pass should be a short execution plan with a confirmed target date, explicit launch gates, owners, and concrete next actions. Once agreed, those actions should be tracked in Beads rather than duplicated in a separate NEXT.md file.

Immediate planning work

1. Consolidate the known source material under the relevant project files.
2. Define the outcome and scope of each project.
3. Identify real dependencies and milestone gates between projects.
4. Decide what should happen first and what can run in parallel.
5. Assign owners and decide where execution-level tasks will be tracked.

Sources

• Project Coordination — README
• [MASTER] SoR 2026 Objectives and Key Results — PROJECT: 2026 Rebrand Run-up Phases
• Rebrand Coggle diagram and issue tree