docs-arcbos-v2

ARCBOS Reference Web Repository

enxpower/docs-arcbos-v2 is the governed source repository for the public ARCBOS reference website:

• Public site: https://ref.arcbos.com
• Source repository: Private
• GitHub Pages: Public
• Pages source: main branch, repository root /
• Custom domain: ref.arcbos.com

This repository is active. It must not be archived, deleted, or treated as an obsolete document-output repository while ref.arcbos.com continues to serve ARCBOS public reference content.

Repository role

This repository owns public, intentionally published ARCBOS web surfaces that are not part of the governed Publisher V3 document lifecycle, including:

• ARCBOS visual identity and brand assets under /vi/;
• the public SnowBot product introduction under /snowbot/;
• investor teasers and business-plan presentations under routes such as /teaser/, /teaser-angel/, and /teaser-angel-v2/;
• approved project, partner, campaign, demonstration, and other standalone HTML pages;
• historical ARCBOS reference material that remains intentionally available on the public internet.

Representative routes include:

• https://ref.arcbos.com/vi/
• https://ref.arcbos.com/snowbot/
• https://ref.arcbos.com/teaser/
• https://ref.arcbos.com/teaser/bp/
• https://ref.arcbos.com/teaser-angel/
• https://ref.arcbos.com/teaser-angel/bp/
• https://ref.arcbos.com/teaser-angel-v2/

The route list is illustrative, not an authorization to publish unreviewed content.

Domain boundary

ARCBOS uses two separate public publishing surfaces:

Surface	Authority	Purpose
ref.arcbos.com	This repository	VI, product pages, BP/teaser pages, campaigns, selected public reference HTML
docs.arcbos.com	enxpower/notion-doc-publisher-v3	Governed Publisher V3 documents, canonical document routes, HTML and Phase 4 Typst PDF output

The two domains must not be merged implicitly. This repository must not publish or imitate the governed V3 document lifecycle, and Publisher V3 must not overwrite the standalone reference surfaces owned here.

Publisher V2 retirement

enxpower/notion-publisher-v2 has been decommissioned as a production publisher.

This repository must no longer receive automated output from Publisher V2. The following are prohibited unless the owner approves a new governed architecture through an explicit PR:

• scheduled legacy publishing;
• push-triggered legacy publishing;
• workflow_dispatch legacy production publishing;
• Notion metadata or lifecycle writeback from this repository;
• cross-repository deployment using legacy publishing PATs;
• destructive synchronization such as an external rsync --delete over the repository root.

Existing static content remains live and is maintained through reviewed repository changes.

Publishing model

The production model is intentionally simple:

1. approved changes are merged to main;
2. GitHub Pages publishes the repository root;
3. the root CNAME remains ref.arcbos.com;
4. HTTPS remains enforced;
5. representative public routes are verified after deployment.

No external publisher is authorized to own or replace the repository tree.

Public-content warning

A Private GitHub repository does not make its GitHub Pages site private.

Everything reachable through ref.arcbos.com must be treated as public internet content. Route names such as clients/, internal/, unlisted/, or private/, and metadata such as noindex, do not provide access control.

Do not publish:

• secrets, tokens, credentials, internal state, or private source material;
• confidential customer or partner information;
• restricted engineering records;
• unapproved financing, legal, personnel, or diligence material;
• content that depends on obscurity of the URL for protection.

Change requirements

Every substantive change must use a controlled branch and pull request. Before merge, verify:

• desktop, tablet, and mobile layouts;
• no horizontal page scrolling;
• navigation, buttons, language switches, anchors, and calls to action;
• canonical URL and social-preview metadata;
• PNG social preview compatibility where a page is intended for sharing;
• favicon and ARCBOS VI compliance;
• all local assets and public links;
• absence of credentials and unintended public information;
• representative production URLs after deployment.

Governance

All contributors and AI agents must read, in order:

1. AGENTS.md
2. docs/REFERENCE_SITE_GOVERNANCE.md
3. this README.md

The authoritative repository governance is docs/REFERENCE_SITE_GOVERNANCE.md.

Historical state

Legacy files and Git history may remain for audit and archaeology. Historical Publisher V2 state, including .publisher_state.json, does not authorize any current publishing workflow and must not be used to reactivate the retired system.