Status
What is running, and what changed.
The repository behind this site is private, so this page is the public record. The checks request a snapshot from the live Worker when you open the page. The log tracks changes to the site, its features, and how it is served.
Change log
-
Sustain and Headcount, open to anyone
A new section on the homepage introduces Sustain and Headcount, two services that need no referral or NDA. Sustain is the AI maintenance agent for custom apps. Headcount sets up AI agents for one-person companies. Each has its own illustration, which plays once when it comes into view. With reduced motion on, it appears finished.
-
Quality and security lead the headline
The homepage gives its two priorities distinct treatments: quality settles into a solid blue highlight, while brackets close around security. The words remain readable throughout, and reduced-motion preferences retain the finished styling without the entrance effects.
-
Motion that waits for the diagram
The Sustain workflow now waits until its steps are visible before playing, including on mobile. The hero assembly also waits for its drawing. The permissions comparison traces a request through the old access path or stops it at the corrected boundary. A short underline highlights client ownership, and writeup title underlines respond to the whole row's hover or keyboard focus. These effects respect reduced-motion settings.
-
Introducing Sustain
The homepage product feature introduces Sustain, Zetesis's autonomous maintenance agent, with links to explore the product and request early access. A brief animation traces an illustrative maintenance workflow on arrival, hover, or keyboard focus. Reduced-motion preferences keep the illustration still.
The mobile contact layout also stays within the page when the verification widget loads.
-
30-day warranty covers critical and minor defects
The free 30-day warranty after full transfer now covers both system-critical and minor bugs in the agreed deliverable. The page explains how project contracts define coverage for defects, third-party outages, security vulnerabilities, client modifications, unsupported environments, and changes requested after acceptance. The Engineering page reflects the expanded coverage.
-
A closer look at the engineering
A new homepage comparison illustrates the permissions issue from the public writeup and the change that blocked access to private documents. It links to the full explanation and the runnable reconstruction with synthetic data. Both explanations remain readable without JavaScript.
-
Connected selection states and quieter motion
Selection highlights move between the system layers, service choices, project stages, and permissions comparison. Service outlines enter in the direction of the selection, and expanded testing checks have a clearer boundary. The patterns draw on 21st.dev, Motion Primitives, and Watermelon UI, adapted to the site's existing HTML, CSS, and JavaScript. A restrained Haikei step illustration frames the writeup preview. Reduced-motion preferences turn off the transitions.
-
Linked company and founder identity
The team page names Yuvraj Sharma (Yuvi) and includes a Person record with his role, personal profiles, and relationship to Zetesis. Organization data on the homepage and company profile identifies Yuvi Co. LLC, the 2024 founding year, founder, and company profiles. Consistent identifiers connect these records and the writeups' author and publisher metadata.
-
A single headline for software engineering, quality, and security
The homepage now opens with “Software engineering that puts quality and security first.” Only “quality” and “security” are blue. The type scales and wraps naturally across screen sizes, with the service label above and the explanation of private referrals below. Layouts were checked from 320 to 1440 pixels wide.
-
Discuss a project, then introduce it
The main button now says “Discuss a project” and leads through Working Together. Visitors arriving through that button see a small, dismissible prompt after they start reading, with an “Introduce your project” link to the contact form. Its spacing accommodates the longer label. Direct visits to Working Together do not show the prompt.
-
Security and quality, explained through the engineering
The Engineering page explains permission boundaries, sensitive data flows, testing, external services, and handover. It links the permissions writeup and its runnable reconstruction using synthetic documents. The page is linked from the homepage, navigation, and footer, and included in the site build and sitemap.
On the homepage, the Test stage lets readers expand access, failure-handling, and acceptance checks. The matching part of the diagram highlights as each explanation opens. The controls support keyboard use, and the explanations remain available without JavaScript.
-
Optional referral source on project introductions
The contact form asks how visitors heard about Zetesis, with a reminder that they do not need to name a confidential client. The answer is optional and limited to 200 characters. The Worker validates it and forwards a supplied answer with the inquiry; a blank answer is omitted. The privacy notice explains how it is used.
-
Private referrals, agency origins, and the introduction process
The homepage explains that Zetesis works primarily through private referrals and considers new inquiries for project fit and an ongoing working relationship. The About section describes how independent software engineering work grew through referrals and is developing into an agency around those relationships.
The contact section explains that an inquiry is reviewed for fit before a conversation is arranged. It asks for a high-level introduction without confidential material. Working Together sets out the sequence: introduction, mutual fit, an NDA before confidential scoping, an agreed scope and signed contract, then delivery.
-
Choose a starting point for a project
The service selector offers application, AI, automation, and undecided paths. Each shows what to discuss and bring to the first meeting. The choice carries through Working Together into an editable contact brief. Changing the choice updates the suggested text without replacing a visitor's own writing.
-
Writeup navigation and runnable companion code
Writeups now generate section links and a contents list from Markdown. The list stays visible on desktop, highlights the current section, and folds away on smaller screens. Authors can add a brief overview and a repository description. The first writeup includes both, along with local setup commands and code-copy controls. Article text and navigation remain available without JavaScript.
-
Interactive scope-to-handover walkthrough
The homepage project walkthrough follows scope, build, testing, and handover. A sticky diagram changes with the section being read, and the stage links let readers jump ahead or go back. Client ownership is highlighted in blue, with the transfer details explained at handover.
-
An explorable system diagram in the hero
The homepage diagram assembles once as it enters view. Readers can select the interface, application logic, or data and services to see what each layer does, then replay the assembly. The diagram illustrates a general system structure without showing client work.
-
Sharp corners and shorter, more deliberate motion
Buttons, panels, and service cards return to sharp corners and thin borders. Short section entrances replace the longer blurred reveals, with a reading-progress line below the header where supported. The new interactions support keyboard navigation and reduced motion; their content stays readable without JavaScript. Layouts were checked from 320 to 1440 pixels wide.
-
Remote project status toggle
Project availability is stored in Cloudflare D1 and read through the Worker. The site checks every 30 seconds and when a visitor returns to the tab. Pausing new projects adds a header notice and a message beside the contact form, without a site deployment.
-
Click-to-reveal phone control
The contact section adds a telephone link when the reveal button is selected. The value is decoded from base64 in the browser. This delays its display; it does not keep the value private from someone reading the JavaScript.
-
Status page and live checks
This page. The status response confirms the Worker can answer and checks access to the rate-limit store. Bot-check and mail-relay rows report configuration, not a completed form submission or inbox delivery. The snapshot has no stored history or uptime percentage.
-
Writeups link their source repository
Writeup metadata now accepts an optional source-repository link, displayed beside the author and date. The first article includes one, giving readers a way to inspect the accompanying code.
-
30-day warranty for minor issues
The initial warranty policy introduced a free 30-day period after full transfer for minor issues. Coverage was expanded on 20 September to include system-critical bugs; the linked section contains the current terms.
-
Company details and public profiles
The company page brings together the operating name, business entity, founder, contact details, and official profiles. It also states who owns the code, repository, and infrastructure. The team profile now links to Yuvi's personal GitHub and LinkedIn accounts.
-
Working Together page
Working Together explains the signed project agreement, the 1% initial payment credited toward the quote, and payments after milestone approval. It covers ownership, confidentiality, third-party services, optional maintenance, termination, disputes, and liability. Payment examples show how the amounts add up.
-
Maintenance costs explained
The support section gives an indicative monthly maintenance range and separates provider costs from upkeep. It explains the included provider-cost cap, shows a worked example, and identifies which details belong in the project-specific maintenance agreement.
-
Reading navigation and a quieter contact prompt
The main project button leads to Working Together. Its contents navigation stays visible and highlights the section being read. Visitors arriving through that button see a small, animated contact prompt after they start reading; they can dismiss it and continue without an overlay covering the page.
-
Writeups compile at build time
Markdown writeups compile into complete HTML pages, an article index, metadata, and a sitemap. CI checks pull requests to main; pushes to main also build and publish the site. Drafts stay unpublished, and invalid publication metadata stops the build. Reading an article no longer depends on a browser-side GitHub API request.
-
Team page and named authorship
The team page introduces Yuvi as Founder & Technical Lead, explains his work, and notes plans for future hires. Writeups name their author and link back to the profile, while the main site stays focused on the agency.
-
First engineering writeup
Why a system prompt is not a security boundary documents a permissions issue found in sandbox testing before deployment. It explains the credential separation that addressed it while keeping the client and their documents confidential.
-
One message per IP address each hourly window
The contact form uses Workers KV to count accepted submissions by IP address within each clock-hour window. The allowance is recorded after the mail relay accepts the request. An expired bot check does not use it, and relay acceptance does not confirm inbox delivery.
-
Contact form moved behind a Worker
The form posts to a Cloudflare Worker instead of straight to the form service. The Worker validates the required fields and checks the Turnstile token before forwarding a submission. The form shows the result and offers email as an alternative when submission fails.
-
Privacy policy and custom error pages
A privacy policy describes the contact form's data flows and the services involved. Custom 404 and error pages give visitors a route back to the site.
-
Inbound mail on Cloudflare Email Routing
Mail for the domain routes through Cloudflare to an existing mailbox. Receive and forward only, so there is no mail server to run or patch.
-
Agency site and visual identity
The initial site presents the three service lines, project estimate ranges, toolchain, agency background, and contact form. Switzer headings and body text pair with JetBrains Mono labels. The zeta mark, favicons, and social preview image carry the identity beyond the page.
-
Domain live on Cloudflare and GitHub Pages
Nameservers moved to Cloudflare. The site is static files served by GitHub Pages behind the Cloudflare proxy, with HTTPS end to end.