Landmark

The quarterly review is due and the only data is ticket counts. Ticket counts single out individuals. They do not show the system. Career conversations feel subjective with no shared evidence base. Landmark resolves both problems.

Landmark surfaces marker evidence alongside developer-experience outcomes. Guide assesses that evidence against your engineering standard. Landmark presents it and does not blame individuals.

What becomes possible

For Engineering Leaders

Demonstrate engineering progress and do not make individuals feel surveilled. See system-level trends that show direction. Tell whether culture investments work before the next budget cycle. Ground quarterly reviews in evidence rather than impressions.

• Team health dashboards that combine evidence, driver scores, and engineer voice
• GetDX snapshot trends and quarterly comparisons
• Practice pattern analysis that shows which skills the team exercises

For Empowered Engineers

See what your recent work demonstrates against the standard. See how the evidence accumulates over time. When Guide recommends a growth area, Landmark shows your proof of progress.

• Marker evidence that links GitHub artifacts to skill definitions
• Promotion readiness and growth timeline views
• Skill coverage analysis against standard markers

---

How Landmark Works

Audience Model

Audience	Views	Privacy
Engineer (own data)	evidence, readiness, timeline, coverage, sources, voice --email	Full individual detail
Manager (1:1 tool)	health, readiness, timeline, practiced, practice, voice --manager	Individual specificity for direct reports
Director (planning)	snapshot, practiced, practice, voice --manager	Aggregated team views

Commands

Organization

npx fit-landmark org show                    # Full organization directory
npx fit-landmark org team --manager <email>  # Hierarchy under a manager

Snapshots

npx fit-landmark snapshot list
npx fit-landmark snapshot show --snapshot <id> [--manager <email>]
npx fit-landmark snapshot trend --item <item_id> [--manager <email>]
npx fit-landmark snapshot compare --snapshot <id> [--manager <email>]

Evidence & Readiness

npx fit-landmark evidence [--skill <id>] [--email <email>]
npx fit-landmark marker <skill> [--level <level>]
npx fit-landmark readiness --email <email> [--target <level>]
npx fit-landmark timeline --email <email> [--skill <id>]
npx fit-landmark coverage --email <email>
npx fit-landmark practiced --manager <email>
npx fit-landmark practice [--skill <id>] [--manager <email>]

Engineer Data

npx fit-landmark sources [--email <email>]

This command lists the classes of activity rows that Landmark retains about an engineer. The view gives transparency to the engineer who asks what data the system holds.

Health

npx fit-landmark health [--manager <email>]
npx fit-landmark health [--manager <email>] --verbose

The default output is a compact table of drivers with one anchor per row. Pass --verbose for the full per-driver paragraph layout. That layout includes all percentile anchors, GetDX comments, and contributing-skill evidence.

Sample default output:

  Team — health view

  Drivers (6)
  ────────────────────────────────────────────────────────────
  #  Driver          Percentile  vs_org   More
  1  Quality         42nd        -10      +4 anchors via --verbose
  2  Reliability     n/a         n/a      -
  …

Engineer Voice

npx fit-landmark voice --manager <email>   # Themed team comments
npx fit-landmark voice --email <email>     # Individual comment timeline

All commands support --format text|json|markdown.

Prerequisites

• GetDX account with API access configured
• Map with the activity schema migrated (npx fit-map activity migrate)
• Standard data with drivers and markers authored in your capability YAML

Data Flow

Landmark reads from Map's activity layer:

1. organization_people for hierarchy and team slices
2. github_artifacts + evidence for marker analysis. Guide assesses artifacts against your standard's markers and writes results to Map
3. getdx_snapshots + getdx_snapshot_team_scores for quarterly outcomes
4. getdx_snapshot_comments for engineer voice

GitHub + GetDX → Map (ingest + store) → Landmark (present)
                       ↑                       ↑
              Guide (marker analysis)    Summit (recommendations)

Health works without Summit. It shows driver scores, evidence, and comments. Growth recommendations appear after you install Summit.

---

Getting Started

npm install @forwardimpact/landmark @forwardimpact/map
npx fit-map init                            # seed ./data/pathway/ with the starter standard
npx fit-landmark marker task-completion     # reference view — no Supabase required

The other Landmark commands (health, voice, snapshot, evidence, …) read from Map's activity layer. The per-persona guides below walk through that setup.

---