The ecosystem · English, Australia

What each part makes possible.

A person’s knowledge, creative work, relationships and place in the living world belong together. These are the parts being developed to support them—and the different jobs each one does.

Try a working subset

Move from an explanation
to something you can inspect.

The native world includes real graph queries, public rule fixtures, source-backed terrain and modelled field data. The module guide also covers work whose demonstrations are still to come.

QualiaDB

Working examples in the lab

QualiaDB 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
    Revision
    7f6057a743937173260c1d62d670283214a1d09a
    Inspected SHA-256
    0eddc00413554d1548579ec97a9eb840ecbcfda6cd9703ee17e7d5ad3cb491f9

    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
    Revision
    7f6057a743937173260c1d62d670283214a1d09a
    Inspected SHA-256
    8ae4b72eda21999c536be4afa9716011ad0a227b327c8b019f6f8a1610a0e39c

    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.

Download the complete explanation and source records

Back to the module guide ↑

Webizen applications and runtime

Working examples in the lab

Webizen is the human-facing application environment built around QualiaDB. Desktop, Studio and application interfaces bring knowledge, creative work and authorised actions into places where a person can use them.

Its particular role

Looking at a tool, adding its resources and allowing it to act are separate choices. That distinction gives a person a chance to understand an application before giving it access to information or capabilities.

Why it matters

A useful computing environment should make the next action understandable and let people work towards their own purposes. It should make room for assistance, review and changing circumstances.

People, rights and agency

Application controls must preserve the difference between a person's choices and another party's authority. An accessible explanation and a visible result are part of meaningful control, not merely visual decoration.

What is demonstrated, and the source evidence

Current demonstration scope

The new native website host supplies dataset, query and selected proof instruments. It is not a qualification of all Webizen Desktop, Studio or QApp workflows.

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
    Revision
    7f6057a743937173260c1d62d670283214a1d09a
    Inspected SHA-256
    0eddc00413554d1548579ec97a9eb840ecbcfda6cd9703ee17e7d5ad3cb491f9

    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/webizen-studio/src/semantic_instruments.rs
    Revision
    7f6057a743937173260c1d62d670283214a1d09a
    Inspected SHA-256
    114e909860b2f0d6ded68831d6107b6c937877324f64756bfc4cc53f4621a37e

    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.

Download the complete explanation and source records

Back to the module guide ↑

Poet

Demonstration still to come

Poet is the authoring application associated with projects, documents and creative work in the ecosystem. Its role is to help people shape a work, while shared libraries supply the underlying language, knowledge and production services.

Its particular role

Poet is the place for shaping and revising a work; Synth is the producer that turns its recipes into deliverable resources. Keeping editing and production distinct lets a creator revisit the work without losing the account of how an earlier version was made.

Why it matters

Creators should be able to revise a work while keeping its sources and meaning available. A project should remain understandable to its collaborators and future maintainers.

People, rights and agency

Authorship, attribution and permission to use a source need to survive editing and export. The website must show these relationships in a real workflow before claiming the authoring experience complete.

What is demonstrated, and the source evidence

Current demonstration scope

Shared host implementation is source-mapped in QualiaDB. The separate Poet application repository and current application release still require owner reconciliation; no complete Poet UI demo is claimed.

separate Poet application owner not reconciled; shared QualiaDB host mapped.

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.

  • synth/README.md
    Revision
    0d08884612f387685eb96e5ddd0a2085c1f1ff02
    Inspected SHA-256
    5fdfc2b495fca45f4a108d11514616b68bf12f35d70064778d6c3814ef12cef8

    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/poet_host/mod.rs
    Revision
    7f6057a743937173260c1d62d670283214a1d09a
    Inspected SHA-256
    5a3b7930271593cb2587ed1bb6f8ab5aeb507183fee0a44ea106de58b313445a

    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.

Download the complete explanation and source records

Back to the module guide ↑

VibeScript

Working examples in the lab

