A
2- Added per day
- The strip’s intake chart — projects entering the index per day, with the trailing 7-day daily average shown beneath it (see Cadence).
- Added this week
- New projects a market gained over the trailing 7 days — a rolling window, not a calendar week. The large figure on each market tile.
C
3- Cadence
- New projects landing in the markets on the homepage board, per day: a daily average over seven complete days, and the figure under CADENCE in the footer. The week it averages is the one the homepage chart compares against: the seven complete days ending a week ago, not the seven the chart draws, so a single page cannot carry two different weekly averages. Today is excluded either way, because it is still filling and would drag an average down all morning.
- Correction
- A change made to a record by hand, as the correction log keeps it: the field, its value before or after, a written reason and who made it. The log is only ever added to, so a wrong correction is followed by another correction, never edited away.Corrections
- Coverage
- How much of the software market PulseGate holds, counted in projects — the figure under COVERAGE in the footer. It is a count, not a share: the total size of that market is not knowable, so no percentage of it is published.
E
1- Edition
- A monthly copy of what the index recorded for each record in it — liveness and the evidence behind it, platform type, pricing, category, identifier counts and dates — frozen once and never rewritten. When the method behind it changes, the month gains a new method version and the earlier one stays.Editions
F
3- First-seen basis
- How a record’s first-seen date was set: observed means this index saw the record then; backfilled means a backfill’s own record shows it wrote the date, or the date is older than the index itself, so we cannot vouch that this index saw the record then — read it as at best a lower bound on the project’s age; unknown means we hold a date and could not establish which. The API returns it as firstSeenBasis.The first-seen-basis method
- Freshness
- How long ago the newest entry in the index arrived — the figure under FRESHNESS in the footer. It is the age of the most recent arrival, not of the last refresh: nothing on this page reports when a listing was last re-checked.
- From the index
- One listing shown in full, so you can see what a complete one holds: one project from the selected market that has its own home on the web — not a store listing — plus a deep description, a logo and a preview. It is a sample, not a recommendation: the entry is drawn at random from the most-starred listings meeting that bar in the selected market, it changes with the market filter, and it is never sponsored and never a paid placement. Nothing about being shown here is a statement of quality.
G
3- Gaining / Cooling / Steady
- A market’s this-week flow versus the previous 7 days. Gaining (▲) means more projects cleared the gate than last week, Cooling (▼) fewer, Steady (■) about the same. It reads momentum, not size — a large market can be cooling while a small one gains.
- Gate
- PulseGate’s intake path: a project is discovered, verified against public evidence, then either listed or held for review. “Through the gate” means it cleared that path and entered the live index. There is no human editorial gate and no paid placement — but there is a quality bar.
- Gate flow
- How many projects cleared the gate in the current window — the “+N this week” on the homepage strip and the figure on each market tile. It measures arrivals, not total size (see Projects tracked).
I
2- Identity check
- Whether a store listing linked to a record belongs to the same project, judged by comparing listing titles: the record’s App Store and Google Play listings with each other, or an App Store, Google Play, Chrome Web Store, Microsoft Store or Firefox Add-ons listing with the one the record gives as the software’s address — which, compared with itself, counts as the same project. A record’s page counts its linked identifiers as “checked as the same project”, “checked as a different project”, “checked, undecided” (the check reached no decision, for instance because a title was missing) or “not checked” — which includes every identifier from anywhere else. A record holding more than 25 identifiers on one platform gets no count, and its page says why.
- Intake
- Newly discovered projects, or fresh qualifying evidence for ones already known, entering PulseGate’s tracked universe.
L
4- Listed
- A project that has cleared coverage rules and is eligible to appear on public surfaces.
- Live index scope
- The set of projects reflected by a count or list given the active filters. Filter-aware counts (Live indexed) shrink with market or language filters; global counts (Tracked, Projects tracked) stay constant.
- Live indexed
- Listed projects in the current filter scope. The headline figure on the homepage strip; it re-scopes whenever a market, language, or runtime filter changes.
- Live status
- The operational state of the platform, surfaced as the green “All systems operational” pill in the footer. Switches to amber when the health probe fails.
M
2- Market
- A top-level category of software — AI & ML, Design & Creative, Infrastructure, and so on. On the homepage every tile is a market; selecting one rescopes the strip, counts, and feeds to that slice. “All markets” is the unfiltered whole.
- Method version
- Some of what PulseGate publishes is decided by a written method — editions, liveness and the first-seen basis among them — and each method carries a version and the date it took effect. The checks that run on main fail for as long as a method’s files differ from the newest entry of its changelog, and /api/apps names the versions behind its answers in meta.methods.Methods and their versions
N
1- Newest through the gate
- The live feed of the most recently listed projects, newest first. It follows the active market filter — unlike the whole-gate rail, which ignores it.
P
1- Projects tracked
- The projects a visitor can actually reach — the visible pool, unaffected by the filters on the page. It is the figure in the footer and the homepage total. It is smaller than everything PulseGate holds: records held for review are tracked but not listed, and are not counted here (see Tracked, Listed).
R
1- Record
- What PulseGate holds about one project: its identifiers, liveness, category, pricing and dates. A listed record’s page, /apps/<slug>, is its permanent address and the one to cite; the API returns it as recordUrl.
T
3- The Wire
- The homepage news river: releases, launches, and version bumps clustered from independent public sources. It follows the active market filter.
- Topic
- A subject or event cluster built from independent public sources covering related software.
- Tracked
- A project that exists in PulseGate’s monitored universe — listed publicly or held for review.
V
1- Verified
- A word about intake, not a verdict on a project: nothing is listed without a public surface — a site, a repository or a store listing — that can be reached and re-checked. On a card, “unverified” means something else again: no liveness check has reached that listing yet.
W
2- Whole gate
- The live rail across the top of the homepage, labelled JUST INDEXED — everything clearing the gate in real time, across every market, independent of the filter below it.
- Window
- The time range used to display recent activity — new entries, updates, and freshness reflected in the visible counts.