Published package / CLIR

kz.corpus.pinningexample

v0.1.0

Положение о порядке учёта обращений

Cover of kz.corpus.pinningexample: 16 CLIR nodes by family

Authored metadata / not derived

Label

Jurisdiction
KZ
Kind of instrument
statute
Status
teaching slice
What is pinned
official bytes pinned

not verified No manual check of the text against the source is claimed: the bytes are pinned and hashed, but the author made no assertion of “read it and it matched”.

State of preservation

  • official bytes2 editions

    The bytes of the official publication are pinned.

Depth of formalisation

5
EXECUTABLE 0
a deriving node refers to the fragment — something is derived from it
ANCHORED 0
addressable by a semantic node, but nothing is derived
SOURCE_ONLY 5
the text is pinned and addressable, no references

lower bound The package refers to the source through 1 anchors in code form (KZ-…-ART-…). Such an anchor is not a node and does not enter the measure: matching it to a fragment is possible only by a heuristic over the locator, and a guess has no place in a completeness report. So the levels above are the minimum of what exists, not the fact.

The levels are computed from CLIR; authored markup for them does not exist: hand markup would mean that an author’s mistake silently changes the completeness report. This is not a share of the act: the share of the document covered by fragments is measured against the bytes of the pinned publication and is not computed here.

Sources

Try it

The package is embedded in the workbench whole — the same 4 files as in corpus/laws/kz/study/pinning-example: the same law.toml, the same pinned bytes, the same tests. The law is executed by two engines in the browser rather than retold by the showcase.

The workbench is not deployed publicly: the GitHub Pages artefact gathers the documentation and the showcase, and the constructor runs locally. Hence a command rather than a link — a button leading nowhere would promise work that does not exist.

cd constructor && pnpm --filter @law/workbench dev
# then: http://localhost:5273/?sample=pinning-example

Cite

The address of a norm is immutable: contentHash is computed over the canonical bytes, and any edit of the package yields a different hash. The link below points not at “the latest version” but at specific bytes — what citation requires and a version number does not give.

Положение о порядке учёта обращений · PINNING_EXAMPLE_ACT · kz.corpus.pinningexample@0.1.0 · sha256:25c722bc30eea0b77f2dcf9a876ecdc8d96d9f3eeca657bc0950cc72964231cb