VibeScript expresses a piece of work as checked source: calculations, authored resources and the capabilities a host is asked to provide. The language engine lives in QualiaDB; the separate vibe-script repository supplies editing and language tools.

Its particular role

The instructions for a work are kept as source that can be checked and run again. They name what the host is asked to do, so a change to the work can be reviewed rather than disappearing into a sequence of clicks.

Why it matters

A person can revisit how a result was produced, and a developer can reproduce or repair it. That helps creative work remain editable and makes technical explanations more concrete.

People, rights and agency

Naming a capability does not itself grant authority to use personal information or a device. Host admission and a person's permission remain separate responsibilities.

What is demonstrated, and the source evidence

Current demonstration scope

Native Vibe recipes produce this proof's assets and control the world. The editor, language-service and complete family catalogue have not all been recreated as website instruments.

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.

  • vibe-script/README.md
    Revision
    07a4b85ab9ac910bbcc7fe91de976f8fa5c85950
    Inspected SHA-256
    c7507935b18f94d14317fe81d551f1b32c42bf6582135dc6374d1b95bb2923ee

    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/vibe/Cargo.toml
    Revision
    7f6057a743937173260c1d62d670283214a1d09a
    Inspected SHA-256
    42296516ff966e4888f541074c1cc0638253c9b06a75a2afc96f7472fed038e9

    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.

Download the complete explanation and source records

Back to the module guide ↑

Synth

Working examples in the lab

Synth turns VibeScript recipes and retained inputs into resources such as geometry, images and field data. It packages the source and outputs so that a work can be reopened and checked.

Its particular role

Synth keeps the instructions and retained inputs with the produced resources, and checks that recorded production can be replayed. A creator or reviewer can trace an output back to the work that made it.

Why it matters

An impressive picture is more useful when its underlying work is inspectable and reproducible. Creators can continue editing; reviewers can distinguish a generated illustration from an acquired measurement.

People, rights and agency

Keeping source and provenance with a work helps preserve attribution and permitted use. A successful replay proves reproducibility of the recorded production, not ownership of every possible input.

What is demonstrated, and the source evidence

Current demonstration scope

Real asset production, strict replay and native resource outputs are exercised by this proof. All available production operations are not yet individual interactive instruments.

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.

  • synth/README.md
    Revision
    0d08884612f387685eb96e5ddd0a2085c1f1ff02
    Inspected SHA-256
    5fdfc2b495fca45f4a108d11514616b68bf12f35d70064778d6c3814ef12cef8

    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.

  • synth/src/production/files.rs
    Revision
    0d08884612f387685eb96e5ddd0a2085c1f1ff02
    Inspected SHA-256
    2b6844e7b9f50c5e68ee379cf176d189f827ef001bf2a4be10127d63cb69bba1

    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.

Download the complete explanation and source records

Back to the module guide ↑

Hypermedia production

Working examples in the lab

Hypermedia production supplies composable authoring libraries for geometry, surfaces, images, typography, layout, motion, sound and other media. Synth and other applications use these libraries to build editable works.

Its particular role

The shared libraries let a model, its materials, movement, sound and written explanation be authored as related parts of a work. Their transformations can retain inspectable sources instead of reducing the whole work to a finished picture.

Why it matters

The same underlying work can support an illustration, an accessible explanation and an inspectable technical instrument. It need not become a disconnected promotional image each time it changes form.

People, rights and agency

A composition must retain source terms and the meaning of its data across transformations. Availability of an operation is separate from permission to publish its inputs or from artistic acceptance of its output.

What is demonstrated, and the source evidence

Current demonstration scope

