Glossary — Vaethra

A–ZDefinitions

A B C D E F G H I K L M N O P R S T U V W

Analogue: A past event whose text is close to a current one, found by comparing the embeddings the Terminal stores for every record. Answers "has anything like this happened before"; it is a similarity of description, not a claim that the two events are connected.See also: semantic near-duplicate.
API key: The credential a programmatic client presents. A key belongs to a customer organisation, carries a tier (trial, standard, enterprise or internal), a set of scopes, its own rate limit and row cap, an optional expiry, and can be revoked at any time. Every request made with it is recorded against it. The Terminal and Atropos need none.See also: key scope, rate limit, dormant key, trial key.Used in API, data and licensing, Access control, Business continuity, Data Processing Agreement, Data protection, Incident response, Privacy, Security, Security architecture, Subprocessors
AtroposSystem 02: The cascade simulator. Names a subject, applies one of four severities, and walks the recorded dependencies outward to report what is exposed — hop by hop, with the channel and the evidence behind each. Reaches six hops by default; a complete cascade is available on request and is bounded by work rather than depth. Named for the Fate who cuts the thread.See also: cascade, hop, channel, share of dependence.Used in API, data and licensing, About, Access control, Atropos, Availability, Business continuity, Changelog, Commercial terms, Compliance, Data Processing Agreement, Eschaton, Live case, Methodology, Privacy, Privacy Policy, Security, Security architecture, Subprocessors, Support, System status, Terms of Use, Vaethra, Western Bulk and the Strait of Hormuz, April to August 2026

Backtest: A replay of history that asks whether signals preceded confirmed events more often than chance. Reconstructs what was visible on each past date using only what was known then, scores it against independently sourced ground truth, publishes two null baselines beside every result, and refuses to print a rate from fewer than ten scored signals.See also: null baseline, point-in-time, ground truth, verdict.Used in API, data and licensing, About, Commercial terms, Oracle, Questions, Security
Backtest region: The area a confirmed event is attributed to. A maritime region is a lane and claims events by distance from its chokepoint, over water only; a land region claims only events inside a declared boundary. Containment is tested first and wins, and an event that fits neither is left unmapped rather than guessed — a gap is honest, a mis-attributed event is fabricated ground truth.
Baseline: A series' own recent normal, against which a current reading is judged. There is no global threshold. For a route it is the median of its own recent finalised daily history; for an electricity grid, the median of the same hour on the same kind of day over recent weeks; for a mined series, a robust estimate of its own history. Nothing is judged against another entity's normal.See also: below normal, signal.Used in Changelog, Live case, Oracle, Terminal, Track record, Western Bulk and the Strait of Hormuz, April to August 2026
Baseline signal: A signal from an instrument that publishes slowly — port calls a few weeks behind, satellite dark-vessel shares about seven weeks behind — so it describes a recent past window rather than now. It corroborates a trend; it is lead-only and never fires an alert or drives a prediction on its own. five of the nineteen mined families are baseline.See also: nowcast signal, lead-only.
Below normal: A port or strait moving less traffic than its own baseline: a lag-adjusted median of its recent days against the median of its recent finalised months. Frequently the earliest visible sign of a closure, because vessels divert before anyone announces anything. Stale or thin data reads unknown, never critical.See also: watchboard level.Used in Terminal

