Base2026 welcomes focused contributions to its public-safe code, product UI, search, data contracts, source-quality checks, accessibility, documentation and creator correction/removal workflows.
Read:
AGENTS.mddocs/project-memory/PUBLICATION_BOUNDARY.mddocs/GIT_PUBLICATION_AUDIT.mdSECURITY.mdROADMAP.mddocs/project-memory/VISUAL_SYSTEM_CONTRACT.md
For a substantial change, open an issue describing the user problem, affected data/rights boundary and how success will be verified.
Do not add private research, raw captions, raw ASR, media, generated exports, local databases, logs, cookies, tokens, keys, credentials or deployment archives.
public-data/, output/, local D1 state, Wrangler state and node_modules/ are generated or local artifacts—not repository source.
Do not submit confidential material through GitHub issues or the live Support/Partner forms.
Run the smallest relevant checks. For startup release or Worker changes, use:
python3 -m pytest tests/test_build_base2026_cloudflare_release.py -q
python3 -m pytest tests/test_base2026_design_authority.py -q
python3 scripts/check-base2026-design-authority.py
python3 scripts/audit-publication-boundary.py
cd cloudflare/base2026-worker
npm ci
npm run typecheck
npm test
npm run import:dry-run
npm run wrangler:dry-runFor UI changes, verify representative desktop and mobile viewports, keyboard behavior, horizontal overflow and the browser console.
Do not introduce a second design authority. Historical Alex V4, WordPress,
Stitch, Search V1 and Source Detail V2 assets are compatibility/history only;
the current Cloudflare release must use the b26-independent-v1 templates and
builder described in the visual-system contract.
- explain the user-facing outcome;
- list exact verification commands and results;
- call out public/private data or creator-rights risk;
- keep changes focused and reviewable;
- update docs when architecture, behavior or boundaries change;
- never include generated release trees or unrelated local changes.