Selected genuine geometry, material and electromagnetic operations are used. The source catalogue contains 150 operations; catalogue coverage is not150 completed website demos.

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.

  • hypermedia-production/README.md
    Revision
    8321792cb700cdac90adf1b1ef8accdc039597f1
    Inspected SHA-256
    984d16ffb40d41fb13fc05ee16f00f3487a9b87970d427cacbb3ace16c10a96c

    The inspected bytes match this repository revision. Revision link identifies repository baseline; recorded SHA256 identifies inspected working bytes. Local changes may not be in the linked revision.

  • hypermedia-production/crates/asset-production-vibe/src/operations_catalog.rs
    Revision
    8321792cb700cdac90adf1b1ef8accdc039597f1
    Inspected SHA-256
    f2100fbbe1a6b89247031ffedac07f4730e1c44061c0289cbbca3052b8f610cd

    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.

Download the complete explanation and source records

Back to the module guide ↑

Etalon

Demonstration still to come

Etalon helps Webizen use graphics and specialist processors to calculate, handle signals and present results. Its direction includes light and other electromagnetic fields; visual rendering is one use of those foundations.

Its particular role

A calculation or sensor reading needs both a dependable execution path and an account of what the result means. Etalon supplies execution building blocks; QualiaDB connects their results to context, permissions and evidence.

Why it matters

People should be able to see what was computed and what an observation can support. Device limits and uncertain measurements matter when a visualisation is used to understand the physical world.

People, rights and agency

Access to a sensor or accelerator does not confer permission to observe a person. Sensing needs a declared purpose and appropriate authority; technical output must not be mistaken for consent.

What is demonstrated, and the source evidence

Current demonstration scope

The proof uses the ecosystem's native field and rendering path. It does not establish a general Etalon waveform generator, RF transmitter or complete sensing/inference demonstration.

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.

  • etalon/README.md
    Revision
    785ab9c1b7d729db9afcd9b0f3fd70344b37be1e
    Inspected SHA-256
    17fac8c6db1a4915c31c7925f0baacba09ff6530ca0b982d12797dc4c0ae5e2a

    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.

Download the complete explanation and source records

Back to the module guide ↑

Anvil

Demonstration still to come

Anvil describes what a device can actually do, so an application can choose work that suits the available hardware and explain its limits. It supplies hardware facts used by other parts of the ecosystem.

Its particular role

It separates what a device reports from what a person permits. The hardware report can guide an execution choice without being treated as authority to access a vault or as a description of the person using the device.

Why it matters

Software should respond honestly to the computer someone has. Reporting a limit or choosing a qualified path is more useful than displaying a control that silently does something else.

People, rights and agency

A device identifier is not a person. Hardware observations can inform a policy decision, but must not replace a person's agency or become an undeclared tracking mechanism.

What is demonstrated, and the source evidence

Current demonstration scope

Repository ownership and public interfaces are source-mapped. No independent Anvil capability-routing instrument is qualified in this website slice.

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.

  • anvil/README.md
    Revision
    b5e0466c1800577c2075db0919eab6250b16f723
    Inspected SHA-256
    ecbd18c9e212a52bf7197bc8658736f8e9b3637ffa21f21fb6b5dfcd2900a705

    The inspected bytes match this repository revision. Revision link identifies repository baseline; recorded SHA256 identifies inspected working bytes. Local changes may not be in the linked revision.

Download the complete explanation and source records

Back to the module guide ↑

Aether

Demonstration still to come

Aether is the application framework being developed for native Webizen interfaces. It brings components, state changes and rendering together so that applications can respond to the person using them.

Its particular role

Its native application direction brings interface components, rendering and VibeScript together through shared ecosystem interfaces. The aim is for changes to a work and the controls a person uses to stay connected across presentations.

Why it matters

People need interfaces that explain changes, remain usable under real device constraints and offer more than one way to reach a task. That work belongs in the application framework as well as individual pages.

People, rights and agency

Supporting different needs requires tested navigation, understandable state and accessible alternatives. A framework's architectural intention is not proof that every application already provides them.

What is demonstrated, and the source evidence

Current demonstration scope

The repository and native production limits are documented. The current website host is not a demonstration that Aether's complete QualiaDB/Vibe application bridge is finished.

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.

  • Aether/README.md
    Revision
    d5ccce3bb9d6cab2aa5d7ef185d57ad786737c27
    Inspected SHA-256
    69001cac301bec9d187127cd1453b028a7f46fd51bb877fc70b9f9ff3b20ffeb

    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.