Cascade: The set of consequences traced outward from a shock. Presented as an ordered list of exposures, each with the path that reached it, the channel it arrived through, the weakest evidence anywhere on that path, and the accumulated lag.See also: Atropos, hop, path confidence.Used in API, data and licensing, About, Atropos, Changelog
Category: The second half of a record's classification. Each of the eleven domains splits into named categories — 82 in all — and every record carries exactly one domain and one category. A source that does not fit extends the taxonomy first; it never adds an axis of its own.See also: domain.Used in Compliance, Data Processing Agreement, Eschaton, Methodology, Privacy, Privacy Policy, Trust centre
Channel: How a shock arrived, labelled on every hop. There are four: dependency (something relied on stopped), demand (a customer stopped buying), containment (they were inside the thing that was destroyed) and security (a standing commitment drew them in). Kept separate because they move at different speeds, carry different weight, and mean different sentences about the world.See also: dependency channel, demand channel, containment, security channel.Used in Atropos, Availability, Security
Chokepoint: A strait, canal or passage through which a disproportionate share of trade must pass — Hormuz, Suez, Bab-el-Mandeb, Malacca, Panama and others. Each is tracked against its own traffic baseline, and each is a region the backtest can score.See also: below normal, backtest region.Used in Live case, Oracle, System status, Western Bulk and the Strait of Hormuz, April to August 2026
Confidence: How much to trust a record, 0 to 1, set from its source class — an official publication highest, a single press report lowest — and distinct from severity, which says how bad the event is. On a cascade, path confidence is the product of the link confidences along the route.See also: source class, path confidence.Used in Methodology
Containment: The channel that walks location backwards. Facilities, companies and ports point at their country; a shock walked forward from a destroyed country would reach none of its own infrastructure, the one thing certainly destroyed. Atropos follows located-in, based-in, part-of and hosts in reverse, only for containment, and only when the shock is severe enough that the container really is gone.See also: channel.Used in Atropos, Incident response
Corroboration: Independent reports of the same event. Duplicates are collapsed rather than counted twice: the representative gains a count of the reports behind it, and the others remain reachable. In the pressure index an event from any source stronger than press counts in full, and an event known only from press counts for a fifth of that.See also: story collapse, representative report, source class.
Coverage: What the system watches, on what cadence and under which licence — and plainly, what it does not watch. 55 feeds across eleven domains, roughly 2,097 routes with a current reading. Published at /coverage from the same registry the feeds run from.Used in About, Availability, Coverage, Enterprise Service Addendum, Eschaton, Questions, Support, System status, Terminal

Demand channel: A shock transmitted by losing a buyer rather than a supplier. A revenue problem that plays out over quarters, weighted well below a dependency shock, and only counted when the lost customer was more than ordinary churn to the supplier. Commodities are markets, not customers, and cannot stop buying.See also: channel.
Dependency: A recorded relationship in which one entity relies on another, with a direction, a weight, a lag in days and the method that established it. A dependency is never assumed from a shared name.See also: link method, relation, graph.Used in API, data and licensing, About, Access control, Atropos, Changelog, Compliance, Data Processing Agreement, Oracle, Security architecture, Terms of Use, Trust centre, Vaethra, Vulnerability management
Dependency channel: The channel through which most of a cascade arrives: something the entity relied on stopped. How much of the failure passes on is a property of the relation kind, not of the edge — a supplier failing passes almost fully; a membership barely moves the whole.See also: transmission.
DocumentaryLink method: A relationship read out of published documents by a language model. Recorded only when the sentence asserts it explicitly, both endpoints already exist in the registry, and two independent publishers state it (or a structural or measured link already does, or a person accepts it); every such link keeps the passages it came from. Ranks below measured, structural and statistical evidence, and carries no cascade until a person has accepted it.See also: link method, superseded.
Domain: One of the eleven subject areas the record is split across: conflict, maritime, energy, hazard, food, health, economy, infrastructure, cyber, society and space. These are the names the API reports, so a filter in the Terminal and a field in a payload always agree.See also: category.Used in API, data and licensing, Access control, Methodology, Security, Terminal
Dormant key: An API key with no request recorded against it for 90 days. Flagged as dormant in the workspace so a customer can revoke what it no longer uses; nothing is revoked automatically.See also: API key.

Entity: Anything the system can track and connect. Seventeen kinds: country, port, chokepoint, region, commodity, energy node, cable, airspace, sector, organisation, currency, city, concept, facility, index, bloc and person. A person is its own kind because a person owns things rather than producing them.See also: graph, relation.Used in About, Changelog, Compliance, Live case, Security, Security architecture, Subprocessors, Trust centre, Western Bulk and the Strait of Hormuz, April to August 2026
EschatonSystem 04: Not started. A study of how religious traditions read the present moment — which prophetic claims circulate, where, and against which events. It adjudicates nothing.Used in About, Eschaton
Event record: The one shape every source is normalised into: a stable identifier, the publisher and its licence, the source's own record id and URL, one domain and one category, a severity from 0 to 1, a confidence, a lifecycle status, a location where the source gives one, the time the source published and the time Vaethra first saw it, and the source's own numbers preserved as they came. Provenance is mandatory: a claim that cannot be traced to its publisher is not admitted.See also: first seen, severity, confidence, event status.Used in Eschaton
Event status: Where a record is in its life: active, monitoring, resolved or historic. A state, not a judgement of importance; a historic record is still a record.
Evidence tier: How a record or a link was established. Two ladders, one per thing: a record carries a source class (six of them, from official down to press) and a link carries a method (five, from measured down to signal). Both are visible on everything and filterable everywhere.See also: source class, link method.Used in Security architecture, Terminal
Extract: A pre-built bulk file of records, built by the nightly run and served from object storage rather than generated on request, capped at 25,000 rows and available only to a key holding the exports scope. Sources whose licence forbids redistribution are left out. A build that did not finish is labelled failed and the previous file stands; a stale extract is called stale.See also: licence class, key scope.Used in Commercial terms, Data protection, Security architecture

