wedgewoodai.com — Design Document

1. Summary

wedgewoodai.com is the company website for WedgewoodAI Tapui Limited, a family software company on the Kāpiti Coast, New Zealand. It presents the company's products (AuraShop, CaddieChat, AuraKin AI, AuraBiz AI, WedgewoodAI Indoor Golf and Footprints & Folios), the family story, how the team builds with AI, and the Tech Initiatives programme — including the AuraShop migration to Azure, with its Timeline, Design proposal and Migration strategy pages, deployment journal and decision log. The site also hosts a small storefront (Shop), a customer product area (MyProducts), the WedgewoodAI Builders community at /community, and a contact channel. Wedge, an AI advisor, is live. It solves the problem of showing, in one honest and transparent place, what the family builds and how it builds it, while giving customers a way to buy and manage products and giving builders a place to talk.

2. Users and main uses

The site serves visitors interested in the company and its products, prospective and existing customers, members of the WedgewoodAI Builders community, and the company's own administrators.

The most important things people do:

1. Read about the products and open each product page to understand what it does and its status.
2. Follow the Tech Initiatives programme — the AuraShop-to-Azure migration, its Timeline, Design proposal and Migration strategy pages, execution tracker, deployment journal and decision log.
3. Learn the family story and the "How We Build" approach to AI-assisted development.
4. Buy a product through the Shop and then sign in to MyProducts to view purchases, subscriptions and memberships.
5. Join and read the WedgewoodAI Builders community at /community (invite only, read-only for Members at launch).
6. Send an enquiry through the Contact form.

3. Features

4. Architecture

The site is a single web application built with a modern React framework running as a standalone server. The front end and back end live in the same application; the back end is a set of server API routes. Data is held in managed PostgreSQL databases. The site's only runtime AI feature is Wedge, the AI advisor, which calls the Anthropic Claude API server-side; the site does not call an AI model to generate its other content.

graph TD
  Visitor["Visitor / Customer / Community member browser"] -->|HTTPS| App["wedgewoodai.com web app"]
  App --> Pages["Marketing + content pages"]
  App --> API["Server API routes"]
  App --> Community["Community"]
  API --> DB[("Managed PostgreSQL databases")]
  API --> Email["Notification email service"]
  API --> Claude["Anthropic Claude API — Claude Haiku 4.5 (Wedge)"]
  API --> Stripe["Stripe (hosted checkout + webhook)"]
  API --> GoogleAuth["Google Sign-In"]
  API --> Turnstile["Bot protection"]
  Visitor --> SW["Service worker + PWA manifest (offline + installable)"]

• Front end: Server-rendered and client React pages. Marketing and programme content is held within the application.
• Back end: Server API routes handle the contact form, the Shop, MyProducts sign-in, the community and the admin console.
• Data store: Managed PostgreSQL databases for accounts, products and orders, the community, configuration and logs.
• AI services: Wedge, the AI advisor, calls the Anthropic Claude API (Claude Haiku 4.5) server-side to answer visitor questions from the public pages. No AI model generates the rest of the site content, and a notification service sends transactional email.
• External services: Stripe for payments, Google for optional sign-in, a bot-protection service, and a notification email service. Anthropic's Claude API (Claude Haiku 4.5) powers Wedge.

5. How a request flows

The most representative action that exercises the back end is sending a Contact enquiry.

sequenceDiagram
  participant V as Visitor
  participant W as wedgewoodai.com (web app)
  participant A as Contact API route
  participant E as Email service
  participant R as Recipient (company inbox)
  V->>W: Open Contact page, fill in name, email, subject, message
  V->>W: Submit form
  W->>A: POST enquiry
  A->>A: Sanitise and validate input, apply spam protection
  A->>E: Send notification email (reply-to = sender)
  E->>R: Deliver enquiry to company inbox
  A-->>W: Success response
  W-->>V: Confirmation message

The form requires no sign-in. The server cleans and validates the input and applies spam protection. The enquiry is saved securely and delivered to a company inbox with the sender set as reply-to.

6. Data

Data is held in managed PostgreSQL databases. Passwords are stored only as salted hashes; no plain-text passwords are kept.

7. AI use at runtime

Wedge, the AI advisor, is the only AI feature called at runtime. The rest of the site's features are ordinary application logic, and the notification email service is not a generative-AI feature.

Wedge is live. It answers visitor questions about WedgewoodAI from the public pages, with links, and answers general technical questions labelled as general guidance. Wedge uses Claude Haiku 4.5 via the Anthropic API, called server-side only; it allows up to 10 questions per visit with a bot check; and it keeps questions and answers for 30 days (with hashed IPs) before deleting them. Question text is sent to Anthropic, in the USA, to generate each answer. Wedge answers only from published, public material, says when it does not know rather than inventing answers, and never exposes private information. A second advisor, Winona, is planned to cover questions about products and the community.