Download the complete explanation and source records

Back to the module guide ↑

Chora

Demonstration still to come

Chora is an embeddable web and spatial document engine. It gives a host application a way to render traditional web content and documents while exposing explicit interfaces to the surrounding application.

Its particular role

A document can be rendered inside an application while its permissions and security-sensitive actions remain under the host’s control. That boundary matters when ordinary web content appears beside a person’s local tools or records.

Why it matters

A human centric ecosystem still needs to read and use the existing web. Clear boundaries help people move between documents and applications without making every embedded page equally trusted.

People, rights and agency

Origin isolation and delegated permissions are practical places to enforce boundaries. The website must demonstrate actual refusal and authorised access before claiming a particular guardianship or privacy outcome.

What is demonstrated, and the source evidence

Current demonstration scope

Library interfaces are source-mapped. The proof runs in the user's browser and does not constitute an embedded Chora engine qualification.

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.

  • chora/README.md
    Revision
    f42e01c686ba24aa6f25d24ad308a6c004077220
    Inspected SHA-256
    25a9c7925449ca3f3ab44d0051264e8d6317f96d9ec593a3a824cbf387520164

    The inspected bytes match this repository revision. Revision link identifies repository baseline; recorded SHA256 identifies inspected working bytes. Local changes may not be in the linked revision.

Download the complete explanation and source records

Back to the module guide ↑

Webizen Host

Demonstration still to come

Webizen Host is being developed to run applications and shared services on Linux servers, with records of who maintains them, what resources they use and which responsibilities are shared.

Its particular role

Its design separates publishing a name, running an application, limiting its resources and deciding who may act for a group. An account name or domain is treated as a technical handle, not as the entirety of a person.

Why it matters

People and communities need understandable choices about where a service runs, who maintains it and how shared costs and responsibilities are handled.

People, rights and agency

A hosting account must not be treated as the whole person. Isolation, delegated authority and accountability need end-to-end evidence, especially when a service acts for a family or cooperative.

What is demonstrated, and the source evidence

Current demonstration scope

This local website review is not a Webizen Host deployment or a completed VPS service. Product acceptance gates remain separate.

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.

  • webizen-host/README.md
    Revision
    436cd68e4b7e5d74a76e44b8db2c7c7c64686f8f
    Inspected SHA-256
    533cbc0397c32943f550636daaa816491aa2442284cf6cfd640bfa0fa1c2dd9c

    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.

Download the complete explanation and source records

Back to the module guide ↑

Web Civics and semantic instruments

Demonstration still to come

Web Civics supplies shared terms for describing human agency, agreements and normative instruments: documents stating rights, duties or agreed rules. People and software can trace those terms to definitions and sources, and validate how an application uses them.

Its particular role

Its terms are organised around people, shared agreements and the sources of normative instruments. Keeping an instrument’s wording and provenance available helps someone check what a rule actually refers to before relying on it.

Why it matters

A shared term is useful only if people can discover what it means and where it came from. Clear definitions help communities, developers and institutions discuss the same subject without silently changing it.

People, rights and agency

Encoding an instrument is not the same as resolving a legal question or enforcing a right. Preserve its source and scope, and show exactly which authored rule an evaluator applied.

What is demonstrated, and the source evidence

Current demonstration scope

Selected authored deontic fixtures run natively, but the full Web Civics namespace and instrument corpus have not been imported and qualified here.

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.

  • ns/README.md
    Revision
    a0ef9c74a1242f1fc0c67045f08cfad081521d69
    Inspected SHA-256
    ba853b00669f7f92d5faf3fd67c92bc2047adaf2e3c272594180149cac9ff886

    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.

Download the complete explanation and source records

Back to the module guide ↑

Wellfare, cooperation and the work graph

Demonstration still to come

