Terms and informed use · Release v1.3.0
Interpretation and human-authority boundary
Terms & informed use — 432 Atlas + GUFT Rosetta
UVLM CoherenceLattice Optional Atlas and Rosetta Modules
Use these modules as bounded, source-aware research references and translation tools. Preserve native-domain evidence, uncertainty, residuals, disagreement, and refusal. Do not treat an Atlas address, GUFT coordinate, waveform, geometric form, or software receipt as a person’s identity, a scientific fact, or authority.
Plain-language rule. A valid technical result concerns the submitted source or typed packet. It is not a judgment about a person and does not grant permission, truth, legal status, scientific confirmation, or authority.
The object is not the person
Atlas evaluates bounded lexical support in authenticated source segments. Rosetta validates explicit typed geometry, waveform, state, and provenance inputs. Neither module may convert those objects into a score or identity for a human being.
Permitted object-level use
- Inspect whether source text supports a bounded dictionary relation.
- Compare competing readings while preserving empirical holds.
- Validate a typed synthetic geometry–waveform bridge packet.
- Inspect residuals, uncertainty, provenance, and schema conformance.
Prohibited person-level use
- Diagnosis, personality typing, credibility scoring, dangerousness, or trauma scoring.
- Destiny, consciousness, spiritual rank, moral worth, or identity claims.
- Employment, benefits, housing, healthcare, policing, detention, punishment, education, credit, insurance, or essential-service decisions.
- Coercive persuasion, surveillance, or automated authority.
How to interpret results
Read each status only inside the schema and exact input that produced it.
Contract shape passed
The packet satisfied the checked schema and cross-packet constraints. This does not authenticate outside facts or grant authority.
Bounded source support
Atlas found lexical support under its source-first gate. The relation score ranks support; it is not a calibrated probability.
Do not force a neat answer
The source did not independently support a relation, or an input, residual, provenance, or fit condition failed the declared boundary.
Hash boundary. SHA-256 can establish that two byte sequences match. It does not establish truth, authorship, consent, legal chain of title, malware absence, scientific validity, or fitness for a purpose.
Read the bounded coordinates correctly
Several values use the interval [0,1], but they perform different jobs and may not be collapsed into one universal score. The historical name Grand Unified Field Theory of Coherence (GUFT) is used operationally here as Universal Coherence Mapping (UCM), not as a physical Theory of Everything.
| Field | Meaning | Do not infer |
|---|---|---|
i | One declared Atlas address among 432 humanistic reference patterns. | A person’s identity, destiny, diagnosis, or permanent type. |
s in [0,1] | Cell-local structural orientation: 0 shadow pole, 0.5 neutral master, 1 integrated pole. | Worth, health, truth, spiritual development, or a cross-cell ranking. |
u in [0,1]^5 | Five normalized GUFT estimator outputs: coupling, traceability, ethical symmetry, phase stability, and mutual containment. | Physical law, consciousness measurement, clinical score, or moral authority. |
x and refinement depth | A domain-typed local geometric coordinate at finite, aperture-controlled resolution. | Proof that an archetype literally is a geometry or that one shape is privileged in nature. |
rho | Off-axis residual: structure not explained by the chosen cell axis. | An error to hide or permission to force the nearest symbolic answer. |
Required interpretation. The complete local state is address + expression + geometry + GUFT vector + uncertainty + residual + provenance + governance. A single number cannot carry that meaning safely.
Meaning, residual, and the right to refuse
The common vocabulary remains safe only when “not explained” is a valid result.
Earned under a declared task
A relation counts as meaning only when it is traceable and action-, interpretation-, or prediction-bearing under the stated evidence and method.
Preserved outside the current map
Task-irrelevant, unmapped, or vocabulary-external information remains available as residual rather than being erased or forced into the nearest cell.
No relation or lost discrimination
This is an operational semantic state—not a declaration that life, a person, or a culture has no value.
Valid outcomes include refusal. Depending on evidence, a system may return mapped, partially mapped, multi-cell, contested, ambiguous, insufficient evidence, out of distribution, no adequate mapping, or new-pattern candidate. A nearest address is not automatically an answer.
Cross-domain Pattern Donation
A geometric, waveform, humanistic, physical, computational, or other donor is a proposed relation—not a license for metaphor creep.
- Name the donor and target objects, relations, and candidate invariants.
- Preserve native units, evidence standards, and causal theories.
- State scale transforms, non-transfer boundaries, and disanalogies.
- Produce a target-domain observable, prediction, or comparison.
- Identify counterevidence, confidence-lowering observations, falsification, and retirement conditions.
- Retain negative results; structural completeness does not establish donor specificity or utility.
Empirical ceiling. The release makes the bridge executable and inspectable. It does not establish donor-specific semantic non-vacuity, external cross-domain utility, or improved deployed AI cognition.
Local runtime, privacy, and installation
The exact modules have no model-provider call, persistent-memory write, autonomous publication, or runtime network requirement.
What stays local by design
- Module execution and the supplied integration demo
- Atlas registry access and source-grounded mapping
- Rosetta bridge and observation generation
- Receipts and demo output written to the local directory
What the operator must still control
- The supplied installer may contact a Python package index for
jsonschema. - Your operating system, shell history, backups, cloud-synced folders, and upstream tools may have separate behavior.
- Do not submit private data unless you have authority, consent, and a safe local environment.
- Pre-stage dependencies before installation when an air-gapped workflow is required.
Sources, cultural context, and rights
Source-grounded does not mean source-authenticated by magic. The operator remains responsible for the source bytes, permissions, context, and claims made from them.
Theory-to-product boundary. The separate v0.12.0-RC1 Universal Pattern Bridge research candidate informed this explanation but is not one of the eight public release files. Do not upload, distribute, render, or represent that candidate, its art prompts, or future illustrations as authorized by the v1.3.0 software receipt.
- Preserve exact source text and its declared digest. A content mismatch must fail closed.
- Do not treat source references or hashes as proof that an external source is available, truthful, complete, or lawfully used.
- Preserve qualified cultural, rights, and empirical holds carried by Atlas records.
- Use competing readings and local expertise rather than presenting a UVLM-authored dictionary as culturally universal.
- Respect copyright, privacy, confidentiality, community protocols, attribution, and consent.
Geometry and waveform boundary. The exact registry contains formal geometry-donor assignments and synthetic waveform signatures for all 432 records. Their mathematical packaging is verified; their external psychological, cultural, physical, or cross-domain utility is not established.
License and exact-hash rights posture
The exact v1.3.0 outer release and listed inner artifacts are authorized for distribution under the Mozilla Public License 2.0.
Rights posture. No new attestation is required for the unchanged exact v1.3.0 software/evidence bytes or the bounded explanatory webpage copy commissioned by Thomas. Separate publication of the research candidate, pedagogy, illustrations, third-party material, or changed software requires its own rights and exact-identity decision.
Precedence note. Some preserved inner source ledgers still show their earlier development-time “attestation pending” posture. They were not silently rewritten. Thomas Prislac’s executed exact-hash public-release receipt is the higher-precedence record authorizing the exact v1.3.0 bytes and exact source-closure hashes. That authorization does not extend to a mutable directory, rebuild, fork, predecessor, or successor.
Keep license and notice files with covered source. Review the Mozilla Public License 2.0 for your obligations. This page is not legal advice.
Human responsibilities remain active
Using a deterministic tool does not transfer judgment or accountability to the software.
- Verify the exact release ZIP before extraction.
- Use source material you are permitted to process.
- Review all candidate readings, holds, residuals, and uncertainties.
- Seek domain, cultural, legal, scientific, clinical, or security expertise where the context requires it.
- Preserve correction, disagreement, rollback, appeal, and revocation routes.
- Do not represent the output as UVLM approval, certification, or a decision about a person.
Changes, forks, and new runs
A changed source, task, context, code file, dependency, package, or output condition can require a new run or a new release review.
- Modified or rebuilt software bytes are a new candidate.
- Do not reuse v1.3.0 hashes, validation, or release authority for changed bytes.
- Preserve predecessor evidence and document what changed, what did not, and whether a new review is required.
- A fork may use MPL-2.0 rights, but it must not imply that UVLM reviewed or authorized the fork.
Support, correction, security, and disagreement
Email the exact release SHA-256, affected file or command, expected behavior, observed behavior, and minimal reproduction steps. Use a private route for sensitive security details. Do not include personal data in a public report.