Nav Center

Native macOS app for reviewing local job-application packages, generated artifacts, tracker status, interview prep, and confirmation-gated workflow actions.

Nav Center is local-first. It reads a workspace on disk, binds no public network service, and does not submit applications, send outreach, scrape job boards, upload private files, or mutate external accounts.

Status

This is an extracted public-ready source tree from a private workflow. The repository contains source code, tests, public docs, beta setup skills, release scripts, and a small synthetic sample workspace only. It does not include private resumes, application history, tracker databases, vault mirrors, generated PDFs, or local account data.

Requirements

• macOS 13 or later
• Swift 5.9 or later
• sqlite3 for tracker-backed views
• Optional: atsim for the confirmed ATS scan action
• Optional: NAV_CENTER_EXPORT_BIN for any future confirmed resume export action
• Optional: Codex Desktop app-server for the in-app Codex panel

Build

swift build
swift test
scripts/build-and-run.sh

The app bundle is staged at dist/Nav Center.app.

The bundle includes Contents/MacOS/navcenterctl for local setup, diagnostics, document import, package creation, and beta feedback support.

Workspace Layout

Installed builds use this app-owned workspace by default:

~/Library/Application Support/Nav Center/Workspace

For development or advanced testing, set NAV_CENTER_WORKSPACE_ROOT. When launching through the dev bundle script, set NAV_CENTER_INCLUDE_WORKSPACE_ENV=1 to embed that override in the staged app bundle:

NAV_CENTER_WORKSPACE_ROOT=/path/to/workspace NAV_CENTER_INCLUDE_WORKSPACE_ENV=1 scripts/build-and-run.sh

A workspace should look like this:

applications/
  2099-01-01_Example_Corp_Security_Engineer/
    posting.md
    Resume_2099-01-01_Example_Corp_Security_Engineer.md
    interview-prep.md
    artifacts/
      ats-report.json
master-resumes/
  master_primary.yaml
tracking/
  applications.sqlite
imports/
  originals/
  markdown/
feedback/

tracking/applications.sqlite is optional. When it is missing, Nav Center still scans package folders and labels them as package-only records.

Friends and Family Beta

See docs/BETA.md for install, onboarding, feedback, and uninstall guidance.

Codex Plugin Skills

Nav Center publishes its beta helper skills as a Codex plugin from this public repository. The marketplace plugin root is plugins/nav-center, which keeps the installable package limited to the skill manifests and skill files.

Install the Nav Center plugin marketplace for the Codex app with:

codex plugin marketplace add subdepthtech/nav-center

Then open Codex and enable the Nav Center plugin from the plugin marketplace. The plugin provides:

• nav-center-codex-setup: first-run setup, workspace preparation, document intake, master resume review, Codex connection checks, and paused automation setup.
• nav-center-beta-feedback: redacted beta feedback and diagnostic report drafting.

For development from a source checkout, install the same packaged skills directly with:

scripts/install-codex-skills.sh

Homebrew Install

Beta builds are distributed through the public subdepthtech/nav-center Homebrew tap:

brew tap subdepthtech/nav-center
brew install --cask nav-center

Do not pass the git@github.com:subdepthtech/homebrew-nav-center.git SSH URL unless the tester has SSH access configured for that repo. The one-argument tap command above uses GitHub over HTTPS.

For a private or local cask file generated during release prep:

brew install --cask /path/to/homebrew-tap/Casks/nav-center.rb

Upgrade with:

brew update
brew upgrade --cask nav-center

Uninstall the app with:

brew uninstall --cask nav-center

Remove the app and local Nav Center support files with:

brew uninstall --cask --zap nav-center

Release

Create a beta DMG with:

NAV_CENTER_VERSION=0.1.0-beta scripts/package-beta-dmg.sh

See docs/RELEASE.md for signing, notarization, and Homebrew cask steps.

Safety Model

• Package paths are normalized and constrained to applications/<package>/.
• Package previews only read allowlisted markdown, text, JSON, and HTML paths.
• Mutating package actions require explicit UI confirmation.
• Codex markdown edits require explicit sign-in and package-markdown edit approval.
• Generated binaries, PDFs, DOCX files, tracker databases, and local workspaces are ignored by default.

Release Readiness

See docs/PUBLIC_RELEASE_CHECKLIST.md before creating a public GitHub repository or release artifact.