These QualiaDB libraries describe welfare support, shared projects, contributions, records and delegated assistance. They provide structures for cooperation without reducing a person to their account or a single task.

Its particular role

A correction can preserve the earlier record rather than erase it. Assistance can be limited to a purpose, time and authority, with consent and revocation kept explicit; permission to help with one task is not permission to take over someone’s life.

Why it matters

Care and shared work involve changing needs and relationships. Keeping who may do what, for whom and under which conditions visible helps people cooperate without losing their own voice.

People, rights and agency

Support should preserve agency rather than assume unlimited substitute authority. Real consent, revocation and consequential-decision evidence need to be exercised in the eventual native workflow.

What is demonstrated, and the source evidence

Current demonstration scope

Relevant native domain structures are source-mapped. Current generic deontic proof cases are not a completed Wellfare, clinical or cooperative delegation workflow.

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/crates/qualia-cooperative-core/src/lib.rs
    Revision
    7f6057a743937173260c1d62d670283214a1d09a
    Inspected SHA-256
    0d28dcda9c7c7f11db7750baa5e7f3dbc51cf0bd753ab046fd91a6b24b7b68de

    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-cooperative-core/src/agency_delegation.rs
    Revision
    7f6057a743937173260c1d62d670283214a1d09a
    Inspected SHA-256
    51bb3e5a15faa4336e8e007aeaa99eb43880927b98a16a5f37f3cd06bbc33d93

    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/wellfare-core/src/lib.rs
    Revision
    7f6057a743937173260c1d62d670283214a1d09a
    Inspected SHA-256
    cbd831de7ff61cefa2466e7ec0e21ac1231b50061b113098255541ba39ca6689

    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.

Download the complete explanation and source records

Back to the module guide ↑

Anatomy

Demonstration still to come

Anatomy develops spatial models to help people explore bodies and discuss care and support needs. Its current distributed bodies are welfare schematics, with fuller anatomical work described in the modelling requirements.

Its particular role

The modelling requirements keep named structures, their sources and their relationships available for inspection. That makes the accuracy of a particular part something a reviewer can examine, rather than judge only from the appearance of a whole body.

Why it matters

Spatial explanations can help people understand a body and discuss support needs. Their usefulness depends on recognisable structure and clear limits, not just on producing a renderable file.

People, rights and agency

Educational models should support comprehension and dignity. They must not imply a diagnosis, a personal body measurement or clinical validation that the source does not establish.

What is demonstrated, and the source evidence

Current demonstration scope

Existing source and distributed schematic assets are identified. No complete anatomical atlas or all 63 historical anatomy previews is claimed as migrated by this dataset.

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.

  • anatomy/README.md
    Revision
    43336d5ccdbdcabf0a30fc1a86bcb0cc2b12b4a0
    Inspected SHA-256
    467ef0ef0cb9efe8d0c659abbcbbce2f4b915e5dfdd2504afe18e6b070d69aa7

    The inspected bytes match this repository revision. Revision link identifies repository baseline; recorded SHA256 identifies inspected working bytes. Local changes may not be in the linked revision.

  • anatomy/master/research/modelling-requirements.md
    Revision
    43336d5ccdbdcabf0a30fc1a86bcb0cc2b12b4a0
    Inspected SHA-256
    af5def8332d83298e7118cabe0b2974f5288380f3b4086db8e851d339fbb7199

    The inspected bytes match this repository revision. Revision link identifies repository baseline; recorded SHA256 identifies inspected working bytes. Local changes may not be in the linked revision.

Download the complete explanation and source records

Back to the module guide ↑

Ecopunk and living-world work

Demonstration still to come

Ecopunk connects environmental source registers, biological knowledge and authored living-world experiences. Its current sources include Australian, Earth-space and socioeconomic discovery registers and procedural botanical studies.

Its particular role

It keeps a discovered source separate from material that has been reviewed for publication, retaining licence, sensitivity and provenance along the way. An artist’s tree remains an illustration rather than becoming an unsupported claim that the species was observed there.

Why it matters

