Desktop Helper Contract

Keep native helper work behind a thin local contract.

A future helper should not replace Chokmi's import workflow. It should only gather desktop context and hand off into the same response-import APIs used by the browser bridge and Excel add-in.

Architecture

Recommended contract

Three rules keep helper work portable, replaceable, and auditable inside the Chokmi operating record.

Do

Keep one canonical import path

  • Expose a local health endpoint so the web bridge can detect helper availability without guessing.
  • Hand off exported spreadsheet files or extracted sheet context into the same Chokmi import endpoints.
  • Use app-specific adapters behind the helper rather than leaking Numbers or Calc runtime assumptions into Chokmi core models.
source_surface: browser_upload | excel_addin | numbers_helper | libreoffice_extension
Anti-patterns

Do not do this

These three failure modes break the activation + evidence audit story. Avoid them in any future helper.

Avoid

Don't fork the workflow per app

  • Do not make Chokmi depend on one desktop runtime.
  • Do not fork the import workflow logic per spreadsheet app.
  • Do not hide the browser fallback path behind a helper requirement.
Get started

Activate trials faster. Defend every decision.

Talk to us about how Chokmi structures consent, eligibility, evidence, and country setup into one inspection-ready operating record.