@prosopo/types-database 5.4.0 → 5.5.0

package/.turbo/turbo-build$colon$cjs.log

@@ -1,5 +1,5 @@
 
-> @prosopo/types-database@5.4.0 build:cjs
+> @prosopo/types-database@5.5.0 build:cjs
 > NODE_ENV=${NODE_ENV:-development}; vite build --config vite.cjs.config.ts --mode $NODE_ENV
 
 ViteCommonJSConfig: .
@@ -43,9 +43,9 @@ dist/cjs/types/userAgent.cjs         0.00 kB │ gzip: 0.02 kB
 dist/cjs/types/bannedDomain.cjs      0.23 kB │ gzip: 0.16 kB
 dist/cjs/types/spamEmailDomain.cjs   0.25 kB │ gzip: 0.17 kB
 dist/cjs/types/captcha.cjs           0.99 kB │ gzip: 0.27 kB
-dist/cjs/types/index.cjs             2.42 kB │ gzip: 0.48 kB
-dist/cjs/index.cjs                   2.52 kB │ gzip: 0.53 kB
-dist/cjs/types/client.cjs            6.94 kB │ gzip: 1.52 kB
-dist/cjs/types/provider.cjs         28.98 kB │ gzip: 4.55 kB
+dist/cjs/types/index.cjs             2.50 kB │ gzip: 0.49 kB
+dist/cjs/index.cjs                   2.60 kB │ gzip: 0.54 kB
+dist/cjs/types/client.cjs            8.03 kB │ gzip: 1.67 kB
+dist/cjs/types/provider.cjs         29.10 kB │ gzip: 4.57 kB
 
-✓ built in 67ms
+✓ built in 46ms

package/.turbo/turbo-build$colon$tsc.log

@@ -1,8 +1,8 @@
 
-> @prosopo/types-database@5.4.0 build:tsc
+> @prosopo/types-database@5.5.0 build:tsc
 > tsc --build --verbose
 
-10:39:37 PM - Projects in this build: 
+11:40:55 AM - Projects in this build: 
     * ../../dev/config/tsconfig.json
     * ../locale/tsconfig.json
     * ../util/tsconfig.json
@@ -16,29 +16,29 @@
     * ../user-access-policy/tsconfig.json
     * tsconfig.json
 
-10:39:37 PM - Project '../../dev/config/tsconfig.json' is up to date because newest input '../../dev/config/src/vite/NodejsPolarsNativeFilePlugin.ts' is older than output '../../dev/config/tsconfig.tsbuildinfo'
+11:40:56 AM - Project '../../dev/config/tsconfig.json' is up to date because newest input '../../dev/config/src/vite/vite.backend.config.ts' is older than output '../../dev/config/tsconfig.tsbuildinfo'
 
-10:39:37 PM - Project '../locale/tsconfig.json' is up to date because newest input '../locale/src/translationKey.ts' is older than output '../locale/tsconfig.tsbuildinfo'
+11:40:56 AM - Project '../locale/tsconfig.json' is up to date because newest input '../locale/src/translationKey.ts' is older than output '../locale/tsconfig.tsbuildinfo'
 
-10:39:37 PM - Project '../util/tsconfig.json' is up to date because newest input '../util/src/url.ts' is older than output '../util/tsconfig.tsbuildinfo'
+11:40:56 AM - Project '../util/tsconfig.json' is up to date because newest input '../util/src/url.ts' is older than output '../util/tsconfig.tsbuildinfo'
 
-10:39:37 PM - Project '../logger/tsconfig.json' is up to date because newest input '../logger/src/logger.ts' is older than output '../logger/tsconfig.tsbuildinfo'
+11:40:56 AM - Project '../logger/tsconfig.json' is up to date because newest input '../logger/src/index.ts' is older than output '../logger/tsconfig.tsbuildinfo'
 
-10:39:37 PM - Project '../util-crypto/tsconfig.json' is up to date because newest input '../util-crypto/src/types.ts' is older than output '../util-crypto/tsconfig.tsbuildinfo'
+11:40:56 AM - Project '../util-crypto/tsconfig.json' is up to date because newest input '../util-crypto/src/types.ts' is older than output '../util-crypto/tsconfig.tsbuildinfo'
 
-10:39:37 PM - Project '../types/tsconfig.json' is up to date because newest input '../types/src/types.test-d.ts' is older than output '../types/tsconfig.tsbuildinfo'
+11:40:56 AM - Project '../types/tsconfig.json' is up to date because newest input '../types/src/types.test-d.ts' is older than output '../types/tsconfig.tsbuildinfo'
 