Facts endpoint: The keyless endpoint every surface reads its published numbers from — the site at build time, the Terminal and Atropos at load. Each group is labelled derived (compiled from code) or measured (read from the database on request), and a measurement that fails is a null, never a guess. A figure on this site that disagrees with it stops the build.Used in Changelog
Feed: One source adapter on the registry — 55 in all — declaring its publisher, source class, licence class, cadence and any key it needs. Every run is logged with what it fetched and whether it succeeded, and the adapter's state after its last run is one of seven.See also: feed state, source class, licence class.Used in API, data and licensing, Changelog, Commercial terms, Coverage, Incident response, Live case, Methodology, Questions, Support, System status, Terminal, Vaethra, Western Bulk and the Strait of Hormuz, April to August 2026
Feed state: The one word that describes a feed after its last run. Live: the run succeeded in full. Degraded: it ran and delivered, but not everything it wanted. Paused: the backoff has parked it after repeated failures, a chosen state that delivers nothing. Failing: it ran and failed. Needs key: a required credential is not configured. Idle: it has not run yet. Parked: taken off the schedule on purpose, so it makes no request at all, and the row carries the date and the reason — not a fault, so it never makes ingestion degraded or failing. Health counts only live as healthy, and every state is shown by name.
First seen: When Vaethra first received a record — kept separate from when the source published it, because several providers publish hours to months after the fact. Conflating the two would make a stale feed look live.Used in Changelog
Forward ledger: The append-only record of what the signal miner actually emitted: one row per series per day, stamped with the as-of date of its inputs and the day it fired. It is the honest substrate for validation and it accrues from the day it started; a replay reconstructed after the fact is the weaker basis and is labelled as such.See also: backtest, point-in-time.

Graph: The recorded web of dependencies between entities. Roughly 78,000 links, of which about 9,980 are measured. Built in layers — structural rules, published measurements, learned co-movement, documentary extraction and transient signals — each labelled with its method.See also: link method, dependency.Used in API, data and licensing, About, Atropos, Business continuity, Changelog, Commercial terms, Coverage, Data protection, Live case, Methodology, Oracle, Security, Security architecture, Terms of Use, Vaethra, Western Bulk and the Strait of Hormuz, April to August 2026
Ground truth: Independently sourced confirmation that an event occurred, held in a ledger separate from the signals it scores, with the real event date, the source, a reliability tier and the region it maps to. Confirmed events only: machine-coded press is excluded as a claim rather than a confirmation.See also: backtest, reliability tier.Used in Track record

Hop: One step in a cascade. Each states the relation it followed, the channel it used, the share of the dependent's total dependence it carried, the evidence behind it and the lag it added.See also: cascade, share of dependence.
Horizon: In the backtest, the window after a signal within which a confirmed event counts as caught; an event on or before the signal's date never counts, whatever the horizon. In Atropos, the ceiling on accumulated lag a path may reach — "what breaks within a month".See also: lead time, lag.Used in Atropos, Track record

Integrity checks: A set of database checks, each written from a real failure that once passed every counter — a cursor that never advanced, a source restamping unchanged rows, a column null on every row. Run hourly, and the count of open findings is published on /status and in the facts endpoint.Used in Availability, Business continuity, Compliance, Incident response, Secure development, Security, System status, Vulnerability management

Key scope: What an API key may do, from a fixed list of seven: read events, entities, signals, backtest results, extracts or metadata, or write OSINT sightings. Every live route is classified against this list, and a route that is neither public nor classified is denied — a new route must be classified deliberately before any key can reach it.See also: API key.

