Pack

{% if not curation %}

No curation file for this pack yet. The build stage skips until one exists.

{% else %}

These fields become the release manifest. scope_statement and out_of_scope_response are returned on every coverage root call, so their length matters; the release screen shows the root's size against the 2 KB target.

Manifest text title scope_statement {{ curation.scope_statement | length }} characters out_of_scope one per line out_of_scope_response {{ curation.out_of_scope_response | length }} characters limitations one per line freshness_max_age_days

Publishers host=name, one per line; the fallback when no institution rule matches a cited host

Institutions YAML list: who publishes the cited pages; institution_id, name, native_name, level, body, jurisdiction, urls

A page takes the entry whose URL rule (a host, or a host plus path prefix) is the longest one it falls under; a page matching no rule takes its catalogue entry. The registry is never weighed in ranking.

Page basis YAML mapping: default basis of every excerpt of a page, by host or prefix

A citation's own basis, set in the fact form, wins over the page default; a page without a rule defaults to guidance at its institution's level. For an act, an ordinance or a treaty the build appends the article from the cited block's heading path.

Ranking policy YAML; empty means the defaults; never served

Context fields name=value,value|description, one per line

A field a condition uses cannot be removed, and an enum value in use cannot be renamed without confirming; both refusals name the facts.

I understand that renaming an enum value in use changes which facts resolve

{% if not read_only %}{% endif %}

{% endif %}