-10:39:37 PM - Project '../common/tsconfig.json' is up to date because newest input '../common/src/tests/utils/batches.unit.test.ts' is older than output '../common/tsconfig.tsbuildinfo'
+11:40:56 AM - Project '../common/tsconfig.json' is up to date because newest input '../common/src/error.ts' is older than output '../common/tsconfig.tsbuildinfo'
 
-10:39:37 PM - Project '../api-route/tsconfig.json' is up to date because newest input '../api-route/src/index.ts' is older than output '../api-route/tsconfig.tsbuildinfo'
+11:40:56 AM - Project '../api-route/tsconfig.json' is up to date because newest input '../api-route/src/apiRoutes.ts' is older than output '../api-route/tsconfig.tsbuildinfo'
 
-10:39:37 PM - Project '../redis-client/tsconfig.json' is up to date because newest input '../redis-client/src/index.ts' is older than output '../redis-client/tsconfig.tsbuildinfo'
+11:40:56 AM - Project '../redis-client/tsconfig.json' is up to date because newest input '../redis-client/src/index.ts' is older than output '../redis-client/tsconfig.tsbuildinfo'
 
-10:39:37 PM - Project '../api/tsconfig.json' is up to date because newest input '../api/src/tests/apiHarness.ts' is older than output '../api/tsconfig.tsbuildinfo'
+11:40:56 AM - Project '../api/tsconfig.json' is up to date because newest input '../api/src/index.ts' is older than output '../api/tsconfig.tsbuildinfo'
 
-10:39:37 PM - Project '../user-access-policy/tsconfig.json' is up to date because newest input '../user-access-policy/src/ruleRecord.ts' is older than output '../user-access-policy/tsconfig.tsbuildinfo'
+11:40:56 AM - Project '../user-access-policy/tsconfig.json' is up to date because newest input '../user-access-policy/src/transformRule.ts' is older than output '../user-access-policy/tsconfig.tsbuildinfo'
 
-10:39:37 PM - Project 'tsconfig.json' is out of date because output file 'tsconfig.tsbuildinfo' does not exist
+11:40:56 AM - Project 'tsconfig.json' is out of date because output file 'tsconfig.tsbuildinfo' does not exist
 
-10:39:37 PM - Building project '/home/runner/work/captcha/captcha/packages/types-database/tsconfig.json'...
+11:40:56 AM - Building project '/home/runner/work/captcha/captcha/packages/types-database/tsconfig.json'...
 

package/.turbo/turbo-build.log

@@ -1,9 +1,9 @@
 
-> @prosopo/types-database@5.4.0 build
+> @prosopo/types-database@5.5.0 build
 > npm run build:cross-env -- --mode ${NODE_ENV:-development}
 
 
-> @prosopo/types-database@5.4.0 build:cross-env
+> @prosopo/types-database@5.5.0 build:cross-env
 > vite build --config vite.esm.config.ts --mode production
 
 ViteEsmConfig: .
@@ -48,9 +48,9 @@ dist/_virtual/_rolldown/runtime.js   0.04 kB │ gzip: 0.06 kB
 dist/types/bannedDomain.js           0.22 kB │ gzip: 0.17 kB
 dist/types/spamEmailDomain.js        0.23 kB │ gzip: 0.17 kB
 dist/types/captcha.js                0.82 kB │ gzip: 0.25 kB
-dist/types/index.js                  1.60 kB │ gzip: 0.38 kB
-dist/index.js                        1.67 kB │ gzip: 0.40 kB
-dist/types/client.js                 6.79 kB │ gzip: 1.56 kB
-dist/types/provider.js              27.83 kB │ gzip: 4.52 kB
+dist/types/index.js                  1.65 kB │ gzip: 0.39 kB
+dist/index.js                        1.72 kB │ gzip: 0.42 kB
+dist/types/client.js                 7.86 kB │ gzip: 1.71 kB
+dist/types/provider.js              27.95 kB │ gzip: 4.54 kB
 
-✓ built in 169ms
+✓ built in 68ms

package/CHANGELOG.md

@@ -1,5 +1,90 @@
 # @prosopo/types-database
 