8. How AI was used to build it

The site was built with Abacus.AI agents in an AI-assisted workflow, directed by the founder.

• What the agents did: Generated and edited the application — the pages and components, the server routes (contact, shop, MyProducts, community, admin), the data model, the styling, the installable PWA and offline support, the social/SEO metadata, and the Tech Initiatives content (Timeline, Design and Strategy pages, execution tracker, deployment journal and decision log). The agents also ran build and type checks and fixed errors.
• What the founder designed or decided: The product line-up and how each is described and staged; the family story and tone; the decision to run a public, transparent Tech Initiatives programme; the AuraShop-to-Azure migration plan; the WedgewoodAI Builders community and its rules; the brand; and the policy of only claiming what actually exists.
• What was checked by hand: The founder reviews content, product statuses and programme wording for accuracy; reported issues are reproduced and fixes confirmed before release.

This AI-assisted approach is described on the "How We Build" page.

9. Identity and access

There are four kinds of access:

• Visitors: No sign-in. They browse content, use the Contact form and start a Shop purchase.
• Customers (MyProducts): Sign in to view their products, subscriptions and memberships, by email and password or with Google Sign-In, protected by a bot check. Sessions use a signed, secure cookie.
• Community members (WedgewoodAI Builders): A separate account and sign-in from MyProducts; the community never shows purchases. Members join by invite code (16+), accept the Code of conduct and Terms, and verify their email. Roles are Visitor, Member, Contributor, Moderator, Core team and Owner, with increasing abilities from reading only to posting, moderating and running the community. At launch the community is read-only for Members.
• Administrators: A private console for managing orders, product users and settings, protected by two-factor authentication.

10. Integrations

11. Hosting and deployment

The site runs on a managed cloud platform as a standalone web application with managed PostgreSQL databases, served on the company domain. Changes are made in an AI-assisted workflow, reviewed in a preview, and then released by deploying to the live domain, which refreshes the published site within a few minutes. Backups are handled by the managed database service.

12. Security and privacy

• All traffic is over HTTPS.
• Passwords are stored only as salted hashes, never in plain text, and are checked against known-breach lists.
• Two-factor authentication protects administrators and community moderators.
• Posts in the community are scanned for anything that looks like a secret, and content is cleaned before it is shown.
• Bot protection and input cleaning guard the sign-in, community and contact features.
• Payments are handled by Stripe's hosted checkout; the site does not store card numbers.
• Wedge (our AI advisor) sends your question to Anthropic's Claude API, which is hosted in the USA, to generate its answer. Questions and answers are kept for 30 days and then deleted, and IP addresses are stored only as a hash.

In line with the New Zealand Privacy Act 2020, the site collects only the personal information it needs, uses it only to provide products, run the community and respond to enquiries, and protects it with the measures above. Our privacy statement explains what we collect and why, and the community has its own privacy notice, a data-download option and account deletion with a "Former member" option.

13. Quality and operations

Quality is maintained through automated build and type checks on every change, with reported issues reproduced and verified before release. Support is by email through the Contact form. Where a feature cannot complete, the site fails gracefully — for example, the installable app shows an offline page when there is no connection.

14. Known limitations

• The WedgewoodAI Builders community is read-only for Members at launch.
• Some product pages present beta or in-development products; statuses are kept up to date as they change.

15. Portability

Not applicable (internal version only).

16. Roadmap

• WedgewoodAI Builders community Phase B — Members' and Core team libraries, and "Sign in with LinkedIn" later (planned).
• Community private test and soft launch — after 7 October 2026 (planned).
• Winona — a second advisor for products and the community (planned).
• AuraShop-to-Azure migration — continue the programme, with the main migration work targeted for November 2026; keep its deployment journal and decision log updated.

No fixed dates are confirmed except the migration programme's own published target windows.

17. Decisions

• Build with Abacus.AI agents in an AI-assisted workflow — to let a small family team ship quickly.
• One combined web app (front end + server routes) — simplest to build and run.
• Managed PostgreSQL databases — reliable, standard data storage.
• Keep the community account and sign-in separate from MyProducts — different purpose, and the community never shows purchases.
• Stripe hosted checkout — avoid handling card data directly.
• Two-factor authentication for administrators and community moderators — protect privileged areas.
• Spam protection on Contact, and saving enquiries as well as emailing them — reduce abuse and keep a record.
• Progressive web app with offline fallback — installable and resilient on any device.
• Publish a public design document and a transparent Tech Initiatives programme — "show our work".
• Only claim what exists; mark the rest as planned — accuracy for the knowledge base.

