Scoring and evaluation fields
Find score policies, provider results and the request manifests for fixed evaluation workflows.
Score policy · object
Document structure
Start with a top-level field, then follow its values and alternatives. The index stays available as you explore.
Required fields must be present. Lists may be empty unless a minimum is specified.
Extra fields: Not allowed at this document root. There is no extensions field in these contracts.
Choose a scale shape
2 alternativesA policy defines numeric points or named ordinal levels. Each uses its own fields.
Document identity
5 fieldskindstringDiscriminator selecting this document or field alternative. Use its exact declared value.RequiredschemaVersionstringDocument contract version, separate from the method revision and npm package version.RequiredidstringStable identity of this scoring policy, qualified by its version and exact serialized bytes.RequiredversionstringDeclared revision of the policy or artifact. Retain its exact bytes as well as this label.RequiredtitlestringReadable name for this policy or source artifact.Required
Purpose and scope
2 fieldsFiles and method
1 fieldRules and result
4 fieldsapplicabilitystringConditions under which the method is intended to be used.RequiredmissingDataobjectWhether required missing information withholds the score or permits a partial result.Required2 nestedlimitationslist of stringLimits on the method or result. Preserve them with any displayed score.Required1 nestedscalechoiceChoose numeric points with optional grades, or named ordinal levels. These are alternatives, not a universal ladder.Required20 nested
How to read this reference npm 2.0.0-beta.4
Required is local. A field marked required must exist in its containing object or selected alternative. A required list can be empty unless minItems says otherwise. Choose the alternative that describes your data; do not combine every alternative.
Structure and meaning are checked separately. These entries come from the published package. Explanations and grouping are editorial. Follow the validation guide for semantic checks such as unresolved references.
- Schema identifier
urn:disclosureos:experimental:provider-score-policy:0.1.0- Package export
@disclosureos/scoring/experimental/v2/provider-score-policy/schema/0.1.0
Repeated keys in different branches are separate schema entries. Their exact paths and field links preserve that context. The schema version is independent of the npm package version.