About

We build the parts of software that have to survive an audit.

Greenbar Systems is the company behind Tahlk. Before we built a scribe for behavioral health and podiatry, we built the same kind of tamper-evident, local-first architecture for a different regulated problem — because that's the default we start from, not a feature we added for healthcare.

Not our first hash chain

The same integrity pattern, in a different regulated domain.

Greenbar Clearing

Local-first bank reconciliation

A SHA-256-hash-chained audit ledger with a role-gated maker/checker workflow — reconciled transactions are sealed the same way a signed clinical note is in Tahlk, and for the same reason: the record needs to prove it wasn't altered, not just claim it.

AccessSpec

Accessibility compliance, before code ships

A dashboard that catches WCAG issues at the spec and PR stage instead of after an app is built — the same instinct as Tahlk's compliance scope-determination work: do the compliance thinking before it's forced on you, not after.

The throughline: tamper-evident by construction, compliant by default, and honest about what's still a gap. Tahlk isn't a healthcare company bolting on security — it's this pattern applied to behavioral health and podiatry.

Why Tahlk

Why behavioral health and podiatry, and why local-first.

Behavioral health carries some of the strictest confidentiality law in healthcare — 42 CFR Part 2, state mental-health confidentiality statutes, the newer state consumer-health-data laws. Podiatry runs on high visit volume where documentation time is the bottleneck. Both needed a scribe that treats on-device transcription and a tamper-evident record as non-negotiable defaults, not a "trust us" cloud pipeline with compliance bolted on afterward.

What we won't compromise on

Principles, not features.

Local-first is the default, not an option

Audio and transcription stay on the device unless there's one deliberate, disclosed reason for something to leave it.

A record should be able to prove itself

Hash-chained, tamper-evident signing isn't a Tahlk-only idea — it's how we think a record should work anywhere it needs to survive scrutiny.

Say what's a draft and what's shipped

Compliance determinations, security controls, and roadmap items are labeled as what they actually are — see Compliance and Security for what that looks like in practice.

What's not on this page

We've kept this page to what we can back up: the architecture, the products, and the reasoning behind them. Team, location, and company history will be added here as those pages are finalized, rather than filled in with placeholder biography.