QualiaDB
Working examples in the labQualiaDB stores information with its relationships and supplies the query, reasoning and scientific libraries used across Webizen. A document, a source measurement and a permission can be examined together without treating them as interchangeable facts.
Its particular role
A result can stay connected to the source, circumstances and permissions that give it meaning. The same foundation supports storing those relationships, asking questions about them and applying an explicit rule before an action.
Why it matters
People need to understand why a result appeared, question its sources and correct mistakes. Those same capabilities help a developer trace a fault and help an organisation explain a decision.
People, rights and agency
Context, provenance and permission checks support informed use of information. They are tools for implementing safeguards, not a blanket guarantee that every application meets human rights obligations.
What is demonstrated, and the source evidence
Current demonstration scope
Native Q42 inspection and flat-pattern queries, selected deontic fixtures, source-backed terrain and typed field inspection are present. The full graph, inference, privacy and scientific catalogue is not yet migrated.
source repositories identified; runtime scope separately qualified.
Inspected source records
The references identify the repository baseline and the exact working bytes reviewed. A source link is evidence for this explanation, not a claim that its demonstration is complete.
- qualiaDB/README.md
The inspected working bytes differ from the baseline revision, or are untracked; this includes possible line-ending differences. Revision link identifies repository baseline; recorded SHA256 identifies inspected working bytes. Local changes may not be in the linked revision.
- qualiaDB/crates/qualia-core-db/src/query/mini_parser.rs
The inspected working bytes differ from the baseline revision, or are untracked; this includes possible line-ending differences. Revision link identifies repository baseline; recorded SHA256 identifies inspected working bytes. Local changes may not be in the linked revision.