Product guide

Product Specification

Product

CarVitae (카비테 in Korean) is a premium, local-first vehicle ledger. People record fuel, charging, service, repairs, expenses, optional vehicle-related income and manual trips, inspection checklists, meter readings, documents, and reminders; they can then search years of history, understand tracked spend, and hand a useful history to a buyer without surrendering control of the raw data.

First-release outcomes

1. Register, edit, archive, sell, and switch among multiple vehicles, with an optional verified private photo for long-lived Garage identification. 2. Record ICE fuel, EV charging, services with multiple searchable line items, expenses, optional income/manual trips, inspection checklists, meter readings, reminders, documents, and attachments. 3. Keep data offline, searchable, exportable, backupable, and restorable. 4. Calculate cost, full-to-full fuel economy, electric efficiency, and reminder due state reproducibly. 5. Generate a privacy-aware Seller Pack PDF and a checksummed .carvitae transfer package. 6. Offer privacy-safe widgets and platform shortcuts that open reviewable local actions without writing a record on the user's behalf. 7. Keep backup restore, vehicle-transfer import, and full local-data erasure reachable before a vehicle exists, so no residual local templates or files trap a person in onboarding.

Deliberate non-goals for launch

• OBD or diagnostic claims, repair booking, insurance sales, resale marketplace, automatic price estimates, external recall data without an explicit data source, ad networks, and social feeds.

Information architecture

| Navigation area | Primary purpose |

| --- | --- |

| Home | Current meter, status, upcoming work, monthly spend, review queue |

| Timeline | Unified, filterable, searchable vehicle event ledger |

| Quick Add | Fuel, Charge, Service, Expense, Income, Trip, Inspection, Meter, Document, Reminder |

| Reports | Cost flow, energy efficiency, maintenance, drill-down to records |

| Garage | Vehicle portfolio, vehicle details, documents, sale/transfer actions |

Product invariants

• A pending OCR or import row never changes reports before user review; editable OCR candidate date and meter values become ledger data only after that confirmation.
• DIY work does not require a shop.
• Fuel, service, and expense places accept a direct name and editable address; no map/search result is required to save a record.
• Every service line item is independently searchable.
• Changing a vehicle default never rewrites historical currency or units.
• A vehicle photo is an optional verified private attachment, never a temporary photo-picker URI; it survives backup/restore and a selected vehicle transfer.
• Deleting a vehicle is explicit and destructive: the app shows its record, reminder, and copied-attachment counts with a backup recommendation before the final confirmation, then removes only that vehicle's local data.
• Full local-data erasure is separate from vehicle deletion. It previews vehicles, records, reminders, reusable templates/places, and copied attachments, then clears the on-device vehicle ledger and vault without deleting external backups or purchase entitlement.
• Expired Pro access never hides existing data or prevents raw export/backup.
• The app never represents user-entered intervals as manufacturer diagnosis.
• Optional income is a separate timeline event and exportable local record. It never reduces, offsets, or is presented as vehicle maintenance spend.
• Optional trips are manual and do not request background location. A trip's ending meter becomes an auditable local meter event; editing or deleting the trip updates that derived event atomically.
• Inspection templates are editable local input helpers; completed checklist records preserve their own copied labels and owner-entered results. They never claim to diagnose or certify vehicle safety.
• Remote sync is not configured in the shipped local-first build. Backup, restore, and vehicle transfer remain the cross-device data-ownership routes until a future explicit sync opt-in is implemented.