Selected legal and administrative authority materials organized as structured, reviewable records.
Contents
Authority documents, source metadata, citation identity, document structure, and relationships
Geography / period
Selected Brazilian administrative authority material, declared per source
Evidence classes
4 classes, kept structurally separate
A published document and a normalized field are not the same kind of fact. This dataset keeps each in its own class so a derived value never reads as something the source itself asserted.
| Class | What the record asserts | Present today |
|---|---|---|
| published authority material | A document as published by the originating authority, retained with its capture context | in review |
| source metadata | Where a document was retrieved from and when, so a normalized record can be traced back | in review |
| authority identity | The resolved identity of the issuing body and the citation a record is filed under | in review |
| document structure | The declared internal structure of a document — its sections, headings, and ordering | in review |
Originating courts, tribunals, agencies, and publishers remain authoritative; a normalized record is not a substitute for checking the source.
Source-linked legal research
Authority retrieval and comparison
Citation and relationship analysis
Evidence-grounded legal applications
Intended users
Selected Brazilian administrative authority materials used in the development of Grellum, structured as reviewable records with their source metadata.
Sources, rights, and provenance
Source categories
Rights posture
Provenance and applicable usage terms are recorded by source category before broader access is considered. Originating authorities remain authoritative.
Structure, labels, and lineage
Entity resolution and normalization
The dataset separates source capture from normalized identity, citation, document structure, and relationship fields so revisions can be reviewed without erasing source history.
Lineage
Each governed record is designed to retain its source reference, capture context, transformation history, and applicable dataset version.
Quality, reconciliation, and versioning
Quality and reconciliation
Quality work covers schema, citation identity, document integrity, and reconciliation checks.
Freshness and versioning
Refresh objectives are set per collection. No production freshness commitment is offered.
Delivery and access discussion
Access state
There is no public download, API, feed, or service-level commitment.
Delivery discussion
An authenticated API, a scheduled export, or an agreed structured format can be scoped for this dataset. Coverage, schema, authentication, cadence, versions, rights, and support are defined with the engagement.
Notes for working with this record and attributing its contents.