How it works
A live register of knowledge that concerns several organisations. It holds the knowledge model for building permits – the Planning and Building Act and Ordinance, read from data.riksdagen.se, with their terms, responsibilities and what an application must contain – and what local nodes chose to publish – with every connection and where it comes from.
- Knowledge Object
- A document or record with its source (address + content hash), provenance, rights and lifecycle. The source is not copied.
- Actor Profile
- An organisation or node as a Knowledge Object of its own. Everything the actor did, answered or is responsible for points there. Held by the register until the actor claims it.
- Reference
- A pointer to something the documents are about: a concept, an EU legal act. It has an ID but no source of its own.
- Assertion
- A typed connection between two objects, e.g. “cites”. Always has evidence, a method and someone who stands behind it.
- Evidence
- Exactly where a connection comes from: a field in an API response (JSON Pointer) or a text passage (highlighted when you open the link).
- Event
- An entry in the node’s log. Signed with the node key and chained to the entry before. Changing a single row breaks the chain.
- Node
- An installation with a register, a log and its own key. The register is a node; every visitor can have their own node in the browser.
- Visibility and masking
- Every field has a visibility. A node chooses what it releases; fields it masks are never sent and show here as 🔒.
- Quarantine and mediator
- What nodes publish lands in quarantine first. The register’s mediator accepts or rejects, and every decision is a signed event with a purpose.
How do we know the connections are right?
Stated in source are stated explicitly in the source data, e.g. that the committee report considers the bill.
Rule were read from text by named rules and are marked with the rule and a confidence.
Manual were made by a person in a local node and published.