What Is the 955.WLB Whitelist Project and How Does It Work?

The 955.WLB whitelist is a community-curated GitHub repository that catalogs companies adhering to a 9am-5pm, Monday-Friday work schedule through transparent, peer-reviewed pull requests.

The 955.WLB whitelist project operates within the 996icu/996.ICU repository as a counter-initiative to excessive overtime culture. This lightweight system leverages GitHub's native collaboration features to maintain a version-controlled database of employers that respect standard working hours, requiring no server-side infrastructure or complex automation.

How the 955.WLB Whitelist Works

The project relies entirely on GitHub's built-in workflow tools to manage submissions. This architectural simplicity ensures transparency while allowing instant updates upon community approval.

Community Contribution Workflow

Anyone can propose a new company by opening a Pull Request (PR) against the repository. The submission must include verified evidence such as official announcements, recruitment pages, or internal policy screenshots. Maintainers review each PR for correctness, verify that evidence is publicly accessible, and ensure personal data is properly redacted before merging. Once approved, the merge instantly updates the public whitelist with no additional build steps or CI/CD pipelines required.

Evidence Handling and Storage

Contributors attach proof as PNG or JPG images placed under whitelist/img/. The filename is referenced in the main table using standard markdown link syntax, such as [员工手册](img/company_handbook.png). This approach keeps the evidence permanently archived within the repository while maintaining a clean, readable table format in the documentation.

Repository Structure and Key Files

The entire system consists of minimal static files that work together to create the whitelist:

• whitelist/README.md – Contains the core whitelist table organized by city, company, date, schedule description, and evidence link
• whitelist/img/ – Stores all evidence screenshots referenced by the markdown table
• README.md (root) – Provides context about the whitelist's role within the broader 996.ICU ecosystem
• i18n/ directory – Contains internationalized descriptions of the project for non-Chinese speakers

Adding a Company to the 955.WLB Whitelist

To submit a new company, contributors modify whitelist/README.md by appending a row to the markdown table:

| 城市 | 公司 | 时间 | 制度描述 | 证据内容 |
|:---:|:---:|:---:|:---:|:---:|
| 北京 | [新星科技有限公司](https://xinxing.tech) | 2024年3月 | 9-5-5 (弹性上下班) | [内部手册截图](img/xinxing_handbook.png) |

Follow these steps to complete the submission:

1. Create the evidence image (xinxing_handbook.png) and place it in whitelist/img/
2. Commit the updated README.md and the new image file
3. Open a Pull Request with a clear description, such as "Add 新星科技 to the whitelist – includes official handbook screenshot"

Accessing Whitelist Data Programmatically

Developers can consume the whitelist data directly from the raw markdown file. Here is an example using JavaScript with the marked library to render the table in a web application:

import fetch from 'node-fetch';
import { marked } from 'marked';

async function renderWhitelist() {
  const raw = await fetch(
    'https://raw.githubusercontent.com/996icu/996.ICU/master/whitelist/README.md'
  ).then(res => res.text());

  const html = marked(raw);
  document.getElementById('whitelist').innerHTML = html;
}

renderWhitelist();

This approach fetches the latest version of whitelist/README.md directly from the main branch, ensuring your application always displays the most current list of work-life-balanced employers.

Summary

• The 955.WLB whitelist tracks companies that follow a 9am-5pm, Monday-Friday schedule without overtime
• Community-driven submissions occur through GitHub Pull Requests with mandatory evidence attachments
• All data resides in whitelist/README.md with supporting images stored in whitelist/img/
• The system uses no automation or servers, relying purely on GitHub's version control and review features
• Content is instantly accessible via raw GitHub URLs for programmatic consumption

Frequently Asked Questions

What does "955" stand for in the whitelist project?

The term 955 refers to a work schedule of 9am to 5pm, 5 days per week (Monday through Friday), representing a standard 40-hour work week without overtime. This contrasts with the "996" schedule (9am-9pm, 6 days per week) that the parent 996.ICU campaign opposes.

How is the evidence verified before a company is added?

Project maintainers manually review each Pull Request to confirm that the evidence links to official company documentation or verifiable public sources. They check that the schedule description matches the provided proof and ensure that any sensitive personal information is redacted from screenshots before merging.

Can a company be removed from the 955.WLB whitelist?

Yes, companies can be removed or updated through the same Pull Request process used for additions. If a previously listed company changes its policies or new evidence contradicts its 955 status, community members can submit a PR to remove the entry or update the schedule description with current documentation.

Does the whitelist project use any automated testing or CI/CD?

No, the project intentionally avoids automation, build steps, or server-side processing. According to the repository structure, the whitelist relies solely on GitHub's native Markdown rendering and PR workflow, making the system transparent, portable, and instantly updatable upon merge without dependency on external services.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}