"It's not where you have been, but where you are going"

The TaTech App Signature

One standard, signed and locked: 24 points across five disciplines that every ta-techsolutions app ships before it is "done" - so any one of them is instantly recognisable as TaTech-grade, and they all stay aligned.

ExperienceIntelligence & communicationTrust, security & brandQuality, docs & observabilityEngineering discipline

Alignment scoreboard

Where each platform stands against the signature. A living matrix, updated as apps advance.

Done In progress To do
Signature pointPamojaCivicLoopPolyHealthPulSeAAANdamBaSaBiStanleyCom
1.Themes
2.Mobile-first + offline PWA
3.Multilingual
4.Great UI/UX
5.Named AI assistant
6.Self-testing suite
7.Voice-narrated walkthrough
8.How-to docs
9.Platform console
10.Observability
11.Source of truth + brief
12.Branding signature
13.Data discipline
14.RBAC + privacy
15.Everything editable + removable
16.No hardcoding
17.White-label isolation
18.AI onboarding questionnaire
19.Slack-grade in-app comms
20.Smart forms + address autocomplete
21.Engineering hygiene & release gates
22.Branded-domain hosting
23.Global-ready units
24.Event-driven & agentic automation

The 24 points, by discipline

Experience

  1. 1

    Themes

    Light and dark mode, user-toggle, persisted. The product respects the user’s environment from the first paint.

  2. 2

    Mobile-first + offline PWA

    Designed mobile-first, installable on iOS and Android with the tenant’s own icon, and core flows work offline (cache + queue, sync on reconnect) for places where connectivity is not guaranteed.

  3. 3

    Multilingual

    Every UI string in every supported language from day one. i18n is part of "done" - never an English-only screen, never a runtime AI-translation dependency.

  4. 4

    Great UI/UX

    Polished and on-brand, with back navigation on every sub-page (no dead ends) and a first-run in-app guided tour plus per-feature help.

  5. 15

    Everything editable + removable

    Full create, edit, and delete on every entity the app creates. No write-only data, no dead records.

  6. 16

    No hardcoding

    It is multi-tenant: admins define their own lists and content (types, levels, fees, roles). Ship sensible defaults; hardcode nothing a tenant might want to change.

  7. 20

    Smart forms + address autocomplete

    Real dropdowns for every enum, a currency prefix on money, country and region pickers, translated labels and options, and address autocomplete - never a bare text box.

  8. 23

    Global-ready units

    Used worldwide, so every measurement offers both systems with a toggle (km/mi, kg/lb, C/F); dates and numbers are locale-aware; money is per-tenant currency. Store metric, convert at the edge.

Intelligence & communication

  1. 5

    Named AI assistant

    Each tenant’s assistant is named after the owner, answers from a knowledge base of the app plus that tenant’s own policies, and falls back to a general model when it does not know. Role-scoped and renameable.

  2. 18

    AI onboarding questionnaire

    A comprehensive owner questionnaire, in every language, seeds the tenant assistant’s knowledge base at onboarding so it answers real questions from day one.

  3. 19

    Slack-grade in-app comms

    Channels, threads, reactions, mentions, search, and slash commands - and beyond Slack with a WhatsApp/SMS bridge, an AI persona, auto-translation, and inline cards.

  4. 24

    Event-driven & agentic automation

    Database triggers react to events (each shipped with an inline smoke test), and a scheduled, secret-gated agentic runner uses the free LLM tier for reminders, cleanups, and forecasts. Automation is part of "done".

Trust, security & brand

  1. 9

    Platform console

    A separate TaTech-engineer tier, distinct from the tenant’s own admin, with access levels (owner/engineer/support): cross-tenant health and usage, a kill-switch to suspend a tenant, and audited impersonation ("view as a tenant"). Per-tenant billing.

  2. 12

    Branding signature

    Per-tenant logo across the app, the PWA icon, and every printable; a "Powered by TA-Tech" line; branded printable documents; and never an em-dash.

  3. 14

    RBAC + privacy

    Access control enforced in the database, least-privilege by default, sensitive data scoped to the right roles. Privacy is the default, not a setting.

  4. 17

    White-label isolation

    Every tenant experiences the app as if it were built only for them: their brand, their AI, their data, their customizations. No cross-tenant leakage.

  5. 22

    Branded-domain hosting

    Every product on its own domain with branded subdomains (app, docs, videos); never a raw platform URL in public. tatech.dev only embeds the demo reel.

Quality, docs & observability

  1. 6

    Self-testing suite

    An in-app test runner, access-control and privacy QA, and recorded demos. Real tests that assert behavior and database writes, plus an every-button-per-role regression sweep. Green before every release.

  2. 7

    Voice-narrated walkthrough

    A voiced, captioned UI tour in every language - both a detailed end-to-end walkthrough and a short highlight reel. It doubles as a QA pass and a sales asset.

  3. 8

    How-to docs

    User-facing help and a documentation site, updated with every patch. No doc-debt.

  4. 10

    Observability

    Error tracking, synthetic uptime and flow monitors, a health dashboard, and alerts - our own Datadog, built in.

  5. 11

    Source of truth + brief

    A canonical page and API inventory, and an in-app executive brief tab so anyone can understand the product in a minute.

Engineering discipline

  1. 13

    Data discipline

    Versioned schema snapshots over ad-hoc migrations, dev-first, access-controlled, with a code-vs-schema audit before every release.

  2. 21

    Engineering hygiene & release gates

    Build before push, click through in dev, docs with every patch, a fresh schema dump before SQL, trigger smoke-tests, API audits, and no test accounts on production.

How the standard stays locked

One source of truth

The signature lives in TATECH_STANDARDS.md, copied into every repo. A new app starts by dropping in the file.

Enforced in CI

A shared standards check runs on every build and fails on violations (for example, the no-em-dash gate).

This scoreboard

A living matrix so a single glance shows which app is behind on which point.

Updated by direction

When a new rule is set, the doc, this page, and the in-repo standard are updated together.

The point of the signature is simple: a client who adopts one TaTech product knows exactly what every other one will feel like.