GhostPost™ · Visibility Changes Everything™
See what became visible.
GhostPost creates visibility across a fragmented public job ecosystem. It independently observes the public job sources it is configured, technically able, and authorized to reach, and builds a dated, sourced record of what became visible over time.
Your systems record what you intended to publish. GhostPost observes what became visible.
Outside-in visibility
Most hiring technology is built inside-out: it records, distributes, or removes what an organization intended to publish. GhostPost looks the other way around.
Inside-out systems
Outside-in observation
A role can be distributed across several sources, duplicated, re-listed, changed, displayed differently, missing information, still visible after an organization intended it to be gone, or temporarily unavailable to observation. GhostPost records what it saw, where, and when.
One public ecosystem. One independent observation record.
GhostPost observes the sources it is configured, technically able, and authorized to observe. It does not claim visibility into the entire internet, and it says plainly which sources it could not read.
Monitor
Watch
Requirements
Evidence
Three evidence states. No fourth.
The taxonomy is fixed, and source readability is a separate axis: a source that could not be read is recorded as unread, not as an absence.
- Observed
- A source GhostPost successfully read showed this, at a recorded time.
- Stated absent
- The source was read and the posting stated nothing on this point.
- Can't determine
- The available evidence does not settle the question. GhostPost stops there.
THE LENS™ changes perspective — not the facts.
GhostPost is not a pile of raw observations. The same record becomes visible differently depending on who is looking and what they need to understand.
- One observation and evidence engine holds the record.
- THE LENS™ selects whose perspective is reading it — employer, staffing firm, compliance team, government reviewer.
- The Layer Ladder controls how far the reading goes: what happened, why it matters, what is missing, what is worth asking, and what the reader can do next.
- The evidence never changes with the Lens. Only what is surfaced, and what questions the evidence supports, change.
- A layer with nothing honest to say is left out rather than filled in.
See the difference between what was originally visible and what later became visible elsewhere.
Where an organization's own careers source and other public sources are both configured for observation, GhostPost can hold both timelines side by side.
- A role no longer visible on the organization's own source, still visible on a configured third-party source.
- A field or disclosure visible on one source and displayed differently on another.
- A dated record of what an organization's own source displayed at a given time.
- Whether public information drifted after publication, and when the drift was first observed.
GhostPost records what was observed. It does not determine who is responsible for a difference, an alteration, a repost, or a stale posting. It states, for example: “Observed no longer visible on this source as of [timestamp]” — never “the employer took it down.”
Who it's for
Market architecture
Existing technology categories address pieces of this problem from different directions. GhostPost focuses on independent, outside-in observation of the public job ecosystem.
| Capability | Legacy ATS / syndication | Internal equity / policy software | Generic web scraping | GhostPost™ |
|---|---|---|---|---|
| Outside-in public footprint observation | Inside-out distribution focus | Not built for this | Possible with custom development | Purpose-built |
| Field-level change history and provenance | Not a core function | Not a core function | Requires custom build | Built-in, timestamped |
| Historical change-window filtering | Not a core function | Not a core function | Requires custom build | Built into observation history |
| Evidence-first, non-judgmental records | Different function | Policy interpretation | Raw data only | Observed / Stated absent / Can't determine |
| Read-only enterprise API | Custom integration | Not a core function | Requires data engineering | Native, read-only by design |
Category comparison, not a competitor comparison. Other categories can be extended toward parts of this work; the difference is architectural direction and purpose.
What GhostPost does not do
This boundary is not a limitation. It is what makes the record usable as evidence.
- Determine whether an organization is compliant
- Determine whether a law or requirement applies
- Declare a violation, or that anyone is liable
- Provide legal advice or legal opinions
- Assign severity or risk
- Produce a score of any kind — no composite score, no 0–100, no letter grade, no ranking
- Assign, track, or execute remediation
- Track resolution or assign owners
- Remove postings or send takedown demands
- Run notice-to-cure clocks or enforce requirements
GhostPost observes and documents. Qualified professionals and the systems an organization already runs decide what the evidence means and what happens next.
Read-only by design
Downstream compliance, HR, legal, and governance systems consume the record through a versioned, key-authenticated, organization-scoped API.
- Every endpoint is a read. Nothing mutates the record, initiates collection, or charges.
- No remediation, assignment, resolution state, severity, or verdict is exposed — because none exists.
- Historical change-window filtering with ?since= returns the dated delta for a defined observation period.
- Workspace-scoped keys are issued and revoked by workspace managers.
GhostPost delivers the record. Your governance systems decide what happens next.
Bring independent observation to the systems you already run.
GhostPost is an independent evidence and observation layer between public job sources and downstream compliance, HR, legal, and governance systems. Tell us how your team would use the record.