{
  "schema_version": "1.0",
  "product": "TUKO",
  "category": "Business operations command system (ERP-class)",
  "tagline": "Run your business. Know what to do next.",
  "platforms": ["web", "ios", "android", "windows", "macos"],
  "pricing": {
    "free_tier": true,
    "card_required": false,
    "core_is_free": true,
    "model": "free_first",
    "tiers": {
      "tuko_core": "Free — the complete operational system: customers/CRM, sales and orders, quotes and invoices, payments and receivables, inventory, purchasing, expenses, reports, CSV import/export, HR (attendance, leave), payroll, multi-location, POS, and Business Pulse. No subscription and no per-seat, per-location, or per-record charges.",
      "tuko_intelligence": "Optional premium layer under development — advanced forecasting, scenario planning, and analytics. Not for sale yet; no published pricing.",
      "tuko_enterprise": "The only paid organizational tier — custom contract for SSO, advanced governance/audit, contractual SLAs, dedicated support, custom integrations and retention, and implementation services."
    },
    "retired_tiers": "Starter, Growth, and Scale were retired; everything they covered is part of the free TUKO Core.",
    "note": "The complete core system is free. Optional paid offerings are arranged on the web, not billed through the app stores."
  },
  "capabilities": {
    "attendance": {
      "name": "Attendance & photo-verified time clock",
      "summary": "Employee self-service timekeeping with optional photo verification.",
      "facts": [
        "Employees clock in/out from the TUKO app on web, iOS, or Android.",
        "Workspace admins can require a photo at clock-in, clock-out, both, or neither (per-organization attendance policy); self-service clocking can also be disabled entirely.",
        "Every punch is stamped with the SERVER clock — editing the device time cannot fake an entry; the device timestamp is diagnostic only.",
        "Punches are idempotent: double-taps and retries cannot create duplicate records.",
        "Attendance photos are stored in private storage, path-scoped to the organization; the employee sees their own and authorized managers/HR view evidence through short-lived expiring links. TUKO does NOT perform facial recognition or biometric identification on these images.",
        "Photos are deleted automatically 60 days after the punch by default (admins may set 1–365 days); the attendance record is retained.",
        "Corrections go through an employee request + manager approval flow that preserves the original record.",
        "Daily summaries (worked hours, overtime, incompletes) are grouped by the organization's timezone and feed payroll without re-encoding."
      ]
    },
    "payroll": {
      "name": "Payroll",
      "summary": "Payroll runs inside the same workspace as attendance, leave, and the employee directory.",
      "facts": [
        "Payroll is restricted to workspace owners and admins; employees see only their own payslips in My Workspace self-service.",
        "A run covers a period at a chosen frequency (weekly, every 2 weeks, twice a month, monthly). Overlapping runs are rejected so a period cannot be paid twice.",
        "Flow: create draft run -> compute (one line per employee) -> submit for review -> approve -> generate payslips -> mark each line disbursed. Run statuses: Draft, Computed, Under review, Approved, Paid, Cancelled, Reversed.",
        "Gross pay comes from each employee's effective-dated compensation plus their approved attendance for the period; extra amounts are added as explicit earning/deduction adjustment lines.",
        "Statutory rules are a versioned ruleset per jurisdiction; a run cannot be approved until the rules are verified and blocking exceptions are cleared.",
        "Approved runs are locked and immutable. Corrections land as audited adjustments in the next run or as a reversal with a recorded reason.",
        "Philippines pack: SSS, PhilHealth, and Pag-IBIG contributions (employee and employer shares), BIR withholding tax, holiday/overtime/night-differential multipliers, and 13th month accrual pro-rated for mid-year hires. TUKO computes the amounts; employers still file and remit with the agencies.",
        "HR beside payroll: an employee directory, weekly schedule patterns that generate dated rosters, and leave requests that hold balances until a manager approves or rejects them."
      ]
    },
    "next_move": {
      "name": "TUKO Next Move",
      "summary": "A single ranked feed inside the app that answers 'what should I do first?' each day.",
      "facts": [
        "Next Move composes the workspace's own findings — overdue receivables, orders needing follow-up, low stock, plus growth-plan items and external opportunity matches — into one ranked list.",
        "Ranking is deterministic and evidence-backed: every card shows the reason lines (amounts, waiting time, urgency) that placed it there. No hidden scoring, no fabricated urgency.",
        "Cards deep-link to the screen that resolves them; items can be snoozed (time-boxed) and are marked Seen once opened.",
        "The Business Growth Plan is the full checklist; Next Move is the short daily-ranked slice of it."
      ]
    },
    "results": {
      "name": "TUKO Results",
      "summary": "The outcome loop built into every TUKO plan — signals with evidence, actions the owner approves, and results verified against the business's own records.",
      "facts": [
        "The loop: detectors find what needs attention in real business records; findings rank into one daily list with reasons; the owner approves each action (recorded in an audit trail); where records change, TUKO reports what the evidence confirms; detectors keep scanning against the organization's own baselines.",
        "Verified results are reported conservatively — 'paid after follow-up', converted quotes, repeat orders that arrived after detection. Temporal evidence, not a causation claim. Activity (a reminder sent, a task created) is never counted as a result.",
        "Estimated values are always labeled 'est.' and never blended into observed metrics; insufficient data is reported as insufficient, never replaced with an invented baseline.",
        "TUKO does not guarantee revenue, profit, or cash-flow outcomes; does not charge based on outcomes (included in the free TUKO Core; the only paid offerings are Enterprise contracts and the future TUKO Intelligence layer); and never takes actions without owner approval.",
        "Owners can set named goals on real metrics (30-day sales, collections, overdue receivables, low-stock count, health score) with targets and deadlines. Progress is measured from a baseline snapshotted when the goal is set; 'achieved' and 'missed' are written by the system from live records, never by marking a goal done.",
        "Outcome verification annotates growth-plan items with what the source record shows — 'resolved by records' when a detector no longer sees the condition, 'closed by review' when a human records the outcome in-system. Activity is reported in its own labeled section, never blended into verified results.",
        "Managed results services and outcome-linked pricing are roadmap items — not shipped today. Shipped-vs-planned status: https://tukohq.com/results/"
      ]
    },
    "business_pulse": {
      "name": "Business Pulse",
      "summary": "TUKO's intelligence layer, shown as a ranked card on the Command Center.",
      "facts": [
        "Deterministic detectors scan real business data — orders, payments, inventory, purchase orders, expenses, payroll, attendance, and locations — across 30 signal types including overdue invoices, low stock, stockout risk, sales decline, expense spikes, and anomalies vs the org's own trailing 84-day baselines.",
        "Every signal carries evidence (the actual numbers) and a recommended action — create a task, open the customer/order/product, or record a payment. Users can dismiss, snooze, or act.",
        "Estimated values are always labeled 'est.' and never blended into observed metrics.",
        "An optional decision-model enrichment (TypeSafe Jev) can re-rank priorities: off by default, provider-controlled kill switch, sends only minimized numeric state (no names, notes, or PII), low-confidence verdicts fall back to standard ranking, and every evaluation is recorded and auditable. It is advisory only — it cannot mutate records.",
        "Every workspace ships a built-in Help Center: searchable articles and quick guides under the ? icon or Help in the sidebar."
      ]
    },
    "business_world": {
      "name": "TUKO Business World",
      "summary": "The whole business rendered as a living 3D map — a glanceable spatial layer over the same organization-scoped data the reports read, plus a live operations campus for today's sites, people, transfers, and activity.",
      "facts": [
        "Fourteen districts — command, sales, stock, cash, customers, collections, POS, people, purchasing, expenses, locations, tasks, pulse, growth — rise as towers. Height encodes activity for the selected period, cap color encodes health computed from the org's own records, and a beacon marks districts holding Business Pulse alerts needing attention.",
        "A live operations campus renders today's state: every real location (HQ, branch, kiosk, warehouse) stands as a site building sized by current activity with a stock bar for units on hand; staff who punched in today appear inside their site; open register sessions highlight cashiers; completed stock transfers draw arcs between sites; recent orders, punches, and sessions pulse where they happened.",
        "Presence states are honest — attendance is in/out only, so people show as working or timed out with no inferred breaks; transfers post atomically so flows always read completed rather than a fabricated in-transit state.",
        "The world is a presentation layer over the same authenticated, permission-checked services as every other screen. It never invents numbers, never writes back to data, and restricted districts render dimmed rather than leaking data. Where employee visibility is restricted, names are masked to role labels and headcounts report unknown instead of a misleading zero.",
        "Unavailable data renders as inactive — never a fake zero. Estimated values stay labeled 'est.' and are never blended into observed metrics.",
        "Selecting a district, a site, or a person opens its records with evidence and a deep link into the owning module (Reports, Cash Flow, Inventory, Customers, HR, Scale); staffed sites support stepping inside.",
        "An accessible district directory and a live operations board list every district, site, person, transfer, metric, and alert as plain selectable content — works on no-WebGL devices, with screen readers, and under reduced-motion settings. Rendering pauses when the tab is hidden and pixel density is capped.",
        "The 3D view is feature-flagged per workspace; the directory and live operations board work on every platform regardless."
      ]
    },
    "cash_flow": {
      "name": "Cash Flow Foresight & Revenue Recovery",
      "summary": "Two features that answer 'will I have enough money' and 'what should I act on today'.",
      "facts": [
        "Cash Flow Foresight projects cash day-by-day (7/30/90-day horizons) from verified records only: order due dates, approved expenses, committed purchase orders, payroll runs, recorded payments. It requires a user-entered opening balance and never invents one.",
        "Reconciliation: opening balance + expected inflows - expected outflows = closing, for every day. Overdue and undated receivables are listed separately — never scheduled into the forecast.",
        "Warnings fire on a user-configured buffer; what-if scenarios (delay, partial, drop) run in memory and never mutate records.",
        "Revenue Recovery ranks overdue payments, stalled quotes, and repeat-purchase opportunities with evidence-backed reasons; follow-ups are logged with channel and outcome. Results are reported as 'paid after follow-up' — an honest evidence claim, not a causation claim.",
        "The basic features are in the free TUKO Core; the 90-day horizon and saved scenarios are planned for TUKO Intelligence, the optional premium layer still under development."
      ]
    },
    "customer_360": {
      "name": "Customer 360",
      "summary": "Every customer profile is a full view of the relationship.",
      "facts": [
        "Each customer carries a server-computed health score (0–100) built from five signals: recency, frequency, value, payment health, and trend — grouped into bands (new, strong, healthy, watch, at risk, dormant).",
        "The profile shows lifetime stats from real orders only (orders, actual revenue, average order, reorder cycle), open opportunities, contacts, addresses, notes, tags, and a paginated timeline.",
        "Estimated opportunity values are always labeled 'est.' and are never blended into observed revenue.",
        "Members restricted to locations see only their locations' customers plus unassigned ones; all mutations are audited."
      ]
    },
    "scale": {
      "name": "TUKO Scale (multi-location)",
      "summary": "The multi-location layer — one workspace, every branch.",
      "facts": [
        "Locations are org-scoped entities (branch, kiosk, warehouse, HQ). Orders, customers, expenses, tasks, and staff can be assigned to a location; the Scale overview aggregates revenue, orders, customers, and staff per location with period-over-period change.",
        "Members can be restricted to assigned locations — they see only their locations plus unassigned records; owners and admins see everything.",
        "Business blueprints capture a proven location's product assortment and operating checklist; applying one creates the checklist as tasks at a new location (idempotent — re-applying does not duplicate).",
        "Franchise management (networks, franchisees, agreements, fees, compliance tracking) runs on the same rails and is feature-flagged.",
        "Location detectors feed Business Pulse: underperforming branches and location sales declines surface as ranked signals."
      ]
    },
    "pos": {
      "name": "TUKO POS (tablet point of sale)",
      "summary": "A tablet-first point-of-sale terminal inside the TUKO workspace — not a separate product.",
      "facts": [
        "Cashier flow: open a register session, tap products on a category grid or search by name/SKU/barcode, take payment, print or share the receipt. Designed for landscape tablets; adapts to portrait and phones.",
        "Terminals are registered per organization and location, with a unique code per organization, optional device binding, and a default receipt printer.",
        "Cashier sessions carry an opening float; expected cash is computed server-side; counted cash and variance are captured at close in an X/Z-style session summary. Cash payouts during a session require a reason.",
        "Payments: cash (tendered amount, computed change, quick-tender buttons), card, bank transfer, digital wallet, check, and other — plus split payments across methods on one sale. Card payments are recorded, not processed; TUKO does not run a card terminal.",
        "Payments are individually auditable and idempotent — a double-tap or retry can never create a duplicate sale.",
        "Discounts, payouts, refunds, voids, reconcile, and terminal/printer management are permission-gated and written to the audit trail.",
        "POS sales flow into TUKO orders, payments, inventory, and Business Pulse — no separate analytics. Currency and timezone come from the organization."
      ]
    },
    "integrations": {
      "name": "Integrations",
      "summary": "TUKO connects to external accounting, e-commerce, point-of-sale, and CRM providers through a single integration platform.",
      "facts": [
        "Supported providers: QuickBooks Online, Xero, FreshBooks, Shopify, WooCommerce, Wix, Squarespace, Salesforce, Square POS, Toast POS, and Lightspeed POS.",
        "Synced data types: customers, products, orders, payments, expenses, inventory levels (varies by provider; chosen per connection).",
        "Records are matched on provider IDs — re-syncs update in place, never duplicate.",
        "Authorization uses each provider's official OAuth sign-in; TUKO never sees provider passwords. Credentials are encrypted per connection.",
        "Sync is automatic after the initial import; failures retry with backoff and are visible in a per-connection activity log.",
        "Disconnecting is reversible and keeps already-synced data. CSV import remains available alongside live integrations."
      ]
    },
    "mobile": {
      "name": "Mobile apps (iOS & Android)",
      "summary": "TUKO: Business Manager & POS is the native app — the same workspace as the web app, one account and one set of data everywhere.",
      "facts": [
        "The Android app is live on Google Play (com.tuko.app); the iOS app is live on the App Store (https://apps.apple.com/us/app/tuko-business-manager-pos/id6821272392); the web app is fully live today.",
        "The phone app carries the full command system: daily brief, orders, customers, inventory, payments, expenses, POS register, HR, attendance, and payroll.",
        "Photo-verified clock-ins, receipts, and approvals are built for the phone.",
        "Package identity: com.tukohq.app on iOS and com.tuko.app on Android; deep links use the tuko:// scheme.",
        "Free — TUKO Core is the complete system, no credit card and no subscription. Optional paid offerings (TUKO Intelligence when it ships, Enterprise contracts) are arranged on the web, never billed through the app stores."
      ]
    },
    "windows": {
      "name": "TUKO for Windows (desktop app)",
      "summary": "The desktop app for tills, kiosks, and back-office PCs — the same TUKO workspace, plus what a browser cannot do.",
      "facts": [
        "Offline POS: the register keeps taking sales with no connectivity. Sales queue durably on the PC and replay automatically on reconnect — same cashier, same organization, deduplicated.",
        "Offline attendance kiosk: staff clock in/out at a shared PC; punches queue with their REAL timestamps and photos, and backfill in order when the connection returns.",
        "Setup contract: sign in once and open the register once while online so the app can save the catalog, terminal, tax profile, and staff list.",
        "Receipt printing goes straight to a chosen Windows printer — no print dialog per sale; the sale commits before printing so a printer failure never loses a sale.",
        "Sessions are stored encrypted with Windows' own data protection; a --kiosk flag locks a shared station to the clock-in screen.",
        "Updates are automatic: the app checks on launch and hourly, downloads in the background, and installs on quit.",
        "System requirements: Windows 10 or later, 64-bit (x64), dual-core, 4 GB RAM, 500 MB free disk."
      ]
    },
    "offline": {
      "name": "Offline capability",
      "summary": "Offline capture exists on the Windows app and the iOS/Android apps; the plain web app needs a connection to sell.",
      "facts": [
        "Offline POS sales (iOS, Android, and Windows desktop apps) are queued durably on the terminal and replayed automatically when connectivity returns — same cashier, same organization, deduplicated.",
        "Sales needing attention (e.g. a different cashier signed in, a removed product, insufficient stock) are parked for manager review, never silently lost.",
        "Queued sales keep their real timestamps — a 3:14 PM sale is recorded as 3:14 PM, not re-stamped to sync time.",
        "The register must prepare while online: sign in and open the register once so the app can save the catalog, terminal, tax profile, and staff list. A device that has never been online cannot sell offline.",
        "Card and e-wallet payments still need the network to authorize — offline selling is cash-and-recorded-credit territory."
      ]
    }
  }
}