Understanding a place means relating living things, physical conditions and human activity. Keeping those relationships inspectable helps an attractive landscape become a place to learn and investigate.

People, rights and agency

Sensitive ecological and community knowledge needs appropriate authority and careful disclosure. A public scene should not expose private travel or imply that a species was observed where an artist placed it.

What is demonstrated, and the source evidence

Current demonstration scope

The proof draws on the source-register method and labels reference terrain separately from artwork. It does not qualify the full Ecopunk data pipeline or its botanical model suite.

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.

  • ecopunk/README.md
    Revision
    f28235135f98df7d6b81a2f12ba341cc9e13a403
    Inspected SHA-256
    19f7d1f9caca8900eee5ec843e1e3507ef7970af9fc9089a10ebebc8aa161c93

    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.

  • ecopunk/docs/planning/data-sources/README.md
    Revision
    f28235135f98df7d6b81a2f12ba341cc9e13a403
    Inspected SHA-256
    8e46b05d72cc4ec0d0199123569b97929b8b5f08636c100d85e0486d325dc682

    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.

  • ecopunk/assets/models/corymbia-aparrerinja/README.md
    Revision
    f28235135f98df7d6b81a2f12ba341cc9e13a403
    Inspected SHA-256
    1861998c09912c74ed223730630887d900d33502f6968dbbc05a4650d1f05806

    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.

Download the complete explanation and source records

Back to the module guide ↑

QDNF and the identifier fabric

Demonstration still to come

QDNF supplies native protocol libraries for exchanging information between devices: establishing sessions, routing messages and recognising the authority attached to an exchange. Related identifier policy remains within QualiaDB.

Its particular role

The rules for an exchange are kept separate from the particular connection carrying it. That allows authority and disclosure conditions to be examined alongside a message path, rather than assuming that being connected is enough.

Why it matters

People need to know where information can travel and what authority accompanies an exchange. Naming, transport and permission should be inspectable instead of being collapsed into a single login.

People, rights and agency

A cryptographic handle identifies a particular technical relationship, not the entirety of a person. Human agency and disclosure limits must survive changes of device, network and institution.

What is demonstrated, and the source evidence

Current demonstration scope

Native protocol sources are mapped. No public relay mesh, raw-Ethernet path or full QDNF website experiment is claimed by this module catalogue.

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/crates/qualia-core-db/src/net/qdnf/mod.rs
    Revision
    7f6057a743937173260c1d62d670283214a1d09a
    Inspected SHA-256
    e467f154176ea19452c180150a6160f8c99ff58b5bde8c365729d3fe3e5379df

    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.

  • anvil/README.md
    Revision
    b5e0466c1800577c2075db0919eab6250b16f723
    Inspected SHA-256
    ecbd18c9e212a52bf7197bc8658736f8e9b3637ffa21f21fb6b5dfcd2900a705

    The inspected bytes match this repository revision. Revision link identifies repository baseline; recorded SHA256 identifies inspected working bytes. Local changes may not be in the linked revision.

Download the complete explanation and source records

Back to the module guide ↑

The explanation is data, too

Read it. Query it. Keep the source.

These same sixteen explanations are stored in a native Q42 graph. In the proof laboratory’s Data and queries instrument, choose The ecosystem - 16 module groups explained to ask about module purposes, relationships, rights or demonstration status. You can inspect the result and export the actual data.

How this reading page is checked

The page is generated from the source-reviewed Australian English narratives. Its source digest matches the dataset catalogue. The native builder verified every one of the 402 graph rows and nine query fixtures; this does not certify the outstanding module demonstrations as complete.

Native Q42 SHA-256: 3a73abe1f8cc7c8774f030946468e3efd7582b9eb4e6efa1b48476843c8bacce
Readable source SHA-256: c5725a59173a2cc0ae670f775801713a0b85b2d4d5405e1ad16677b6642c0285

Human significance and safeguard explanations are editorial design reasoning, not legal advice, clinical validation or an assertion of compliance.