---
title: 'WBC Multipage v1: From One Page to Five Public Entrypoints'
description: >-
  This release separates WBC’s public narrative into five complete pages while
  preserving the Build Log, machine interfaces, and field-evidence-0 boundary.
date: '2026-07-21'
slug: wbc-multipage-v1
visibility: public
status: published
tags:
  - WBC
  - Multipage
  - Build in Public
featured: false
locale: en
translationKey: wbc-multipage-v1
author: WBC
sourceId: en/wbc-multipage-v1.md
sourceHash: 22aac55948c7cff267a89fa66a28c63b8a65e8bfa546351afdc5b74760e126c2
---
# WBC Multipage v1: From One Page to Five Public Entrypoints

This record describes the architecture, narrative, and reality boundary released into this site build. It does not mean that production deployment is complete; build verification, deployment, and public checks remain separate facts.

## Five public entrypoints

WBC’s durable public content no longer needs to fit on one homepage. This site structure contains five semantic pages, each with Chinese and English routes:

1. `/`: the shortest route to understanding WBC and its current state;
2. `/wbc/`: why WBC exists, its naming, and its boundaries;
3. `/club/`: WBClub as a club-like small team;
4. `/coffee/`: WBCoffee as a venture-like small team organized around a concrete goal;
5. `/build/`: current status, public records, and the Human + Agent interfaces.

The existing `/notes/*` routes continue to preserve dated public records. The new core pages do not replace them.

## Public narrative

The homepage and core pages now share one primary statement:

> WBC is the community and collective-action layer for the AI work transition.

This release continues to use `WBC` as the shared abbreviation for `WorkBuddyClub` and `WorkBuddyCoffee`.

`WBClub` is shorthand for `WorkBuddyClub`. It behaves like a club-like small team where people stay together through WorkBuddy skills, practice notes, and shared interests.

`WBCoffee` is shorthand for `WorkBuddyCoffee`. It behaves like a venture-like small team where people form roles, tasks, choices, collaboration, and Return around a concrete, demanding goal. Whether a Coffee ultimately opens is not the sole test of whether the team existed.

## Definition, release, and evidence

The site tracks three different states:

- **Definition** distinguishes project facts, Mark-direct definitions, and working synthesis;
- **Release** means only core pages and Markdown records inside the public boundary enter the site build;
- **Evidence** remains `field-evidence-0`.

The relationship among 1000X, DENS, and DonePartner remains a working concept. Mentioning these ideas on the site does not turn them into an active recruitment program, partner network, or operating digital entity system.

## Reality boundary

This site update is a narrative and engineering action, not field validation. It has not established a real Club, Coffee team, customer, revenue, store, franchise system, 1000X cohort, or DENS node.

WBC is not a Tencent-authorized program. It does not promise a coffee franchise, job placement, equity, legal partnership, income, or store returns. Attending a WBE does not automatically create Club membership; joining a Club does not automatically make someone a Coffee builder; Coffee collaboration does not automatically grant DonePartner or 1000X identity.

Only real replies, objections, introductions, meetings, willingness to build, payment intent, or delivery results may change the next loop.

## Human + Agent

Dated public records continue to support four reading modes:

1. Human web pages;
2. the `/content-index.json` structured index;
3. the `/llms.txt` LLM entrypoint;
4. Raw Markdown for every record.

Releasing this record into the public source does not mean that public deployment is complete. After deployment, Chinese and English core routes, public records, raw sources, machine interfaces, HTTPS, and representative URLs still require separate verification.