Artifacts · One line of work

Proof you can hold.

One delivery line, Get Shipped, and every station on it leaves a real artifact behind: a map of the system, a verdict before anything ships, a record a person can read. This page shows those artifacts large, exactly as the tools render them. No mockups, no staged data, and where no honest visual exists, we say so instead of inventing one.

What this page gives you

The real artifacts one line of work leaves behind, exactly as the tools render them.

00 · The system map

What exists, before the boundary is drawn?

Before we govern a system we chart it: every layer, file and dependency, plus a guided tour a new engineer or an auditor can follow. This is that map, generated from our own codebase and shown exactly as the tool renders it.

Interactive knowledge graph of the getadvantage codebase: ten architecture layers connected by dependency edges, with a guided tour sidebar listing thirteen steps — A real map: our own codebase, 241 nodes, 522 edges, July 2026.

The same knowledge graph one level deeper: the analyze.ts file node selected, its import edges highlighted, and the file's recorded summary, tags and functions in the detail panel — The same map, one file deep: app/lib/analyze.ts selected, with what the mapper recorded about it.

Station 00 on the enterprise page →

01 · The controlled zone

Station 01 leaves its artifact in the repository itself: PROJECT-BRIEF.md, the boundary every model reads before it works. How it is drawn is on the methodology page.

02 · The verdict

Is this safe to ship?

Every change clears the same fixed checks before it goes live, and the run ends on a plain GO or NO-GO. This is a real run of the open-source gate, verbatim: a broken build stops the ship, and one warning is left for a person to eyeball.

$ npx getadvantage --build

┌──────────────────────────────────────────┐
│  Ship-Safe — is this safe to ship?        │
└──────────────────────────────────────────┘

Checks
  ✓ Dirty-tree guard — Working tree is clean — nothing unintended would ship.
  ✓ Secret scan — Scanned 11 tracked/staged file(s) — no leaked-secret patterns matched.
  ✓ Tracked .env file — No .env files tracked by git (gitignored local .env files are fine and are never read).
  ✓ Typecheck (tsc --noEmit) — TypeScript compiled with no type errors.
  ✗ Production build (npm run build) — The production build failed — fix it before shipping.
      > acme-storefront@0.1.0 build
      > node scripts/build.mjs
      Bundling acme-storefront for production…
      Build failed: entry module app/main.ts not found (referenced from build config).
  ✓ Schema-bump check — Skipped — no app/lib/server/db.ts with a SCHEMA_VERSION sentinel in this project.

Overview — what your app has (read-only)
  ✓ API surface map — 3 route(s) · 2 look gated (session or cron secret) · 1 mutate (write) · 0 mutate without any obvious gate.
      /api/contact  [POST]  auth-gated
      /api/cron/digest  [GET]  secret-gated (cron/shared)
      /api/health  [GET]  public (read-only)
  ✓ Agents & integrations map — 1 integration(s) detected.
      OpenAI — key: OPENAI_API_KEY  (1 file)
  ✓ Schedules & jobs map — 1 job(s) · 1 scheduled in vercel.json · 0 ungated · 0 cron route(s) not wired to a schedule.
      /api/cron/digest  [0 8 * * *]  gated (CRON_SECRET)
  ⚠ Project brief — No project brief at PROJECT-BRIEF.md.
      project brief is stale, run `ship-safe brief` to refresh.

Verdict
  ✓ 8   ⚠ 1   ✗ 1

  NO-GO — 1 blocking issue(s). Do not ship until these are clear.

Verbatim output of a real check --build run (v0.6.0) against a demo storefront project with a broken build. Nothing hand-written except the prompt line.

This verdict came from one command:

any repo · one command

npx getadvantage --build

you getthe same checks plus the full production build, ending on one plain GO or NO-GO.

The gate, in the open →

03 · The proof record

Who checked this, and what did the checks see?

Every run ends on a record: each check with what it found, then one verdict a person can read, on a page a CI comment or an auditor can link. This one is our own repository through the gate, ingested through the runs API and rendered by the shareable report page.

A run report page: verdict GO with exit code 0 for a ship-safe check run on the getadvantage repository, followed by the list of recorded checks with pass and warn states — A real record: our own repository through the gate, GO with two warnings, July 2026. Rendered exactly as the report page shows it.

How the record is made →

04 · The presence read

Once it ships, do the engines name you?

Get Found is the subordinate module that reads how AI assistants answer when your category comes up: named, missing, or misread. There is no screenshot here on purpose: the reading is live and belongs to each client, so a staged visual would not be a real artifact. The public reading behind it is documented in full.

The Get Found reading →

Want your work to leave artifacts like these?

Thirty minutes over video, directly with the founders. No obligation.

Book a call →Write to us instead