Vocabularies
The closed vocabularies a report and the protocol objects are stated in, and the registered vocabularies a verifier holds, as their machine-readable files declare them. The rules that govern them are in part 12, Verification vocabularies.
Statuses and verdicts
From VERIFICATION_VOCABULARIES.json.
Verification statuses
verification_receipt.status and verification_summary.status take one of these values.
| Status | Registry verdict it maps to |
|---|---|
pass |
PASS |
warning |
WARN |
review |
REVIEW |
fail |
FAIL |
Registry verdicts
registry_entry.verdict takes one of these values.
| Verdict | Statuses that map to it |
|---|---|
PASS |
pass |
WARN |
warning |
REVIEW |
review |
FAIL |
fail |
Other members of the file
| Member | Value |
|---|---|
schema_version |
loquitur.verification_vocabularies.v1 |
profile_id |
loquitur.verification_vocabularies.v0.1 |
protocol_release_line |
0.1 |
closed_status_vocabulary |
true |
extension_rule |
breaking-protocol-change-with-schema-types-and-conformance-update |
unknown_status_policy |
unknown is not a verification status: it resolves to no registry verdict, no producer emits it, and the severity rule makes it unreachable |
non_claims |
not-a-new-runtime-verdict, not-a-trust-root-authentication-claim |
Registered vocabularies
The values a verifier holds for the kinds asset_type, workflow and anchoring_method, from vocabularies/ of loquitur-protocol. Their document format is fixed by registered-vocabularies/schema.json.
asset_type
From vocabularies/asset_type.json. Kind asset_type, vocabulary version 1.0.0, 2 values.
| Value | Title | Since | Status | Profile |
|---|---|---|---|---|
fund_nav |
Fund net asset value | 1.0.0 |
active |
none |
property |
Real property | 1.0.0 |
active |
none |
workflow
From vocabularies/workflow.json. Kind workflow, vocabulary version 1.0.0, 4 values.
| Value | Title | Since | Status | Profile | Asset types |
|---|---|---|---|---|---|
fund_nav_initial |
Initial fund NAV evidence | 1.0.0 |
active |
none | fund_nav |
fund_nav_update |
Fund NAV update | 1.0.0 |
active |
none | fund_nav |
property_pre_listing |
Property pre-listing evidence | 1.0.0 |
active |
none | property |
property_review |
Property periodic review | 1.0.0 |
active |
none | property |
anchoring_method
From vocabularies/anchoring_method.json. Kind anchoring_method, vocabulary version 1.0.0, 3 values.
| Value | Title | Since | Status | Profile |
|---|---|---|---|---|
blockchain_transaction |
A transaction recorded on a blockchain | 1.0.0 |
active |
none |
rfc3161_timestamp |
An RFC 3161 time-stamp token | 1.0.0 |
active |
none |
transparency_log_checkpoint |
A checkpoint of a transparency log | 1.0.0 |
active |
none |
Compatibility classes
The classes a protocol change is classified under, from compatibility-classes.json.
| Class | Rank | Consumer coordination | New protocol version | Meaning |
|---|---|---|---|---|
wire-exact |
0 | required | not required | Exact canonical bytes, field presence, algorithm and expected outcome are unchanged. |
semantic-exact |
1 | required | not required | Wire representation may be regenerated without changing parsed meaning or expected outcome. |
additive-compatible |
2 | required | required | Optional capability is added and every older consumer remains conforming for the pre-existing profile. |
breaking |
3 | required | required | Existing valid bytes, accepted objects or expected outcomes change. Coordinated migration and downgrade policy are mandatory. |
wire-exact-legacy |
4 | required | required | Current behavior is frozen only to make a known defect explicit. It must be superseded by a new profile, never silently edited. |
implementation-assurance |
5 | not required | not required | Security or robustness corpus that does not itself define protocol semantics. |
governance-only |
6 | not required | not required | Ownership, process or metadata change with no wire or expected-outcome change. |
source-api-breaking |
7 | required | not required | Public source-language or compile-time consumer contracts change while accepted JSON bytes, protocol wire semantics and expected verification outcomes remain unchanged. |
vocabulary-registration |
8 | not required | not required | A value is added to, or deprecated in, a registered vocabulary. No schema, closed vocabulary or rule changes; a consumer holding an earlier version of the vocabulary reports the value as unknown and remains conforming. |
A change that is not classified is breaking. Schema version loquitur.compatibility_classes.v1.
Project site: loquitur.dev
Source: loquitur-protocol/VERIFICATION_VOCABULARIES.json at 3ff7899c0c76. Licence of this page's text: MIT OR Apache-2.0.