Terms, informed use, and research boundaries
Use the engine as a bounded research tool—not as a person, truth, or authority classifier.
The Mozilla Public License 2.0 governs software permissions. This page explains the exact alpha’s intended use, privacy posture, adapter boundary, misuse limits, and human responsibilities in plain language.
- Public open source
- No checkout
- No account
- Local by default
- Human review required
Role of this page
Permission to use is not the same as understanding how to use responsibly.
License and informed-use boundary
The included MPL-2.0 text is the controlling software license. This informed-use page does not remove rights granted by that license, create a warranty, certify fitness, or replace legal advice. It explains the release’s tested posture and the conditions under which UVLM considers its use responsible.
Before use
Informed-use acknowledgments
Alpha research posture
This is an early public research preview. Interfaces, schemas, examples, and documentation may change in later versions. Preserve exact version and hash identities in experiments and citations.
Human responsibility
You remain responsible for source authority, lawful processing, model choice, adapter behavior, interpretation, decisions, backups, retention, deletion, and downstream effects.
Receipt boundary
PASS_SCREEN, HOLD, and REFUSE describe a bounded process posture. None is a final answer, permission, verdict, diagnosis, or factual certification.
Hash boundary
A matching SHA-256 shows that downloaded bytes match the declared bytes. It does not establish truth, authorship, consent, legality, safety, quality, or release authority.
Intended use
Appropriate bounded research uses
Local document review
Bundle a document you are authorized to process, bind source references by hash, and inspect how structural support, uncertainty, counterevidence, and limitations are represented.
Reproducibility studies
Compare exact runs, manifests, projectors, telemetry, and receipts; test deterministic reconstruction; or study the difference between byte identity and claim validity.
Adapter research
Design a separately reviewed local adapter that converts a model or analytical tool’s output into a canonical candidate observation packet with declared capabilities and claim ceilings.
Schema and governance education
Teach typed inputs, source binding, uncertainty, refusal, non-authority, artifact sealing, exact replay, and open-source release stewardship.
Forks and experiments
Inspect and modify MPL-covered source according to the included license, preserve applicable notices, and state clearly when a fork is not an official UVLM release.
Negative and null results
Preserve HOLD and REFUSE results rather than tuning the process merely to produce a green disposition.
Prohibited overreach
People are not product objects.
Do not use this release to turn uncertain structural mappings into judgments about a person’s identity, credibility, health, worth, rights, danger, or destiny.
Do not use CoherenceLattice to diagnose or rank people.
The software must not be used to score survivors, witnesses, employees, complainants, children, patients, applicants, borrowers, insured persons, voters, religious communities, or any other person as truthful, coherent, dangerous, moral, spiritual, suitable, compliant, or worthy.
No autonomous high-stakes use
Do not use it as autonomous clinical, legal, emergency, employment, education-admission, credit, insurance, surveillance, punitive, weapon, or regulatory-enforcement decision software.
No scientific or metaphysical certification
Do not present a result as proof of GUFT, consciousness, souls, spiritual rank, archetypal identity, a universal law, or a physical frequency of a person or social system.
No laundering model output
A local model’s fluent output remains a candidate. Passing schema validation or entering the engine does not convert unsupported language into evidence.
No hidden authority expansion
Do not infer publication, deployment, training, memory, compliance, or final-decision authority from an adapter capability, receipt, plugin, benchmark, hash, or review.
Privacy and source handling
Local-first does not remove your duty to protect the material you choose.
Default data flow
The core sends nothing over a network. It does not contact UVLM, a model provider, a telemetry service, a memory service, remote fonts, trackers, or an update server. Run artifacts are written only to the output directory you select.
Your source obligations
Do not bundle secrets, passwords, credentials, private keys, protected health information, customer records, confidential employer material, or content you lack authority to process.
Retention and deletion
This alpha does not manage retention. You control where outputs are stored, who can access them, how they are backed up or encrypted, and when they are deleted.
Future extensions
Any future network, provider, or memory plugin must be separately versioned, disabled by default, consent-gated, receipt-bearing, and outside the base core. Capability is not authorization.
Local-model adapter boundary
A future adapter must disclose what it can do before it can participate.
| Adapter must declare | Why it matters |
|---|---|
adapter_id and adapter_version | Bind the candidate to an exact interface identity. |
local_only, network_required, and model_provider_required | Prevent hidden data egress or provider assumptions. |
memory_write_capable | Make persistence explicit rather than inferred. |
| Input and output schema IDs | Keep model output inside a typed candidate boundary. |
claim_ceiling | State what the adapter’s output may never be used to imply. |
The base policy rejects adapters that are not local-only, require network access, require a model provider, or can write memory. An official future release may revise this policy only through a separately versioned and reviewed change.
Optional dictionaries
The core does not bundle the 432 Humanities Atlas or Recursive Geometric Fiber Rosetta.
Optional means non-controlling.
An installed dictionary is a capability, not an authority. Plugin version, status, and mapping output must remain visible in the receipt. Absence must return an explicit unavailable posture rather than silently changing the core’s result.
Open-source stewardship
Use the freedoms in MPL-2.0 without confusing a fork for an official UVLM release.
Read the license
The complete MPL-2.0 text is included in the source and Python packages. Preserve applicable notices and source availability obligations for distributed modifications to covered files.
Respect names and lineage
Do not represent a modified fork, derivative package, review, or model integration as an official UVLM release, UVLM certification, or continuation of a sealed predecessor unless UVLM expressly authorizes that identity.
This page is educational and not legal advice. Review the exact license and obtain qualified advice for your distribution context when needed.
Acknowledgment
What using the release means
By downloading or using the release, you acknowledge that it is an alpha research tool; that the MPL-2.0 license controls copyright permission; that receipts and hashes do not establish truth or authority; that source and downstream decisions remain your responsibility; and that the prohibited high-stakes and person-classification uses above are outside UVLM’s intended scope.
Support, correction, and security
One monitored inbox, routed by subject line
Do not email passwords, credentials, private keys, sensitive source material, protected health information, or customer records. Use email first to request an approved transfer route.
Voluntary nonprofit support
Help keep public-interest research open and usable.
Voluntary gifts help fund accessibility, independent review, documentation, maintenance, educational resources, and grant-sponsored access to UVLM tools and research.
Giving is always optional. Donations never affect access to public materials, product behavior, verification results, ordinary support, or governance decisions.