Repository navigation
Conversation
Covers all three references on /angeline: the 'Built for you' now-card, the offer heading, and the mailto subject behind 'See if your business is a fit', so a reply lands under the new name rather than the old one. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RWBnyhXBy3VWtH2rRYtyjk
Blueprint is the entry and Build is the build work, formerly the AI Incorporation Sprint. They were one card whose body carried both, with Blueprint doubling as its cheapest tier, so renaming the card alone would have labelled the build work Blueprint and left a tier of the same name inside it. Blueprint now carries the only Book button on the page, pointing at book.chiibitsu.com/blueprint. Build keeps the Foundation and Full System scopes and the mailto; no third scope is named, since those names are still being settled. The section heading goes from three ways in to four, and the 'Built for you' card covers both. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RWBnyhXBy3VWtH2rRYtyjk
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
chiibitsu
changed the title
…ials Everything is Chiibitsu Labs now, so the sub-brand goes. The two AI @ Work booking projects carried 'Futureproof' as their company, which is what the booking page header and every confirmation email and calendar invite print; the seed config and the admin Company placeholder said the same. The 'Built & authored' chip on /angeline is removed rather than renamed, since the other chips are products and Chiibitsu Labs is the company. The live rows were updated in Supabase to match, so the two surfaces agree. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RWBnyhXBy3VWtH2rRYtyjk
The AICOS fit call still carried 'Lighthouse'. Every project is Chiibitsu Labs now, so a project-specific brand in the company field would print the wrong name on the booking page header, the confirmation email and the calendar invite if that seed were ever used. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RWBnyhXBy3VWtH2rRYtyjk
Everything is Chiibitsu Labs, so the platform layer goes. Homepage: the 'What we do' intro no longer routes every area of work through Futureproof, and the Futureproof service card is deleted with AICOS and Chibie renumbered to 04 and 05 behind it. Deleting that card also drops the only link to futureproof.chiibitsu.com anywhere on the site, so the subdomain is now unreferenced. About: the section was framed as the Futureproof architecture with AI @ Work and Lighthouse tagged 'Futureproof Work'. The cards are the real content and they stay; only the framing changes. The heading becomes how the work fits together, the lead keeps the waves-of-change idea without the brand, and the two tags become 'Organizational systems' to match the 'Public learning' and 'Experimentation' tags beside them. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RWBnyhXBy3VWtH2rRYtyjk
chiibitsu
changed the title
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3fd23fa590
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| <p class="offer-body">One day together to map how AI actually fits your business, then I build it. Three levels: <strong>Blueprint</strong>, all three phases mapped for your team to build. <strong>Foundation</strong>, I build phase one. <strong>Full System</strong>, I build all three. Everything runs in your own accounts, so it stays yours.</p> | ||
| <p class="offer-body">The way in. Two weeks of preparation on your own numbers and workflows, then one day together to agree what to build and in what order.</p> | ||
| <p class="offer-leave"><strong>You leave with:</strong> the written plan, within two working days.</p> | ||
| <p class="offer-cta"><a href="https://book.chiibitsu.com/blueprint">Book your Blueprint →</a></p> |
There was a problem hiding this comment.
The booking app is deployed and consistently configured at booking.chiibitsu.com (apps/booking/.env.example, src/app/layout.tsx, and the admin URL hint), but this CTA sends prospective customers to book.chiibitsu.com. Unless an undocumented alias exists, clicking the page's only Book button will miss the new /blueprint booking route; use the configured https://booking.chiibitsu.com/blueprint host.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
The CTA is right and the stale defaults were wrong. The booking host moved from booking.chiibitsu.com to book.chiibitsu.com. The owner confirmed this directly, and lead-magnets/booking-site/index.html already links to book.chiibitsu.com in two places.
You found a real inconsistency, though. The booking app still carried the old host in five places: the metadataBase fallback in layout.tsx, the SSR fallback for the Google OAuth callback in AdminDashboard.tsx, the slug hint in ProjectEditor.tsx, and the README and .env.example. Those are fixed in 4c9569f. They are string changes only, and no booking.chiibitsu.com reference remains in the repo. The CTA is unchanged.
Generated by Claude Code
The booking host moved from booking. to book. but the app still carried the old name in five places: the metadataBase fallback, the server-render fallback for the Google OAuth callback shown in Setup, the URL hint under the slug field in the project editor, and the README and .env.example that tell a deployer what to set NEXT_PUBLIC_BASE_URL to. Most are fallbacks the browser path never reaches, but the slug hint printed the wrong address while naming a new project, and a deploy copied from the example would send confirmation and reschedule links to the wrong host. This is also what led a review to read the /angeline Book button, which correctly uses book., as the mistake. Strings only; no logic changed. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RWBnyhXBy3VWtH2rRYtyjk
|
@codex review Generated by Claude Code |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4c9569f0a1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| **Add the subdomain:** | ||
| - In DigitalOcean App settings, add the domain `booking.chiibitsu.com` | ||
| - In DigitalOcean App settings, add the domain `book.chiibitsu.com` |
There was a problem hiding this comment.
When a deployer follows this renamed-domain setup, the next instruction still creates a booking CNAME rather than book. That leaves book.chiibitsu.com without the DNS record needed to reach the DigitalOcean app, despite configuring that hostname in App Platform; update the record label on the following line to book.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Confirmed, and my own miss. The previous commit changed the domain on the line above but left the record label, so the steps would have registered one hostname and pointed a different one at the app. The label is now book in f76b5ea.
Generated by Claude Code
| <p class="offer-body">One day together to map how AI actually fits your business, then I build it. Three levels: <strong>Blueprint</strong>, all three phases mapped for your team to build. <strong>Foundation</strong>, I build phase one. <strong>Full System</strong>, I build all three. Everything runs in your own accounts, so it stays yours.</p> | ||
| <p class="offer-body">The way in. Two weeks of preparation on your own numbers and workflows, then one day together to agree what to build and in what order.</p> | ||
| <p class="offer-leave"><strong>You leave with:</strong> the written plan, within two working days.</p> | ||
| <p class="offer-cta"><a href="https://book.chiibitsu.com/blueprint">Book your Blueprint →</a></p> |
There was a problem hiding this comment.
When the booking service runs without Supabase or a Supabase lookup fails, getProjectBySlug() falls back to SEED_PROJECTS, which contains no blueprint entry, so this new CTA lands on the booking app's 404 page. The production row may have been changed out of band, but local, fresh, and fallback deployments remain unable to serve the advertised route; add Blueprint to the seed configuration or ship the database change with the repository.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Not changing this one, for two reasons.
SEED_PROJECTSis not a mirror of the live catalogue. It holds two projects (ai-at-work,aicos-fit-call), while the production table also haswork-with-chiiandaiatwork-1on1, which are linked and bookable and also have no seed entry. Addingblueprintalone would make the seed inconsistent in a new way. Mirroring all of them would put pricing, duration and copy in two places that then have to be kept in step.- The seed fallback only applies when Supabase is not configured or unreachable, and in that state the booking app has no calendar, no admin and no approval flow either. Production has the
blueprintrow, which was changed through the database as noted in the PR description. A fresh deploy gets its projects from the admin seeding step, not from this constant.
Under the repo's blocking bar this is an observation: it doesn't lead to a harmful action, doesn't contradict itself, and doesn't make anything unexecutable. If the intent is for the repo to carry the booking catalogue, that is a real design change and should be its own PR.
Generated by Claude Code
There was a problem hiding this comment.
Correction to the second point above: I wrote that without Supabase the app has "no calendar, no admin and no approval flow". Only the admin project list needs the database. Calendar availability uses Google credentials and the Telegram approval step reads its slug from the signed token, so both work without Supabase, and the seed fallback does serve the two seed projects in that state. The first point and the conclusion are unchanged: the seed is not a mirror of the live catalogue, and carrying the catalogue in the repo would be its own change.
Generated by Claude Code
The previous commit moved the domain in the deploy instructions from booking. to book. but left the DNS record on the next line as 'booking', so following the steps registered one hostname and pointed a different one at the app. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RWBnyhXBy3VWtH2rRYtyjk
|
@codex review Generated by Claude Code |
|
Codex Review: Didn't find any major issues. Nice work! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Two changes to the site, both following the Seasoning Table (
00_inbox/2026-10-14-seasoning-table.svg, priced 16 Oct): the business offer on/angelineis split into Blueprint and Build, and the Futureproof brand is removed from the site.1. Blueprint and Build on
/angelineThe AI Incorporation Sprint card carried two products in one body — "One day together to map how AI fits your business, then I build it. Three levels: Blueprint… Foundation… Full System" — with Blueprint doubling as its cheapest tier. A plain rename would have labelled the build work "Blueprint" and left a tier of the same name inside it. The Seasoning Table has them as separate products, with Blueprint crediting into the Sprint.
book.chiibitsu.com/blueprint.2. Futureproof removed
futureproof.chiibitsu.comfrom the site, so that subdomain is now unreferenced.companyvalues (Futureproof,Lighthouse) becomeChiibitsu Labs, and the admin Company placeholder follows.companyis what the booking page header, confirmation emails and calendar invites print./angeline— the Futureproof chip under "Built & authored" is removed.Applied directly to the database (not in this diff)
On Supabase project
chiibitsu-labs,booking_projects:inc-sprint→blueprint, name →Blueprint, emoji 🏃🏻♂️ → 📐company→Chiibitsu Labson all four projectsThe only booking
inc-sprintever had (Amplifi, July) is already past, so no live reschedule link broke.Known and left alone
location_typeon the Blueprint project is stillin_person. The Blueprint spec has an online mode too, but the live app only supports one or the other until feat(booking): manual bookings from admin, booker-chosen location, timezone-correct times #30 merges.chiibitsu-labs-about-page-claude-code-prompt.md, the July compaction record) still mention Futureproof; they are records of past sessions, not site content.🤖 Generated with Claude Code
https://claude.ai/code/session_01RWBnyhXBy3VWtH2rRYtyjk