[chiibitsu]

What this does

Deletes two working documents from the repository root:

• chiibitsu-labs-about-page-claude-code-prompt.md (37 KB, 812 lines)
• compaction-chiibitsu-labs-canon-biz-reg-and-about-page-2026-07-13.md (47 KB, 1121 lines)

Vercel serves this repository root statically, so both have been fetchable over HTTPS at their filename paths for as long as they have been committed. Both declare visibility: internal in their own YAML frontmatter, and the prompt file also declares canonical_status: non-canon. Neither marker does anything — a static host does not read frontmatter.

Neither file is referenced by any page, script, or config. Nothing about the site changes.

Scope check — is anything else affected?

I scanned every file served from the root for visibility: internal, canonical_status: non-canon, confidential, internal only, and do not publish. These two files are the only marked ones.

Correction, after independent review: that scan was for markers, and it was complete on its own terms — but I drew the wrong conclusion from it. Marked files are not the same set as exposed files. Review found the entire apps/booking source tree and CLAUDE.md are also publicly served, carrying no marker at all. Confirmed live: GET https://www.chiibitsu.com/apps/booking/src/lib/admin-auth.ts → 200 with full source. See findings 1 and 2 below.

What each file contains, by category

Categorised without reproducing any of the sensitive content.

chiibitsu-labs-about-page-claude-code-prompt.md

Category	Present	Notes
Business registration details	⚠️ Narrative only	References the trade-name/sole-proprietor arrangement in passing. No registration numbers, TIN, certificate numbers, addresses, or phone numbers.
Client names	⚠️ Yes	Engagement descriptions naming sectors and at least one named venture, in a franker form than the anonymised case studies published on /.
Pricing	✅ No	No rates, fees, or commercial terms.
Canon drafts	⚠️ Yes	Explicitly marked non-canon; superseded framings of company architecture and positioning.
Working notes	⚠️ Yes — bulk of file	An execution prompt for generating the About page, plus a changelog.

compaction-chiibitsu-labs-canon-biz-reg-and-about-page-2026-07-13.md

24 numbered sections. The more significant of the two.

Category	Present	Notes
Business registration details	⚠️ Yes, narrative	§07 on founder legal identity — legal vs. professional vs. artist names, legal structure, a structure guardrail, exact disclosure wording. §19 covers financial-platform and business verification context, naming the platform. No account numbers, ID numbers, addresses, or phone numbers anywhere in the file — checked explicitly.
Client names	⚠️ Yes	Multiple FOUNDER RAW first-person accounts of specific engagements, including a named venture. §15 is the sharpest: each raw account is paired with a separate "Public-safe direction" — the document itself marks the raw versions as not safe to publish, and both versions are published.
Pricing	✅ Essentially none	One line touching commercial framing.
Canon drafts	⚠️ Yes — bulk of file	Company and offer architecture, brand promise, internal vs. external meaning of the promise, an unresolved naming conflict. Tagged by authority (FINALIZED / FOUNDER RAW / VAULT EVIDENCE / SYNTHESIS / OPEN / VERIFY).
Working notes	⚠️ Yes	Reasoning lineage, read-order instructions for an AI, anti-drift rules, and a proof bank (§20) recording which claims are vault-supported and which still need source reconciliation before public use.

Assessment: the two things a reader gets that Chii would not have chosen to give them are (a) unguarded first-person accounts of named client work that the document itself flags as needing a public-safe rewrite, and (b) an internal map of which public claims are not yet evidence-backed.

For the history-rewrite decision

Deleting these files does not un-publish them. The repository is public, so the content remains readable at commit-level URLs, in forks, in clones, and in anything that already crawled them. This PR deliberately does not rewrite history and does not force-push — that is Chii's call to make with full information, not a side effect of a cleanup PR.

For a rewrite: §15's raw-vs-public-safe pairing is an explicit internal acknowledgement that some content was not fit to publish. §20 documents which public claims lack verified sourcing — materially worse in a competitor's or journalist's hands than a customer's. §07 and §19 concern legal and financial identity.

Against, or for lower urgency: there is no directly actionable data — no ID numbers, registration or certificate numbers, bank or account numbers, home address, phone number, credentials, or secrets. Checked for each specifically. The bulk of both files is positioning and process. A rewrite on a public repo is also incomplete by nature: forks, existing clones, and archive caches survive it.

Nothing needs rotating — no secrets are involved. Merging this PR first is compatible with either decision.

Vault status (done outside this repo)

Both files already existed in the Aikiri Garden vault at 03_human/builder-os/Chiibitsu-labs/ — the copies here were duplicates from a 2026-07-13 web-UI upload, not originals. The prompt document has since been archived there (v2.0.0, 2026-08-31) with a banner, body preserved verbatim. The compaction was left active as a provenance record. Reasoning in 00_inbox/2026-08-30-website-repo-internal-notes-staleness-triage.md.

Verification