Lag: The delay a dependency imposes, in days, accumulated along a path. Used to bound how far a shock can reach inside a stated horizon.See also: horizon.
Lead time: The days between a signal's as-of date and the confirmed event it preceded. Must be strictly positive to count — a signal on the day of the event predicted nothing — and is published as a distribution beside every backtest result.See also: horizon.Used in Track record
Lead-only: A signal that may corroborate but never lead: it can strengthen a case another signal makes and can never be the thing that fires an alert or drives a prediction. Baseline-class families are lead-only; so is any sighting whose only source is a tier-4 reporter.See also: baseline signal, reliability tier.
Licence class: What a source's terms allow Vaethra to do with its records: open (served and included in extracts), non-commercial (displayed with the licence attached, excluded from extracts) or internal (feeds the graph, the signals and the backtest; individual records are not republished). Every feed declares one, and every source is listed whatever its class.See also: feed, extract.Used in Security architecture
Link method: How a link was established, in strength order: measured, a published bilateral figure somebody else stands behind; structural, a rule asserted in the code; statistical, co-movement this system learned; documentary, a relationship a model read out of documents from two independent publishers; signal, a transient co-anomaly. When two methods assert the same relation between the same pair, only the strongest stays live.See also: measured, statistical, documentary, structural, signal, superseded.

MeasuredLink method: The strongest link method. Established from published trade, traffic or input–output figures, carrying the year they were measured. A measured weight is already a real share of the dependent's imports, so it is never rescaled.See also: link method.Used in Access control, Atropos, Availability, Commercial terms, Compliance, Data Processing Agreement, Data protection, Enterprise Service Addendum, Methodology, Oracle, Security, Security architecture, System status, Terms of Use, Track record, Trust centre, Vaethra, Vulnerability management
Mitigation: A substitution or a hedge: a relation that softens a shock rather than spreading it. Cargo diverts to a port in range; a hedge absorbs a price move. Handled separately from dependencies and never walked as a path.See also: substitution.Used in Business continuity, Compliance

Nowcast signal: A signal that describes conditions now. Each family declares how fresh its newest observation must be to qualify; a reading older than that means the feed stopped, not that the world went quiet, and is not mined. fourteen of the nineteen mined families are nowcast.See also: baseline signal.
Null baseline: A deliberately naive model a result must beat to mean anything. The backtest publishes two beside every result: an always-flag baseline, which flags every day, and a shuffled baseline, which scores the same signals in random order over two hundred draws. Atropos's ordering test uses its own pair — a random ordering, and a "big things move most" model that ranks the same entities by how much they normally move.See also: backtest, verdict.

Observation: One numeric time-series point: an entity, a metric, a time, a value and its source. Emitted by adapters — port calls, prices, grid load, vessel speeds, river discharge — and read back by the signal miner and the co-movement learner. One shape, so no adapter redeclares it.Used in About, Changelog, Compliance, Live case, Methodology, Oracle, Questions, Vaethra, Western Bulk and the Strait of Hormuz, April to August 2026
Operator dashboard: The staff plane: where an operator administers organisations, invitations and access requests. A separate application on a separate hostname, with accounts, roles and an append-only record of every administrative action. Never touched by the public products.See also: workspace.
OracleSystem 03: In development. The prediction layer, which will turn signals into forecasts carrying a published accuracy record from day one.Used in About, Changelog, Eschaton, Live case, Oracle, Vaethra, Western Bulk and the Strait of Hormuz, April to August 2026
OSINT sighting: A geolocated report of a vessel or a facility from an open-source reporter, kept with the reporter's handle and reliability tier. Warships and merchant traffic are separated because they answer different questions. A sighting whose only source is a tier-4 reporter is a lead and may be shown, but may never drive a prediction on its own.See also: reliability tier, lead-only.

Path confidence: The product of the link confidences along a cascade path. A cascade also reports the weakest method anywhere on the path, which is the honest ceiling on how much the result can be trusted.See also: cascade.
Point-in-time: Reconstructing what was knowable on a past date, using only data available then. Prevents a backtest from quietly using the future; the count of violations is published with every run and must be zero.See also: backtest.Used in Business continuity, Compliance, Data Processing Agreement, Enterprise Service Addendum, Oracle
Pressure: The 0–100 index of how loud the world is today. Built from the last day's high and critical events, weighted by evidence, with each domain contributing on a diminishing curve so breadth of stress counts more than volume in any one feed, plus the stress on routes under watch. Published with a band that shows what the number would be if uncorroborated press were discarded, or trusted fully.See also: pressure band, methodology.Used in API, data and licensing, Methodology, Terminal
Pressure band: The word for a pressure reading: CALM below 25, ACTIVE from 25, ELEVATED from 45 and SEVERE from 70. A different scale from an event's severity, kept in one shared table so every surface prints the same word for the same number. Ninety days of daily peaks are kept beside it.See also: pressure.
Provenance: On every record: the publisher, its licence, the source's own record id, the URL where one exists and the time of retrieval. On every link: the method that established it and, for a documentary link, the passage. The Terminal is public, so every claim on screen must be traceable to who made it.Used in About, Data protection, Privacy Policy
Public paths: The fifteen paths of the API that answer without a key — health, status, uptime, the accuracy record, the published figures, the documentation and the like — so the service can be monitored and its claims verified without buying it.See also: API key.