+## 5.5.0
+### Minor Changes
+
+- af267c2: Web Bot Auth verifier and an authenticated frictionless flow for pre-verified agents.
+  
+  **`@prosopo/web-bot-auth`** — a new package: an RFC 9421 HTTP Message Signatures verifier built on `@noble/curves/ed25519`, with no Cloudflare dependency. It parses `Signature-Agent` in both its bare-string and dictionary forms, resolves the signer's JWKS at `/.well-known/http-message-signatures-directory` honouring the response's cache-control TTL, and verifies the Ed25519 signature over the RFC 9421 signature base.
+  
+  **Provider fast path.** `/captcha/frictionless` returns `captchaType: authenticated` when a non-`deferToVerify` `AccessPolicyType.Allow` rule matches the request's user scope, and writes a session with `serverChecked: false`, `agent: true` and the issuing IP frozen for verify-time binding. Decrypt, bot score and the decision machine are all skipped. A verified `Signature-Agent` is one way to qualify — the userScope gains a `webBotAuthAgent` field, set only when signature verification succeeded so a rule scoped to a signer can never be matched by a spoofed header — but an IP CIDR, JA4, user agent, ASN or country rule qualifies the same way. A `Block` or `Restrict` on the same match set always wins, because severity outranks Allow.
+  
+  **`/client/authenticated/verify`.** A separate router with mandatory IP binding — the operator must forward the client IP (`API.AUTHENTICATED_IP_REQUIRED`) and it must match the one the session was issued to (`API.AUTHENTICATED_IP_MISMATCH`), so a leaked token cannot be replayed from elsewhere. Single use is enforced through `serverChecked`, and `captchaType` is checked so an ordinary captcha token cannot be redeemed on this route. `clientSessionId` correlation goes through the same `isClientSessionMismatch` helper as pow / image / puzzle, so the authenticated path cannot drift from the others.
+  
+  **Surface.** `AccessPolicyType.Allow` and `CaptchaType.authenticated`; `webBotAuthAgent` on the user scope (indexed, normalised at parse time to a lowercase scheme+host with no trailing slash); `Session.agent` / `Session.webBotAuthAgent` for the Traffic view's "pre-verified pass" filter; `submitAuthenticatedCaptchaVerify` on `ProviderApi` and the matching branch in `@prosopo/server.verifyProvider`; `AuthenticatedBadge` and a dispatch branch in `procaptcha-frictionless`.
+  
+  Three fixes the new end-to-end coverage turned up, each of which broke the flow outright:
+  
+  - `ipMatchesSession` compared the operator's parsed IP against the session's composite halves with `===`. A session read back from Mongo carries BSON (`Decimal128`, or `Long` on pre-migration records), not the `bigint` the type claims, so the comparison was false for every session that had been through the database — every legitimate redemption was rejected as `API.AUTHENTICATED_IP_MISMATCH`. Both halves are now normalised before comparison, and an unparseable half fails closed rather than defaulting to `0n`, so garbage still cannot match garbage.
+  - `serverChecked` was never written onto the authenticated session, so "never set" and "consumed" were distinguishable only by an absence. It is now written as `false` at issuance.
+  - `serverChecked` was missing from `SESSION_PROJECTION`. Left out, the single-use check reads `undefined` and an authenticated token verifies an unlimited number of times.
+
+### Patch Changes
+
+- 929d99b: Default `trafficFilter.abuserScoreThreshold` to 0.2.
+  
+  The mongoose default was `0`. The abuser score runs 0..1 with 0 meaning "clean", so a `0` threshold applies the `abuser` category to every IP carrying any non-zero score, which is the widest the field can be set. A site that had never opened the traffic filter got that by default.
+  
+  `trafficFilterAbuserScoreThresholdDefault` moves from 0.5 to 0.2 and `@prosopo/types-database` now reads it instead of its own literal, so the zod default, the mongoose default and the provider's runtime fallbacks (`checkTrafficFilter`, `enrichDnsEvent`) all resolve to one number.
+  
+  `trafficFilter` is optional on `ClientSettingsSchema` and no create-site path sends one, so the mongoose default is what a new site key actually gets — the zod default only applies once a caller supplies a `trafficFilter` object.
+  
+  Existing sites keep whatever value is stored; only records with no value are affected.
+- b2183f9: Fix the client-list poll, which has never carried site settings to a provider.
+  
+  `getUpdatedClients` read `record.sites.siteKey` off the portal's `accounts` documents, where `sites` is an array. That property does not exist on an array, so every record came back as `{ account: undefined }`. `updateClientRecords` upserts filtered on `account`, so a whole poll's worth of sites matched nothing, inserted, and collapsed into a single `account: null` row that each run overwrote. An `as ClientRecord` cast on the mapping is what kept tsc quiet about it.
+  
+  Observed on a production node: `GetClientList` completing every 2 minutes with `clientRecords: 1247`, one `account: null` row in `clients`, and 1,610 site keys still holding settings the portal had changed. Direct registration via the admin `SiteKeyRegister` endpoint was the only path actually updating providers.
+  
+  - `getUpdatedClients` now flattens account → sites and emits one record per site, applying the `updatedAt` cutoff per site rather than relying on the document-level match. The account's `tier` is projected and attached; it was previously projected as `sites.tier`, which does not exist, so `tier` was undefined too.
+  - The cast is gone. `getUpdatedClients` returns `IUserDataSlim[]` and `updateClientRecords` accepts it — these are plain objects built from portal documents, never mongoose Documents, and the declared types now say so.
+  - `updateClientRecords` drops records with no account and logs the count instead of upserting them, so a future mapping bug cannot silently overwrite one row with every client's settings.
+  
+  Adds an integration test covering the flattening, the per-site cutoff, and the active-user filter; it fails with `account: undefined` against the old mapping.
+- 27f525e: Stop the puzzle difficulty ladder silently replacing a site's own puzzle settings.
+  
+  An escalated puzzle session samples its render settings from a difficulty band, and a sampled band sets every knob — decoy count, edge darkness, hole darken, piece scale and tolerance. While that is happening the site's configured `puzzle` block and `puzzleTolerance` are not consulted at all. For a site using escalation that is the intent; for a site that deliberately configured an easier puzzle it means the settings it saved never render, which reads as "my settings aren't being saved".
+  
+  Two changes:
+  
+  `puzzleMaxDifficulty` is a new client setting — the puzzle counterpart to `imageMaxRounds`. It caps how far automatic escalation may climb the ladder, and `0` pins the site to level 0, the documented "nothing escalated" case where the session is left bare and the site's own settings render every time. It defaults to `MAX_AUTO_ESCALATION_LEVEL`, so sites that never set it keep the behaviour they have.
+  
+  Separately, the paths that measured nothing about a client — `MISSING_TOKEN`, `MISSING_HEAD_HASH` and `DECRYPTION_FAILED` — no longer feed the ladder. Each sizes its challenge from a fixed constant chosen to be short ("prove you're human quickly", per their own comments), not from any signal the client produced, but those constants sit above the default baseline of `DEFAULT_SOLVED_COUNT` and so scored as an escalation. A site whose CSP blocks the detector bundle sends no token on every request, so every one of its users was permanently escalated. `OLD_TIMESTAMP` deliberately keeps the ladder: its round count comes from `timestampDecayFunction`, which scales with staleness and is a real graduated measurement.
+  
+  Explicit router and traffic-filter overrides are unaffected in both cases — an operator naming a value still gets it.
+- Updated dependencies [929d99b]
+- Updated dependencies [934fa5d]
+- Updated dependencies [27f525e]
+- Updated dependencies [af267c2]
+  - @prosopo/types@5.8.0
+  - @prosopo/user-access-policy@3.14.0
+
+## 5.4.1
+### Patch Changes
+
+- b6918c0: fix: declare the puzzle render settings on the mongoose user-settings schema
+  
+  `UserSettingsSchema` never declared the `puzzle` block that
+  `ClientSettingsSchema` has carried since the puzzle render tunables shipped.
+  Mongoose is strict by default, so every site-wide override — decoy count,
+  decoy edge/body shading, hole darken, decoy hole darken, piece scale — round
+  tripped through zod, reached the database and was silently dropped on write.
+  The same omission on `TrafficCategoryPolicySchema` did the same to the
+  per-category puzzle overrides a traffic-filter challenge can carry.
+  
+  Identical failure mode to `frictionlessTypes`, which carries the comment
+  explaining it. Bounds mirror the zod field schemas, and the block has no
+  default so an unconfigured site stays free of an empty subdocument rather
+  than gaining one on every save.
+- Updated dependencies [6f57ee9]
+- Updated dependencies [6f57ee9]
+- Updated dependencies [e22d5fb]
+- Updated dependencies [d288371]
+  - @prosopo/user-access-policy@3.13.0
+  - @prosopo/types@5.7.0
+  - @prosopo/common@3.1.54
+  - @prosopo/logger@2.0.9
+
 ## 5.4.0
 ### Minor Changes
 