• git status clean apart from the two deletions; no other files touched.
• Neither filename appears in any HTML, config, or workflow (grep across the repo).
• CI (.github/workflows/ci.yml) only builds apps/booking and is unaffected.
• No history rewrite, no force-push. Branch is a normal commit on top of main.

---

Local review gate — SATISFIED

Per AGENTS.md v3.0.0: independent Claude review, then Gemini, both pasted verbatim, then Chii flips to ready. Both stages have now run against head 485714d. No code changed between them, so both reviews cover the same commit.

Stage 1 — independent Claude review (verbatim)

Fresh-context review by a Claude that did not write this change. Reproduced verbatim, unedited:

---

Independent Claude review — PR #32 (head 485714d)

Verdict

FINDINGS — 3 items (none block this diff; two are scope/completeness gaps in the stated goal)

Claims verified

• "Deletes two markdown working documents from the repository root" — CONFIRMED. git diff main...485714d --numstat returns exactly two paths, 0 812 and 0 1121, both D in --name-status. Zero added lines (git diff … | grep -c "^+[^+]" → 0). Nothing else in the tree is touched. Branch is based directly on current main (git merge-base = 08b7c96 = main), so no stale base.
• "Publicly fetchable because Vercel serves the repo root statically" — CONFIRMED empirically. Vercel project website (prj_CobI9TNkn7EAUH1bJdSp4V1zaEi2, domains www.chiibitsu.com / chiibitsu.com) has framework: null and no build step, so the repo root is the static output. GET https://website-git-main-…vercel.app/chiibitsu-labs-about-page-claude-code-prompt.md returns 200, content-type: text/markdown, with the full document body. Direct curl from this session is blocked by proxy policy (CONNECT … 403), so the fetches were done through the Vercel API.
• "Neither file is referenced anywhere in the repo" — CONFIRMED. git grep for both basenames across main returns hits only inside the two files themselves (they cross-reference each other in front-matter, lines 24 and 58 of the prompt doc; lines 15 and 98 of the compaction doc). Since both are removed in the same commit, no dangling reference remains. git grep -E "\.md\b" over *.html *.json *.yml *.ts *.tsx *.mjs returns nothing. vercel.json contains only the /chii → /angeline redirect and does not mention either file.
• "Nothing about the site changes" — CONFIRMED with one literal caveat: no page, asset, route, redirect, or metadata changes; but the two URLs themselves go from 200 to 404. There is no robots.txt or sitemap.xml in the repo, and nothing linked to them, so no crawl or link breakage.
• Justification on the merits (not asserted in the PR body, checked anyway) — the deleted files do carry visibility: internal, canonical_status: non-canon, internal vault paths (builder-os/…), and unverified founder-supplied metrics the documents themselves flag as needing confirmation before publication. Removing them from the web root is warranted.

Findings

