Guideline Offense Level Base Score Lookup
Exact independently verified base offense levels registry lookup in explicit jurisdiction, guideline edition, independently established offense facts and authority context, retaining source and as-of date. Caller supplies actual applicable records, qualifications and uncertainty; illustrative examples are not authoritative data. No complete/current catalog, eligibility, authenticity, clinical, legal, safety or compliance determination.
Description
A guideline base offense level depends on the governing edition and independently established facts.
A guideline base offense level depends on the governing edition and independently established facts.1
A reference lookup preserves the applicable source without calculating a sentence. Use this tool to retrieve a caller-supplied reference with its source context.
When to use Guideline Offense Level Base Score Lookup
Use this tool to retrieve a caller-supplied reference with its source context. Establish the jurisdiction or research scope, observation and event definitions, reference date, matched period and denominator basis.
How to use Guideline Offense Level Base Score Lookup and understand its results
- Establish the jurisdiction or research scope, observation and event definitions, reference date, matched period and denominator basis.
- Enter callerVerifiedSource, callerVerifiedContext, callerVerifiedAsOfDate, callerReferenceKeys, callerReferenceTexts, queryReferenceKey, using the field meanings and rules below, then run the tool.
- Read result.matchedCallerReference, result.source, result.context, result.asOfDate. Interpret each field using the units, signs and evidence rules below.
- If input validation fails, correct the reported field and run again. Before applying a successful result, check the stated reference scope, units, assumptions and any retained unknown evidence.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| callerVerifiedSource | Caller verified source; caller assertion whose applicability must be independently established | string | Required |
| callerVerifiedContext | Caller verified context; caller assertion whose applicability must be independently established | string | Required |
| callerVerifiedAsOfDate | Caller verified as of date; real Gregorian YYYY-MM-DD date for the supplied record | string | Required |
| callerReferenceKeys | Caller reference keys | list of string | Required |
| callerReferenceTexts | Caller reference texts | list of string | Required |
| queryReferenceKey | Query reference key; exact key or bounded coordinate, according to the rules below | string | Required |
Supply nonblank source and context strings, each at most 256 UTF-16 units, and a real Gregorian YYYY-MM-DD as-of date in years 0001–9999. Enter nonempty aligned reference keys and texts; keys must be unique and nonblank, and texts nonblank. Select an exactly matching key, with case-sensitive matching and no trimming or normalization. The implementation returns its matched text and copies the supplied source, context and date unchanged. These verification labels are caller assertions: the tool does not fetch, verify or update a reference.
matchedText=texts[indexOfExact(queryKey,keys)]; provenance=copied caller assertions Apply the field units and exact ordering, boundary and evidence rules above.
| Output field | Meaning | Value type |
|---|---|---|
| result | Structured result containing the calculation or selected reference fields below | object |
| result.matchedCallerReference | Caller text at the exact matched reference key, returned unchanged | string |
| result.source | Caller source assertion copied unchanged | string |
| result.context | Caller applicability context copied unchanged | string |
| result.asOfDate | Caller date copied unchanged after Gregorian validation | string |
{
"input": {
"callerVerifiedSource": "independently-reviewed-source/edition",
"callerVerifiedContext": "jurisdiction, guideline edition, independently established offense facts and authority",
"callerVerifiedAsOfDate": "2026-01-01",
"callerReferenceKeys": [
"record-a",
"record-b"
],
"callerReferenceTexts": [
"Caller independently verified base offense levels record a",
"Caller independently verified base offense levels record b"
],
"queryReferenceKey": "record-a"
},
"output": {
"result": {
"matchedCallerReference": "Caller independently verified base offense levels record a",
"source": "independently-reviewed-source/edition",
"context": "jurisdiction, guideline edition, independently established offense facts and authority",
"asOfDate": "2026-01-01"
}
}
}Limitations and assumptions
A successful lookup establishes an exact key match to supplied text. The tool does not obtain or authenticate the reference, confirm its applicability, or update its date.
Every listed input requires an explicit value. Unexpected fields, incorrect value types, nonfinite numbers and sparse numeric arrays fail validation; tool-specific bounds and alignment rules apply as described above. Extremely large inputs or outputs can also be rejected. An input error is distinct from a successful calculation that reports a false comparison or retains unknown evidence.
Alternative or Complementary methods
Use Sentencing Table Zone Letter Crosswalk Lookup to examine a related aspect: Sentencing zone labels belong to a particular jurisdiction's table and edition.
Use Criminal History Category Points Table Lookup where its separate inputs and scope apply: Criminal-history categories belong to a specific guideline and edition.
References
Similar or alternative tools
- Sentencing Table Zone Letter Crosswalk Lookup
Sentencing zone labels belong to a particular jurisdiction's table and edition.
- Criminal History Category Points Table Lookup
Criminal-history categories belong to a specific guideline and edition.