Burrito’s Labs Indie Tech Outmost Studio
Professional Systems
Active development

FileAdapt

Focused browser tools that diagnose and repair files rejected by accounting, commerce, banking, and filing systems.

Category
Professional Systems
Platform
Web
Status
Active development

Make rejected files work without surrendering their contents.

Each tool explains supported problems, asks when meaning is ambiguous, and prepares a deterministic output in the browser. The original file remains untouched.

User value

From rejection to a usable file.

Understand the problem. Make the necessary choices. Prepare a compatible output locally.

01

See what failed

Plain-language diagnostics separate automatic repairs, required decisions, warnings, and blockers.

02

Keep files private

Source files, parsed records, diagnostics, and prepared outputs stay in the active browser session.

03

Leave with an output

The result is a corrected or rebuilt file plus a factual account of what changed and what remains uncertain.

FileAdapt home page introducing a local file diagnostic workflow and five specialized tools.View full size
One private workflow across five system-specific tools.

Features

Five focused tools.

Each utility targets one receiving system and states its limits.

  1. 01

    QuickBooks CSV

    Map transaction columns and normalize supported encoding, delimiter, date, number, and whitespace issues.

  2. 02

    Shopify product CSV

    Preserve unknown columns while repairing supported headers and constrained product values.

  3. 03

    Xero bank CSV

    Map bank statement data, confirm money direction, and prepare a supported import layout.

  4. 04

    Xero to NACHA

    Build one narrow domestic CCD credit batch and validate routing, records, totals, traces, and controls.

  5. 05

    Filing PDF

    Analyze compatibility and, with approval, rebuild pages for Odyssey or File & Serve workflows.

How it works

A clear path through file rejection.

The common journey stays consistent while each tool applies its own rules.

  1. 01

    Choose the system

    Start with the destination that rejected the file, not a generic converter.

  2. 02

    Select the file

    Read the CSV or PDF locally. The original remains unchanged.

  3. 03

    Review the diagnosis

    See what can be repaired, what needs a decision, and what the tool cannot resolve.

  4. 04

    Resolve ambiguity

    Confirm mappings, conventions, directions, or documented consequences when software cannot know.

  5. 05

    Prepare and validate

    Generate the output locally. Consequential ACH and PDF results receive an independent check.

In practice

The tools in practice.

QuickBooks CSV tool showing a ready diagnosis and corrected CSV download for fictional data.View full size

QuickBooks ready

A mapped transaction file is diagnosed, corrected, and prepared for separate import.

Shopify CSV tool showing preserved columns and a factual repair summary for synthetic product data.View full size

Shopify repair summary

Supported values are normalized while unfamiliar columns remain intact.

Xero bank CSV tool showing a corrected statement and import limitations.View full size

Xero import output

A signed Amount column is prepared with explicit disclosures about omitted or unmapped data.

FileAdapt ACH preflight showing fictional payments, routing checks, totals, and a locally validated result.View full size

ACH preflight

The supported CCD credit profile is checked for routing, totals, record structure, and controls.

Odyssey PDF tool showing independent checks on a rebuilt synthetic document.View full size

PDF validation

A rebuilt filing document is checked for geometry, fields, links, and rendered content.

Product demos

One workflow, end to end.

FileAdapt overview

60 sec

Product concept

Repair without guessing.

Compatibility work becomes safer when the software is narrow about what it knows.

01

Local by design

Useful diagnosis and repair do not require a server copy of the source file.

02

People decide meaning

Dates, number conventions, mappings, and money direction require a choice when they are ambiguous.

03

Specific beats universal

Each tool supports a stated workflow instead of promising conversion between every possible format.

Architecture

The file stays in the browser.

Tool logic remains separate from the anonymous commerce layer and remote infrastructure.

  1. 01Local source file
  2. 02System-specific parser
  3. 03Deterministic diagnostics
  4. 04Explicit user decisions
  5. 05Local output generation
  6. 06Independent validation and download

Strict privacy boundary

Remote services receive opaque wallet, checkout, tool, and operation identifiers, not file contents.

Deterministic core

No AI, OCR service, or probabilistic repair path is implemented.

Verified consequential output

Generated ACH and rebuilt PDF files are reparsed and checked before download.

Technology

Built deliberately.

Application

  • TypeScript
  • Astro 7
  • React 19
  • CSS

Runtime

  • Browser memory
  • Cloudflare Workers
  • Static assets

Services

  • Cloudflare D1
  • Stripe Checkout in test mode
  • HttpOnly wallet cookie

Validation

  • Vitest
  • Playwright
  • Synthetic fixtures
  • Local launch journeys

Development

Implemented, not yet publicly launched.

Five tools, the anonymous wallet, test-mode checkout, broad synthetic validation, and a local launch rehearsal are implemented. Production deployment and live payments are not confirmed.

Stage
Active development
Active tools
5
File processing
Browser-local
Payments
Test mode

Implemented

  • Three CSV repair workflows for QuickBooks, Shopify, and Xero
  • Narrow Xero-to-NACHA CCD credit generation and validation
  • Local PDF analysis and print-style rebuilding
  • Anonymous D1-backed credit wallet with recovery and idempotent entitlements
  • Synthetic unit, stress, database, mobile, cross-browser, privacy, and launch validation
  • Silent overview and tool media produced from fictional fixtures

Launch focus

Confirm the production deployment, live payment path, public domain, operator details, support contact, and final pricing before describing FileAdapt as available.

FileAdapt lab notes

The project, over time.

Notes about the thinking, architecture, development, and decisions behind this work.

  1. FileAdapt
    25 Aug 2026 · Draft

    From Native Recording to a Silent Media Library

    Product demonstration became a tested production system built from scripted journeys, synthetic fixtures, and explicit privacy checks.
  2. FileAdapt
    22 Aug 2026 · Draft

    Aligning the Public Identity Around FileAdapt

    The public name, product language, metadata, legal pages, and interface were brought together around one practical promise.
  3. FileAdapt
    21 Aug 2026 · Draft

    Rehearsing FileAdapt as One Product

    Twenty-six local journeys tested the five tools, wallet, checkout, entitlements, downloads, analytics, and privacy boundary together.
  4. FileAdapt
    11 Aug 2026 · Draft

    The First Recorded FileAdapt Application State

    The first visible repository state already records five tools, a privacy boundary, an anonymous wallet, and a substantial validation system.