1. HIGH — completeness: the entire apps/booking Next.js source tree is served publicly from the marketing site. Same root cause as this PR, much larger blast radius.

   • https://www.chiibitsu.com/apps/booking/src/lib/db.ts → 200, full source (Supabase table names, column schema, service-role env var names).
   • https://www.chiibitsu.com/apps/booking/README.md → 200, the complete operator setup guide: the /admin route, the admin auth model, every env var name (ADMIN_PASSWORD, BOOKING_TOKEN_SECRET, TALLY_SIGNING_SECRET, GOOGLE_REFRESH_TOKEN), and deploy/DNS specifics.
   • apps/booking/src/lib/admin-auth.ts discloses the header-based scheme (x-admin-password, x-admin-email), and every route under src/app/api/ is likewise readable.
   • Mitigating: I found no hardcoded credentials. apps/booking/.env.example contains placeholder keys only, and a repo-wide grep for assigned secret literals returns nothing. So this is attack-surface and design disclosure, not a credential leak.
   • What I would change: fix this structurally rather than file-by-file — add a .vercelignore (or set the website project's Root Directory / an explicit vercel.json output) so only index.html, about/, angeline/, angeline.pdf, and lead-magnets/ are deployed. That approach would also have covered the two files in this PR, and prevents the next working doc dropped at the root from re-creating the problem.

2. MEDIUM — completeness: CLAUDE.md is still served publicly and is the same class of content. https://www.chiibitsu.com/CLAUDE.md → 200, text/markdown, returning the full internal review-gate policy, the reviewer-substitution rule, the reference to unattended-self-merge conditions, and the vault path 01_wiki/kb/decisions.md. This is internal process documentation sitting at the web root, unaddressed by a PR whose stated purpose is removing internal notes from the web root. Covered by the .vercelignore fix in finding 1; if that is deferred, CLAUDE.md should be excluded now.

3. LOW — the PR body's implied outcome overstates what deletion achieves. Chiibitsu-Labs/website is a public GitHub repository (visibility: "public"), and the deleted blobs remain in history — both files are still readable by anyone at github.com/Chiibitsu-Labs/website/blob/08b7c96/…. This PR closes the chiibitsu.com serving path only. If the content is considered genuinely sensitive, history rewrite or repo visibility is the actual remedy and should be tracked separately; if it is merely untidy, the PR description should not read as though the material is now non-public. (Related: the repo has has_pages: true, a second potential serving surface worth confirming.)

Notes

• Risk to the deployed site: none identified. vercel.json is untouched, so the /chii → /angeline 301 is unaffected. vercel.json itself is not served (404 — Vercel excludes it). No HTML, CSS, image, or PDF asset is touched.
• Risk to CI: none. .github/workflows/ci.yml runs only in apps/booking (typecheck, lint, build) and never reads repo-root markdown.
• Risk to the Vercel builds: none. Three Vercel projects build from this repo — website (static, repo root), chiibitsu-booking (Next.js, book.chiibitsu.com), and lm-booking-site. None consume root markdown; the static project has no build step to break.
• Findings 1 and 2 are pre-existing conditions, not regressions introduced here. This diff is a clean, correctly-scoped, pure deletion and is safe to merge on its own; I would open a follow-up for the .vercelignore fix, which is arguably more urgent than the issue this PR resolves.

---

Stage 2 — Gemini cross-vendor review (verbatim)

Model: gemini-3.7-flash. Given the diff, the repo tree, the configs, this PR's claims, and stage 1's findings with my dispositions, and asked to challenge both. Reproduced verbatim, unedited:

---

Cross-vendor review (Gemini) — PR #32 (head 485714d)

Verdict

CLEAN — no blocking findings on this PR.

Assessment of the change

• Diff purity: The diff is strictly a pure deletion of two root markdown files (chiibitsu-labs-about-page-claude-code-prompt.md and compaction-chiibitsu-labs-canon-biz-reg-and-about-page-2026-07-13.md). No other files were touched.
• Reference check: Neither file is imported or referenced by index.html, about/index.html, angeline/index.html, vercel.json, or the Next.js booking app under apps/booking.
• Blast radius: Zero impact on CI (which only targets apps/booking), static site routing, or runtime behavior. Removing these stops the Vercel marketing deployment from serving these prompt/compaction docs at their root URIs.

Assessment of the prior review and the author's dispositions

• F1 & F2 (Source leak & internal docs exposure): Splitting this into PR DO NOT MERGE — .vercelignore approach breaks book.chiibitsu.com (finding kept for the record) #33 via .vercelignore is the correct decision. PR Remove internal working notes from the public web root #32 is an immediate content cleanup; changing Vercel build/ignore rules has distinct deployment side effects and belongs in its own atomic PR.
• F3 (Publicity / git history status): The author's position is fair. Git history retention in a public repository is standard unless the owner explicitly undertakes git history rewriting (e.g., git-filter-repo / BFG). Deleting files from HEAD eliminates direct web scraping against predictable root URLs.

Findings

None.

Notes

• GitHub Pages check: If GitHub Pages is active on this repo (has_pages: true via GitHub API or repo settings) serving the main branch root, note that .vercelignore in PR DO NOT MERGE — .vercelignore approach breaks book.chiibitsu.com (finding kept for the record) #33 will not prevent GitHub Pages from continuing to publish whatever remains in main. Ensure Pages is disabled or rooted only to a designated publish directory if static serving is intended solely through Vercel.
• Additional root assets: Ensure PR DO NOT MERGE — .vercelignore approach breaks book.chiibitsu.com (finding kept for the record) #33 covers .github/ and other dotfiles if the root directory remains the static deploy source for the marketing site.

---

Author response to findings

Stage 1, finding 1 (HIGH) — accepted, not fixed here. Correct, and more urgent than the issue this PR addresses. Deliberately not folded into this diff: a deploy-config change is a different risk class from deleting two unreferenced markdown files. Gemini independently agreed the split is right. Tracked separately.

Stage 1, finding 2 (MEDIUM) — accepted, same disposition.

Stage 1, finding 3 (LOW) — partially disputed. The body has carried a "For the history-rewrite decision" section from the first push, stating in bold that deletion does not un-publish. Gemini assessed the dispute as fair. Accepted sub-point: has_pages: true is a second serving surface, still to be confirmed.

Both reviewers' has_pages note — open. If GitHub Pages serves main, it is a serving path that no Vercel-side fix touches. Flagged for Chii; not actionable from a PR.

Important, on the follow-up: the .vercelignore approach that both stage-1 finding 1 and Gemini's notes point toward was tried in #33 and is wrong — a repo-root .vercelignore is shared by all three Vercel projects and empties the production booking app. See #33 for the evidence. Neither reviewer had that information when writing; it does not affect this PR, which stands on its own.

Gate status

Both stages are complete against 485714d with no blocking findings, so the local requirement is satisfied and this PR is waiting on Chii. Per AGENTS.md v3.0.0 the flip to ready is hers, never the agent's, and I have not requested the finisher.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
website	Ready	Preview	Aug 30, 2026 7:27am