Skip to main content
← Apps

App

JAMARQ Atlas

The local dashboard for running the portfolio: repos, deploy readiness, evidence and plans.

In use

Began 2026-05-09 as Atlas; carried the Tenra name from 2026-06-02 to 2026-10-02; Hub folded in 2026-10-02; Tauri since 2026-10-04.

Why it was built

GitHub shows what happened. It does not show what that means for the work: what state a site is in, what the next action is, what is blocking it, what was decided, and what has been verified. Across a set of client sites and a suite of apps, that layer lived in notes and memory.

Atlas keeps that layer in one place on the machine. Its Dispatch side tracks whether a site can safely ship. Atlas maps the work, Dispatch tracks readiness, and a person decides what ships. Atlas records the evidence and never deploys, pushes or decides on its own.

At a glance

Began
2026-05-09
Status
In use
Runs as
Tauri desktop app for macOS over a Node sidecar
Folded in
Hub

What it does today

Built and working

Today and Needs you

One opening screen with the day's work and the items waiting on a person, so the next action is never buried in a list.

Repos

Read-only git status for every repository, with verification run in waves and the results kept as evidence.

Deploys

One row per site and one next action each. Read-only dry-run plans show what a deploy would do without doing it.

The Suite catalog

The contracts the apps share with each other, in one catalog, with a contract bundle that can be exported.

A command palette

Cmd+K reaches any place or action from any screen. Every command comes from one registry.

Backup you can rehearse

The Data Center backs up and restores the workspace, and a restore can be rehearsed before it is needed.

How it came to be

The development cycle

282 commits and 88 merged pull requests, as of 2026-10-05. Work went straight to the main branch until August 2026, when every change started going through a pull request.

  1. 2026-05-09

    Scaffold and a local-first first version, with Dispatch, GitHub intake, a verification center and a writing workbench on the same day.

  2. 2026-05-10 to 05-13

    Backup and restore, sync, a timeline, planning, reports, hosting runbooks and a review center.

  3. 2026-05-19 to 05-20

    Command centers for GitHub and Vercel.

  4. 2026-05-25

    First desktop build, on Electron.

  5. 2026-07-02

    A daily command center, a run builder, readiness boards and a decision center for boundaries.

  6. 2026-07-06 to 07-22

    Evidence import from connection proofs.

  7. 2026-08-20 to 08-21

    Read-only deploy dry-run planners for cPanel and Vercel.

  8. 2026-10-02

    Hub folded in as the Suite view. The name went back to JAMARQ Atlas.

  9. 2026-10-04

    A Tauri shell built beside Electron, then Keychain sign-in and a local signing identity. Electron removed. The app went from 313 MB to about 13 MB.

  10. 2026-10-04 to 10-05

    Interface pass: one command registry, six places plus Today, plain words, light, dark and Match Mac, autosave, Connect GitHub and Sign in with Vercel.

What was folded in

One app became part of this one

Earlier tools that did one piece of this job on their own. Their work moved here and their repositories were archived.

Hub

2026-05-21 to 2026-10-02

Hub held the contract catalog for the suite, across 99 commits as Hub by Tenra. The catalog became the Suite view and its proof scripts came across. The command center, the proof matrix and the fixture preview were left behind.

Where it stands

Real, and not yet

  • •The installed Tauri app, with GitHub and Vercel connections and every operator view, including Today, Repos, Deploys, Suite and the Data Center.
  • •Read-only dry-run plans for cPanel and Vercel deploys, and evidence imported from connection proofs.

Not built, or switched off

  • Dispatch execution is locked by design. Every runner step is a no-op, and a person does the deploy.
  • Two proof steps from the Hub fold were not yet verified as of 2026-10-05.
  • There is no hosted version. Atlas runs only on the Mac it is installed on.

How it is built

Under the hood

The pieces

Shell
Tauri desktop app for macOS over a Node sidecar
Stack
Vite, Node, SQLite
Data
SQLite in the app's folder on the Mac, nothing hosted
Sign-in
GitHub and Vercel tokens in the macOS Keychain
Size
About 13 MB, down from 313 MB on Electron
Never
Deploys, pushes or decides what ships. It only records the evidence

Works with

  • JAMARQ Registry

    The rental desk for a container yard: customers, units, quotes, dispatch and receivables.

  • JAMARQ Scout

    Finds local businesses worth a call, shows the evidence, and works each one as a deal.

  • JAMARQ Ledger

    Double-entry bookkeeping that stays on the machine, one self-contained book at a time.

  • JAMARQ Align

    Google Business Profile work across many clients and locations, plus a measure of whether AI assistants name a business.

  • JAMARQ Assembly

    The workbench where posts and documents are drafted, shaped, reviewed and approved.

  • JAMARQ Sentinel

    One case from a question to an evidence-weighted risk call, with a person deciding anything that leaves the machine.

  • JAMARQ Guardrail

    The approval inbox the other apps send their risky actions to.

The service behind this

Need a tool like this for your own work?

Describe the job it would do and what you use today. You will hear back within one business day.