Rate limit: 600 requests per minute per key on Teams and 6,000 on an enterprise agreement, each enforced per key at the edge by its own limiter; keyless callers are limited per address at the standard rate. Responses carry the rate applied in their headers.See also: row cap, API key.Used in Access control, Commercial terms, Privacy Policy, System status, Terms of Use
Relation: The kind of a link — twenty-five in the vocabulary. Structural ones express dependency (supplies, transits, produces, hosts, owns, located-in and the rest); causal ones carry a direction of effect (raises, lowers, strengthens, weakens); financial ones couple without trade (insures, finances, flags). Some invert the sign of a shock: a substitute absorbs it, a competitor gains from it.See also: dependency, transmission.Used in Atropos, Changelog
Reliability tier: How far to trust a reporter, on one 1-to-4 scale shared by OSINT sightings and ground truth: 1 for verified geolocation practice, 4 for a state-aligned channel. Travels with every row.See also: OSINT sighting, ground truth.
Representative report: The one report that stands for a collapsed story: the most severe, then the earliest seen. It carries the count of reports behind it, and each of those keeps its own record, provenance and place in every export.See also: story collapse.
Row cap: At most 5,000 rows in one response, on every key. Bulk access is an extract, not a larger page.See also: extract.Used in Access control

Security channel: A standing commitment — a defence pact, a freedom-of-navigation posture — that engages only above a severity threshold. An invasion draws a guarantor in; a port strike does not. What passes onward from an engaged guarantor is damped hard, because a country at war goes on exporting, and the channel label stays on the path so the reader knows which kind of claim they are looking at.See also: channel.
Semantic near-duplicate: A report whose text embedding is nearly identical to an earlier one's, marked as a copy of the first report within a recent window. The representative gains a duplicate count; nothing is deleted. Separate from story collapse, which uses literal rules and is what the feed depends on.See also: story collapse, analogue.
Severity: How bad. On a record: a normalised 0-to-1 operational consequence, mapped from each source's native scale so a filter of "at least high" means the same thing everywhere, and labelled five ways from info to critical. In Atropos: one of four named levels — disrupted, halved, halted, destroyed — with a vocabulary per kind, because a currency collapses rather than being destroyed and a strait is closed rather than halted.Used in Atropos, Compliance, Enterprise Service Addendum, Incident response, Live case, Methodology, Support, Terminal, Track record, Vaethra, Vulnerability management, Western Bulk and the Strait of Hormuz, April to August 2026
Share of dependence: The fraction of a dependent's total inbound dependence that one link represents, computed within the pool of links of the same relation into the same target. It is what makes a large diversified economy shrug and a single-supplier economy collapse from the same rule. Measured links use their published share directly; asserted ones are damped when the pool is thinly mapped, so one known supplier does not read as the only one.See also: hop, Atropos.
Signal: A series diverging from its own baseline by enough, for long enough, on enough history: a direction (drop or surge), a z-score, the size of the move, the number of samples behind the baseline and the freshness of the newest observation. Mined inside the database every fifteen minutes across nineteen metric families, and kept separate from confirmed events everywhere, because most signals amount to nothing. As a link method, the weakest tier: a transient co-anomaly, rebuilt from scratch nightly.See also: nowcast signal, baseline signal, link method.Used in Atropos, Coverage, Oracle, Terminal, Track record, Vaethra
Source class: What kind of publisher a record comes from, which sets its confidence. Six classes, strongest first: official (a government or intergovernmental body), research (a coded, peer-reviewed or research-grade dataset), sensor (satellite, vessel or network telemetry), model (model output rather than observation), aggregator (collected from upstream publishers) and news (press reporting — a lead to verify, not confirmed fact).See also: confidence, evidence tier.Used in Methodology
StatisticalLink method: A link learned from two series reliably moving together over time, on weekly deviations from a trailing baseline rather than levels. It must hold in both halves of the history and must beat the same-day correlation when it claims a lead; two series of the same metric are never compared. Rebuilt every three hours. It carries a cascade only once a review has found a plausible mechanism for it, and a co-movement never extends a cascade beyond its first step. Never presented as a flow of anything: a correlation is not a pipe.See also: link method.Used in About, Atropos, Coverage, Terms of Use, Track record
Story collapse: One row per story, not one per report. Reports are collapsed by three literal rules a reader can check: the same article coded more than once (news sources only, with a ceiling on how many reports one URL may carry), the same source telling the same headline again on the same day, and — for four kinds of physical incident — different providers reporting the same place at nearly the same time. No model and no similarity threshold in the feed's own collapse. Runs every five minutes.See also: representative report, corroboration, semantic near-duplicate.
StructuralLink method: A link asserted by a rule in the code from physical or institutional fact — this facility sits in this country, this strait serves these routes, every economy burns fuel. Above a signal, below every other method.See also: link method.Used in About, Atropos, Eschaton, Methodology, Privacy
Substitution: A port-to-port link recording that cargo diverts to another port in range when one closes, decayed by distance and by the smaller port's capacity to absorb it. A mitigation: it softens a shock rather than spreading it.See also: mitigation.
Superseded: A weaker link kept but marked, after a stronger method established the same relation between the same pair. Nothing is deleted, so the disagreement stays visible, and the mark is recomputed in both directions on every rebuild: a superseded link comes back the moment the stronger one disappears.See also: link method.

