Project DO is the root project for the website as a whole. Within WordPress, it functions as the first and primary project—the point from which all other projects, pages, and initiatives originate.

Project DO exists to turn intent into action.

This website is not a static brochure, blog, or archive. It is a living system designed to capture working knowledge, document decisions, and evolve deliberately over time. Project DO establishes the structure, philosophy, and operating rules that guide how everything on the site is created, revised, and connected.

If nothing else existed on the site, Project DO would still answer:

• Why this website exists
• What it is meant to do
• How it is expected to change without losing clarity

Most websites are built to say something.
This website is built to do something.

The purpose of this site is to:

• Capture working knowledge, not just finished conclusions
• Document decisions, experiments, and outcomes
• Preserve context instead of erasing it
• Improve through use rather than constant redesign

Rather than publishing content and moving on, the site is designed to:

• Revisit assumptions
• Track meaningful changes
• Show how thinking evolves over time
• Remain useful years after publication

This approach prioritizes durability over novelty and clarity over volume.

Version 1.0 establishes the foundation.

The initial release of Project DO focuses on:

• Defining the core purpose and scope of the site
• Establishing a clear project hierarchy in WordPress
• Publishing baseline content that explains what exists and why
• Creating a structure that can grow without being rebuilt

Version 1.0 is intentionally:

• Minimal in surface complexity
• Opinionated in structure
• Clear about what is in scope and what is not

At this stage, the priority is clarity over completeness.

Project DO is designed to evolve in phases, not rewrites.

Future versions may include:

• Expanded documentation layers
• Versioned updates to existing content
• Clear change logs that explain what changed and why
• Stronger cross‑links between related projects

Earlier versions are not discarded. They remain visible as part of the project’s history, preserving context and decision‑making over time.

This prevents the common failure mode where a site grows larger but less coherent.

Project DO follows the same philosophy as the Living Reference Library, applied at a site‑wide level.

• The Living Reference Library answers:
  “What sources, ideas, and references inform this work?”
• Project DO answers:
  “What is this system doing, and how does it change over time?”

Both share the same principles:

• Nothing is assumed to be final
• Context is preserved, not erased
• Updates are additive, not destructive
• Transparency builds long‑term trust

Project DO acts as the operating system of the site.
The Living Reference Library is one of its most important subsystems.

Within WordPress:

• Project DO is the root project
• All other projects inherit structure, conventions, and intent from it
• It sets expectations for how content is created, named, updated, and revised

This ensures the dashboard itself reflects the same principles as the site: clear, intentional, and evolvable.