18. Questions and answers

Can I install the WedgewoodAI site on my phone? Yes. It is a progressive web app, so you can add it to your home screen from your browser and it will open like an app, with an offline page if you lose connection.

How often is the deployment journal updated? It is updated as milestones happen in the AuraShop-to-Azure migration; new entries appear newest-first on the migration page and on the Timeline.

What products does the WedgewoodAI website present? AuraShop, CaddieChat, AuraKin AI, AuraBiz AI, WedgewoodAI Indoor Golf and Footprints & Folios. Each has its own page or card; some are live, some are in beta and some are in development.

Do I need an account to browse the site? No. You only sign in if you buy something and want to manage it in MyProducts, or if you join the WedgewoodAI Builders community.

How do I buy something on the site? Through the Shop, which uses Stripe's secure hosted checkout for one-off and subscription purchases in New Zealand dollars.

Does the shop store my card details? No. Payments go through Stripe's hosted checkout; the website never sees or stores your card number.

How do I sign in to MyProducts? With your email and password, or with Google Sign-In. A quick bot check protects the sign-in.

How do I join the WedgewoodAI Builders community? The community is invite only at launch. With an invite code you can sign up (you need to be 16 or over), accept the Code of conduct and Terms, and verify your email address. After that you can read the community.

Why can't I post yet? At launch the community is read-only for Members. Posting opens as the community grows; your first two posts are checked before they appear.

Is my shop account the same as my community account? No. The community has its own account and sign-in, separate from MyProducts, and it never shows your purchases.

How do I reset my community password? Use "Forgot password" on the community sign-in page. We email you a reset link; new passwords are checked against known-breach lists. You can also change your password while signed in.

How do I delete my community account? You can delete your account from your community settings. You can choose a "Former member" option so your past posts show as from a former member rather than being removed.

Will the website answer my questions with AI? Yes — ask Wedge, our on-site AI advisor. Wedge answers your questions about WedgewoodAI from our public pages, with links, and labels general technical answers as general guidance. Wedge uses Claude Haiku 4.5 via the Anthropic API (server-side only), allows up to 10 questions per visit with a bot check, and keeps questions for 30 days with hashed IPs. A second advisor, Winona, is planned for products and the community.

How is my personal information handled? Only what is needed is collected, it is used only to provide products, run the community and answer enquiries, and it is protected in line with the New Zealand Privacy Act 2020. See the Privacy page.

Where is WedgewoodAI based? It is a family company on the Kāpiti Coast, New Zealand.

How was the website built? With Abacus.AI agents in an AI-assisted workflow, directed and reviewed by the founder — described on the "How We Build" page.

What is the Tech Initiatives programme? A transparent record of the company's technical work, currently the AuraShop migration to Microsoft Azure, with a Timeline, Design proposal and Migration strategy pages, a live execution tracker, deployment journal and decision log.

19. Glossary

• AuraShop — WedgewoodAI's shopping product; also the application being migrated to Azure under the Tech Initiatives programme.
• CaddieChat — WedgewoodAI's golf assistant product.
• AuraKin AI — a WedgewoodAI product (in beta).
• AuraBiz AI — a WedgewoodAI product (in development).
• WedgewoodAI Indoor Golf — a WedgewoodAI product: a virtual golf club concept built around indoor golf simulators (in development).
• Footprints & Folios — a WedgewoodAI product.
• MyProducts — the signed-in customer area for viewing products, subscriptions and memberships.
• WedgewoodAI Builders — the company's discussion community at /community for people building with AI; invite only at launch.
• Core team — the community role and space for the company's own team.
• Contributor — the community role that can post and reply.
• Moderator — the community role that can moderate posts and members.
• Invite code — a code that lets a new person sign up to the community while it is invite only.
• Wedge — the on-site AI advisor that answers from the public pages, with links; uses Claude Haiku 4.5 (Anthropic) server-side, with a 10-questions-per-visit limit and a bot check.
• PWA (Progressive Web App) — a website that can be installed to a device home screen and works partly offline.
• Service worker — the background script that enables offline support and caching.
• Stripe — the payment provider used for checkout.
• Two-factor authentication — a one-time passcode in addition to a password, used for admin and community Owner/Moderator sign-in.
• Social preview card — the image and text shown when a page is shared on social media.
• Deployment journal / decision log — the running records of migration milestones and the reasons behind key choices.

20. Content and publishing

Not applicable (internal version only).

21. Readiness for Wedge, the AI advisor

Not applicable (internal version only).