TerminalSystem 01: The observation layer, and the live product. Every located disruption on one screen with its provenance attached, free, with no account.Used in API, data and licensing, About, Access control, Availability, Business continuity, Changelog, Commercial terms, Compliance, Coverage, Data Processing Agreement, Data protection, Eschaton, Live case, Methodology, Oracle, Privacy, Privacy Policy, Questions, Security, Security architecture, Subprocessors, Support, System status, Terminal, Terms of Use, Vaethra, Western Bulk and the Strait of Hormuz, April to August 2026
Transmission: How much of an upstream failure passes downstream, as a property of the relation kind rather than of the individual link. Physical dependency carries the most; financial and pricing couplings less; membership and location the least. Getting this wrong in the generous direction is how a simulator ends up claiming everything affects everything.See also: relation, dependency channel.Used in Atropos, Compliance, Data Processing Agreement, Eschaton
Trial key: A real API key on the trial tier: every documented endpoint, the standard rate limit and row cap, time-boxed by an expiry date. Issued for evaluation, at no charge and with no invoice.See also: API key.Used in Access control, Commercial terms

Universal need: A commodity every economy consumes — fuel, grain, fertiliser, medicines, chips — for which a country absent from the published producer list is recorded as importing. A deduction from published shares, restricted to commodities where non-production implies dependence; photoresist is deliberately not one.See also: structural.
Uptime record: One sample every five minutes, written by the scheduled run and kept for 400 days, read back as a daily rollup. Measured from inside the system, so a total outage records no sample rather than a failed one; a gap is shown as a gap, and the expected-versus-actual sample count is published so a reader can see it. Not a service-level agreement.Used in System status

Verdict: The backtest's own conclusion on a run, in five forms: beats null, by a stated margin; does not beat null; uninformative, because flagging every day already scores so well the test cannot decide; insufficient, fewer than ten scored signals; or no evidence, no qualifying signals in the window. Every surface reads the stored verdict rather than recomputing it.See also: backtest, null baseline.Used in Track record

Watchboard: The panel tracking ports, chokepoints and electricity grids against their own baselines. Routes and grids are counted separately, because a grid running hot is not a shipping route running below normal.See also: watchboard level, below normal.Used in Methodology
Watchboard level: The state of a tracked entity, in six words: normal, elevated, strained, disrupted, critical or unknown. A state rather than a change, and deliberately a different vocabulary from event severity. Unknown means the data was too stale or too thin to judge, and is reported as such rather than as critical.
Workspace: The customer plane: where the staff of an organisation that licenses the API administer keys and members. Accounts with a second factor, roles enforced by the database, and an append-only record of every administrative action with the actor, the time and the reason. Separate from the public products, which have no accounts.See also: operator dashboard, API key.Used in API, data and licensing, Access control, Changelog, Commercial terms, Compliance, Data Processing Agreement, Data protection, Incident response, Privacy, Privacy Policy, Security, Security architecture, Subprocessors, Terms of Use