package/dist/cjs/index.cjs

@@ -16,6 +16,7 @@ exports.DecisionMachineArtifactRecordSchema = require_provider.DecisionMachineAr
 exports.IPValidationRulesSchema = require_client.IPValidationRulesSchema;
 exports.PoWCaptchaRecordSchema = require_provider.PoWCaptchaRecordSchema;
 exports.PuzzleCaptchaRecordSchema = require_provider.PuzzleCaptchaRecordSchema;
+exports.PuzzleRenderSettingsSchema = require_client.PuzzleRenderSettingsSchema;
 exports.SESSION_PROJECTION = require_provider.SESSION_PROJECTION;
 exports.ScheduledTaskRecordSchema = require_provider.ScheduledTaskRecordSchema;
 exports.ScheduledTaskSchema = require_provider.ScheduledTaskSchema;

package/dist/cjs/types/client.cjs

@@ -70,6 +70,55 @@ var IPValidationRulesSchema = new mongoose.Schema({
 		default: void 0
 	}
 });
+var PuzzleRenderSettingsSchema = new mongoose.Schema({
+	decoyCount: {
+		type: Number,
+		min: 0,
+		max: 200,
+		required: false
+	},
+	decoyEdgeDarkness: {
+		type: Number,
+		min: 0,
+		max: 40,
+		required: false
+	},
+	decoyBodyBrightness: {
+		type: Number,
+		min: -20,
+		max: 20,
+		required: false
+	},
+	decoyHoleDarken: {
+		type: Number,
+		min: 0,
+		max: 1,
+		required: false
+	},
+	holeDarken: {
+		type: Number,
+		min: 0,
+		max: 1,
+		required: false
+	},
+	pieceScale: {
+		type: new mongoose.Schema({
+			min: {
+				type: Number,
+				min: .05,
+				max: .95,
+				required: false
+			},
+			max: {
+				type: Number,
+				min: .05,
+				max: .95,
+				required: false
+			}
+		}, { _id: false }),
+		required: false
+	}
+}, { _id: false });
 var TrafficCategoryPolicySchema = new mongoose.Schema({
 	action: {
 		type: String,
@@ -92,6 +141,10 @@ var TrafficCategoryPolicySchema = new mongoose.Schema({
 	puzzleTolerance: {
 		type: Number,
 		required: false
+	},
+	puzzle: {
+		type: PuzzleRenderSettingsSchema,
+		required: false
 	}
 }, { _id: false });
 var UserSettingsSchema = new mongoose.Schema({
@@ -147,6 +200,16 @@ var UserSettingsSchema = new mongoose.Schema({
 		type: Number,
 		required: false
 	},
+	puzzleMaxDifficulty: {
+		type: Number,
+		min: 0,
+		max: _prosopo_types.puzzleMaxDifficultyMax,
+		required: false
+	},
+	puzzle: {
+		type: PuzzleRenderSettingsSchema,
+		required: false
+	},
 	ipValidationRules: IPValidationRulesSchema,
 	domains: {
 		type: [String],
@@ -220,7 +283,7 @@ var UserSettingsSchema = new mongoose.Schema({
 			type: Number,
 			min: 0,
 			max: 1,
-			default: 0
+			default: _prosopo_types.trafficFilterAbuserScoreThresholdDefault
 		},
 		datacenter: {
 			type: TrafficCategoryPolicySchema,
@@ -327,6 +390,7 @@ var TableNames = /* @__PURE__ */ function(TableNames) {
 //#endregion
 exports.AccountSchema = AccountSchema;
 exports.IPValidationRulesSchema = IPValidationRulesSchema;
+exports.PuzzleRenderSettingsSchema = PuzzleRenderSettingsSchema;
 exports.TableNames = TableNames;
 exports.TrafficCategoryPolicySchema = TrafficCategoryPolicySchema;
 exports.UserDataSchema = UserDataSchema;

package/dist/cjs/types/index.cjs

@@ -15,6 +15,7 @@ exports.DecisionMachineArtifactRecordSchema = require_provider.DecisionMachineAr
 exports.IPValidationRulesSchema = require_client.IPValidationRulesSchema;
 exports.PoWCaptchaRecordSchema = require_provider.PoWCaptchaRecordSchema;
 exports.PuzzleCaptchaRecordSchema = require_provider.PuzzleCaptchaRecordSchema;
+exports.PuzzleRenderSettingsSchema = require_client.PuzzleRenderSettingsSchema;
 exports.SESSION_PROJECTION = require_provider.SESSION_PROJECTION;
 exports.ScheduledTaskRecordSchema = require_provider.ScheduledTaskRecordSchema;
 exports.ScheduledTaskSchema = require_provider.ScheduledTaskSchema;

package/dist/cjs/types/provider.cjs

@@ -1142,6 +1142,14 @@ var SessionRecordSchema = new mongoose.Schema({
 		type: Boolean,
 		required: false
 	},
+	agent: {
+		type: Boolean,
+		required: false
+	},
+	webBotAuthAgent: {
+		type: String,
+		required: false
+	},
 	simdReadings: {
 		type: mongoose.Schema.Types.Mixed,
 		required: false
@@ -1498,6 +1506,7 @@ var SESSION_PROJECTION = {
 	iframeUrl: 1,
 	clientMetaData: 1,
 	captchaType: 1,
+	serverChecked: 1,
 	synNs: 1,
 	synackNs: 1,
 	ackNs: 1,

package/dist/index.js

@@ -1,7 +1,7 @@
 import "./_virtual/_rolldown/runtime.js";
-import { AccountSchema, IPValidationRulesSchema, TableNames, TrafficCategoryPolicySchema, UserDataSchema, UserSettingsSchema } from "./types/client.js";
+import { AccountSchema, IPValidationRulesSchema, PuzzleRenderSettingsSchema, TableNames, TrafficCategoryPolicySchema, UserDataSchema, UserSettingsSchema } from "./types/client.js";
 import { CaptchaRecordSchema, ClientContextEntropyRecordSchema, ClientMetaDataRecordSchemaObj, ClientRecordSchema, CompositeIpAddressRecordSchemaObj, DatasetRecordSchema, DecisionMachineArtifactRecordSchema, PoWCaptchaRecordSchema, PuzzleCaptchaRecordSchema, SESSION_PROJECTION, ScheduledTaskRecordSchema, ScheduledTaskSchema, SessionRecordSchema, SolutionRecordSchema, UserCommitmentRecordSchema, UserSolutionRecordSchema } from "./types/provider.js";
 import { StoredPoWCaptchaRecordSchema, StoredPuzzleCaptchaRecordSchema, StoredSessionRecordSchema, StoredUserCommitmentRecordSchema } from "./types/captcha.js";
 import { SpamEmailDomainRecordSchema } from "./types/spamEmailDomain.js";
 import { BannedDomainRecordSchema } from "./types/bannedDomain.js";
-export { AccountSchema, BannedDomainRecordSchema, CaptchaRecordSchema, ClientContextEntropyRecordSchema, ClientMetaDataRecordSchemaObj, ClientRecordSchema, CompositeIpAddressRecordSchemaObj, DatasetRecordSchema, DecisionMachineArtifactRecordSchema, IPValidationRulesSchema, PoWCaptchaRecordSchema, PuzzleCaptchaRecordSchema, SESSION_PROJECTION, ScheduledTaskRecordSchema, ScheduledTaskSchema, SessionRecordSchema, SolutionRecordSchema, SpamEmailDomainRecordSchema, StoredPoWCaptchaRecordSchema, StoredPuzzleCaptchaRecordSchema, StoredSessionRecordSchema, StoredUserCommitmentRecordSchema, TableNames, TrafficCategoryPolicySchema, UserCommitmentRecordSchema, UserDataSchema, UserSettingsSchema, UserSolutionRecordSchema };
+export { AccountSchema, BannedDomainRecordSchema, CaptchaRecordSchema, ClientContextEntropyRecordSchema, ClientMetaDataRecordSchemaObj, ClientRecordSchema, CompositeIpAddressRecordSchemaObj, DatasetRecordSchema, DecisionMachineArtifactRecordSchema, IPValidationRulesSchema, PoWCaptchaRecordSchema, PuzzleCaptchaRecordSchema, PuzzleRenderSettingsSchema, SESSION_PROJECTION, ScheduledTaskRecordSchema, ScheduledTaskSchema, SessionRecordSchema, SolutionRecordSchema, SpamEmailDomainRecordSchema, StoredPoWCaptchaRecordSchema, StoredPuzzleCaptchaRecordSchema, StoredSessionRecordSchema, StoredUserCommitmentRecordSchema, TableNames, TrafficCategoryPolicySchema, UserCommitmentRecordSchema, UserDataSchema, UserSettingsSchema, UserSolutionRecordSchema };