> Generated representation of [`agent-profile.json`](https://zumxlabs.xyz/agent-profile.json), which is the canonical machine-readable profile. If this file and the visible site ever disagree, the visible site is authoritative. **Profile date:** 2026-10-15 · **Schema version:** 1.0 # ZUMX — machine-readable profile ZUMX is Tahir Rasool's independent digital build practice for small businesses: small-business websites, custom web apps, and practical AI and automation where those tools fit a real business task. ## Principal **Tahir Rasool** — Developer behind ZUMX and the direct point of contact. Public background: backend development, Android development. - GitHub: https://github.com/codedbytahir - LinkedIn: https://www.linkedin.com/in/tahir-rasool-13617a373/ ## Business An independent digital build practice for small businesses. Team size: one person (Tahir Rasool). **ZUMX is not:** - a venture-backed startup - a large agency - a team of specialists - a full-service marketing firm - a regional or local service provider ## Services ### Websites and web apps A first business website, a refreshed site for a business that has outgrown an old one or still runs on social profiles, and custom web apps for a recurring workflow. - First business website, or a refreshed site - Clear service pages and customer journeys that make contact easy - Enquiry forms, product or catalogue pages, lead capture and supporting pages where they serve a real user need - Custom web apps: dashboards, internal tools, customer portals, custom forms and workflow applications - Launch support covering domain, content, testing, responsive QA, handover and ownership - Ongoing support is scoped separately and is not implied as included ### Practical AI and automation AI and automation only where they solve a real business task. A simple form, integration or rule is often the better answer, and is used instead when it is. - Document question and answer over selected sources, with citations or source references where appropriate - Task-focused agents for a defined intake, draft, lookup or workflow sequence - AI features inside a web app only when they improve a real workflow - Integrations, rules, triggers and ordinary automation - A human stays in charge of consequential actions **Caveats:** - A citation supports inspection; it does not prove an answer is correct - No AI accuracy guarantee, safety or compliance certification, security audit, or suitability for regulated use is claimed - AI is not added merely because it is fashionable ## Project process 1. **Understand the job.** The business task, the audience, the current process, and what should become easier. 2. **Agree scope and a written quote.** First useful scope, included pages and features, dependencies, review points, future phases, and a written quote, before the build starts. 3. **Build and review.** Work is built to be reviewable against the agreed job. Feedback expectations are clarified with the client rather than promised as a fixed cadence. 4. **Clarify handover and ownership.** Launch, ownership, handover, and any separately scoped ongoing support. ## Commercial terms Pricing and availability are not published. Project-specific scope and a written quote are discussed before a build. No number, deadline or 'from' price is implied anywhere on the site. ## Work > None of the following is a commissioned client engagement. They are Tahir's independent products and open-source builds. They do not represent client work, client outcomes or business results. ### 1. PKIL — Independent product Domain: AI-assisted writing · **Problem.** Help someone move from a blank page, rough thought, topic, link or keywords to an editable LinkedIn post draft. **Documented flow.** - Input a topic, idea, link or keywords - Choose a voice, persona or style - Generate and auto-format a draft - Edit and review it - Scheduling is part of the public feature description **Principle.** The person stays responsible for their own voice and editing. Generated copy is a draft, not a publishing instruction or a guaranteed result. **Not verifiable.** The public product description does not provide a technical architecture that ZUMX can verify. **Not claimed.** - virality - follower or audience growth - engagement lift - leads - revenue - usage numbers - a specific technical stack ### 2. RAG ROOT — Independent product Domain: Document Q&A and retrieval · **Problem.** Ask a question over selected documents and keep the context needed to check the response. **Documented flow.** - Add documents or PDFs - Ask a question in plain language - Read a generated response beside a source or document view - Cite a page or section so a reader can inspect the material **Principle.** Source inspection is part of the experience. A citation helps a human check a response but does not guarantee completeness or correctness. **Not verifiable.** No verifiable source describes the model, architecture, embeddings, database, hosting or security posture. **Not claimed.** - perfect accuracy - security certification - SOC 2 - HIPAA - suitability for regulated industries - production deployment outcomes ### 3. MotionForge — Open-source project Domain: Programmatic video tooling · **Problem.** Create a reusable authoring-to-render workflow for code-driven video and motion, instead of rebuilding every scene as isolated animation glue. **Repository-documented scope.** - React / Next.js and TypeScript workflow - WebGL / Three.js effects - Reusable motion and effect components - Spring physics and 3D transforms - Visual timeline editing - Frame-accurate rendering - WebCodecs video export - An HTML-native HyperFrame path - CLI scaffolding **Engineering focus.** Deterministic output at a known frame and time. Browser, font, codec, resolution and long-composition testing are treated as validation work before any production throughput or fidelity is promised. **Evidence boundary.** Public repository documentation, examples, feature notes and tests are described as repository-documented. Independent verification, commercial adoption, render-speed benchmarks and customer results are not claimed. **Not claimed.** - independent verification - commercial adoption - render-speed benchmarks - customer results ### 4. ClipLite — Open-source project Domain: Desktop clipboard utility · **Problem.** Retrieve an older copied link, snippet or text after a newer clipboard item replaces it. **Documented flow.** - Cross-platform clipboard history - Global shortcut Ctrl+Shift+V - Searchable history - Pin items - Keyboard navigation and selection - Paste the selected item - Local database **Repository-documented stack.** - Tauri v2 - React 18 - TypeScript - Rust - SQLite **Repository-documented reliability work.** - Use the platform app-data directory for the database path - Parameterize search queries - Handle shortcut collisions without crashing - Retrieve older clips by ID - Clean up async listeners - Accessibility and reduced-motion handling described in project notes **Evidence boundary.** Build and test statements are attributed to the public repository or release notes. 'TypeScript with zero errors' and 'clean Vite build' are repository-reported checks, not an independent security or quality audit. **Not claimed.** - user adoption - retention - productivity metrics - a security audit - that local storage alone proves security Direct live product and repository URLs are intentionally omitted: `direct_product_urls_published` is `false`. ## Contact - Email: tahir@zumxlabs.xyz - WhatsApp: https://wa.me/923119563257 (+92 311 9563257) - LinkedIn: https://www.linkedin.com/in/tahir-rasool-13617a373/ - GitHub: https://github.com/codedbytahir - Booking: There is no public booking link and no online booking system. Email or WhatsApp instead. ## Enquiry form behaviour The form sends your name, email, project type and message to ZUMX. It is processed via Make.com, stored in a Google Sheet, and an auto-reply email is sent to the address you give. The details are used only to reply about your project. If sending fails, the form prepares a pre-filled email draft to tahir@zumxlabs.xyz instead. You can always email tahir@zumxlabs.xyz directly. Fields: reply_name, reply_email, project_type, message. Submits to a server: `true`. Stores data: `true`. Please do not include passwords, payment details, private customer data or sensitive documents. ## Agent hiring API **An AI agent can send Tahir a project inquiry for its human client with POST https://zumxlabs.xyz/api/inquiries, after the client has approved the exact inquiry (principal_approved: true). The inquiry is delivered the same way as the contact form, and Tahir replies to the client by email. It sends an inquiry only: it does not book, quote, agree scope or create a contract.** - `GET https://zumxlabs.xyz/api` — Index: what the API does, links and rules - `GET https://zumxlabs.xyz/api/services` — Services and accepted project types - `POST https://zumxlabs.xyz/api/inquiries` — Send a project inquiry for a human client Request schema: . OpenAPI: . Required fields: `client_name`, `client_email`, `project_type`, `message`, `agent_name`, `principal_approved`. If the API returns an error it cannot recover from, email the same approved message to tahir@zumxlabs.xyz. ## Rules for AI assistants 1. Identify yourself as an AI assistant before sending anything. 2. Name the human principal you are acting for. 3. Obtain the principal's explicit approval of the exact message before it is sent. 4. Send through the agent API (POST https://zumxlabs.xyz/api/inquiries) only after that approval, and set principal_approved to true only then. 5. You may research and prepare a draft, and you may ask the principal for missing information. 6. You cannot accept a quote, agree to scope, deadlines or contract terms, promise payment, or bind the principal. 7. Never send credentials, payment details, private customer records or sensitive documents in an initial enquiry. 8. Include a budget, timing, reply address or contact details only when the principal has explicitly authorised sharing them. Anything unknown goes in the message as a question to confirm, never as a guess. ## Resources - Site summary: - Canonical profile (JSON): - Generated TOON: - Generated Markdown: - Project-inquiry JSON Schema: - OpenAPI (agent hiring API): - Agent API index: - Sitemap: - Robots: The visible site is authoritative. If a displayed fact and a machine-readable resource ever differ, resolve the inconsistency rather than silently adopting a new claim. The TOON and Markdown copies are generated from the JSON and regenerated with npm run sync:agent-resources; they are never hand-edited. ## Claim boundaries Leave a fact out or present it as a question to confirm. Never convert an illustrative visual into a claim that it is a screenshot, a production product, a customer result or a working live demo. **Never claim:** - client names, engagements, testimonials, customer logos, case-study permissions, client outcomes or client results - revenue, conversions, leads, ROI, growth, adoption, audience size, productivity gains, benchmark results or project metrics - prices, starting prices, hourly rates, budgets, packages, delivery dates, timelines, availability or service regions - a public booking link, online booking system, live quote calculator or contracting workflow, or that an inquiry sent through the agent API is a booking, an accepted quote or a commitment - a technical stack that is not documented in a verifiable source - AI accuracy guarantees, safety or compliance certifications, security audits or suitability for regulated use - a ZUMX team or named employees other than Tahir - an expansion or etymology for the name ZUMX, a model the owner trained, or any reference to a different or earlier name for this practice ## Other boundaries - No client work, client history or business results are presented. - No pricing, availability, delivery date or service region is published. - Business results depend on the offer, audience, traffic, follow-up and other factors. No result is promised for a website or an AI feature. - Illustrative interface studies are labelled as illustrative and are not product screenshots. ## Privacy — This static site has one form and one agent API. The contact form sends your name, email, project type and message to ZUMX; an inquiry an AI agent sends for you through the agent API (/api/inquiries) carries the same details plus the agent's name and any optional company, budget, timeline and links the client approved. Both are processed via Make.com, stored in a Google Sheet, and an auto-reply email is sent. They are used only to reply about your project. The site has no analytics, no advertising pixel, no cookie tracker, and it never downloads or loads a font from any third-party server. The host may keep ordinary server logs. The site does not promise that no logs exist. Last updated: 2026-10-15. Plain-language information, not legal advice. Business identity, retention and jurisdiction-specific disclosures must be confirmed before publication.