KAPT Digital Clinic

Maturity: interactive static demonstration · backend and AI workflow not deployed

Open the verified live demonstration

KAPT Digital Clinic demonstrates a human-directed journey for organisations to describe an operational challenge and understand how KAPT could review it before recommending a suitable digital intervention.

The public experience is a product and workflow demonstration. It is not currently a working case-submission system, client portal or live AI diagnostic service.

Business problem

Organisations often know that a process is slow, fragmented or difficult to manage but do not yet know what digital solution to request. A structured diagnostic journey can help a human delivery team understand the challenge before discussing a pilot or proposal.

Intended users

• organisations describing an operational challenge;
• KAPT reviewers conducting a human assessment;
• programme and management teams evaluating a diagnostic workflow;
• portfolio reviewers examining the proposed service journey.

These are intended users, not evidence of adoption, submissions or active client delivery.

What the public deployment demonstrates

The current default-branch build provides:

• a public product narrative and guided challenge-intake interface;
• client-side validation and consent wording;
• optional fields for organisational context, timing, budget and supporting files;
• legal, privacy, consent and disclaimer pages;
• a demonstration confirmation journey;
• responsive Next.js/React interface design.

On submit, the static demonstration validates the form in the browser, generates a random demonstration reference and opens a confirmation page. It does not transmit the form or selected files to KAPT.

What is not deployed

Connected Netlify evidence shows that the current ready production deploy:

• was published from the repository’s default branch on 15 September 2026;
• is a static export with no serverless or edge functions;
• has no Netlify Forms capture enabled.

The repository contains backend design and implementation material — including server libraries, a Prisma schema and a parked-backend/ workspace — but the public build does not deploy those routes. Therefore the following are architecture evidence, not live capabilities:

• persisted submissions and case records;
• staff authentication and case-management screens;
• protected file storage and downloads;
• email notifications;
• Netlify Blobs persistence;
• Anthropic-assisted diagnosis drafts;
• audit logging and printable client diagnoses.

Source-capture status

The default branch is claude/gstack-impecable-uiui-n6e2kx.

Two unmerged Netlify-generated logo branches remain ahead of it:

• agent-the-logo-for-all-instances-1dff — 3 commits ahead;
• agent-with-third-uploaded-logo-1706 — 2 commits ahead.

Those commits are attributed to netlify[bot], not zaiwin-lab. They represent alternative logo changes and have not been merged because the repository does not establish which version is the approved final brand asset.

Strategic value

The product demonstrates a strong business-first service idea: begin with the organisation’s problem, keep diagnosis human-reviewed and treat AI as an internal drafting aid rather than an autonomous adviser. Its next value milestone is a secure, testable submission-to-review vertical slice.

Technology

Deployed public build

Next.js 15 · React 19 · TypeScript · Tailwind CSS · static export · browser session state

Parked implementation foundation

Zod · Nodemailer · Netlify Blobs adapter · signed-cookie and scrypt authentication modules · Prisma/Postgres schema · optional Anthropic draft-generation module

Listing a parked component does not mean it is active in the public deployment.

Delivery role

Product strategy, diagnostic workflow architecture and supervised AI-assisted delivery are led by Ts. Zaiwin Kassim with the KOBIS AI Prodigy Team.

Human reviewers remain responsible for understanding the organisation, validating facts, selecting an intervention and approving anything sent externally.

Responsible use and limitations

• Do not enter confidential, classified, personal or commercially sensitive material into the public demonstration.
• A generated demonstration reference does not confirm receipt, create a case or start a service engagement.
• Selected files remain in the browser and are not uploaded by the current public build.
• The public site does not run an AI model and does not produce an organisational diagnosis.
• The parked authentication, persistence and upload code has not been evidenced as production deployed or independently security tested.
• Legal and consent copy requires organisational approval before any real-data pilot.
• Any future AI-assisted draft must remain labelled, reviewed and approved by a human before external use.
• Real operation requires durable storage, server-side authentication and authorisation, restricted uploads, malware scanning, retention/deletion controls, audit review and incident procedures.

Recovery and pilot-readiness path

1. Choose and approve one logo branch; do not merge both blindly.
2. Restore one server-side submission path on a controlled test deployment.
3. Persist only minimum necessary data in governed storage.
4. Add role-based staff access and protected file handling.
5. Test consent, notification, deletion, recovery and audit procedures.
6. Evaluate AI-assisted drafts against an approved human-reviewed test set.
7. Document the verified deployment commit and only then reclassify the product for a controlled pilot.

Evidence boundary

This README describes the inspected repository, branch comparisons and connected deployment record. It makes no claim about client adoption, submission volume, diagnoses delivered, revenue, partnerships, endorsements or production readiness.