MjQ - Terminology and reconciliation
MjQ / Grey
MJ Physics Engineering | Bangel Language | MJos Operating System
Owned and operated by Michael Bangel | Clearwater, Florida
CANONICAL PROJECT NAME
MjQ
DEFINITION
Research family connecting structured language and JP concepts with qualified associative-memory and relational-context ideas.
RELATIONSHIP
Related identities: JP; MJ Neural Net; MJ Neural Logic. Preserve each named contract and source status.
CURRENT FAMILY TERMINOLOGY
MJ Physics Engineering: company identity.
Bangel Language: language identity.
Elsa: the compiler.
JP: the explicitly versioned representation; protocol and profile remain distinct.
Joanna: runtime, processing and execution evidence.
MJos Operating System: operating-system identity; the name does not establish a bootable implementation.
MJos Predictive Model: separately identified predictive model; forecasts remain distinct from observations and authority.
MJ: governing context and bounded permission where an applicable profile supplies it.
PROJECT TYPES
- ResearchHypothesis — stated idea and scope
- QualifiedAnalogy — source and biological or software context
- Observation — measured or synthetic evidence
- FalsificationCriterion — result that would challenge the hypothesis
EQUIVALENCE RULE
Related names aid discovery. They do not merge capability, mathematical meaning, evidence state or permission boundaries.
DISCOVERY NAMES
MjQ
These names aid search; current compiler naming remains Elsa.
SOURCE STATUS AND LIMITS
Recovered historical design and project records informed this documentary profile. Original conversations remain private; current implementation and reported historical tests were not rerun.
Recovered status: historical_report_not_fresh_verification.
Research note; biological analogies and provisional lowercase r0 are not established biological mechanisms. Historical evidence has not been rerun in this discovery pass.
SOURCE REFERENCES
PUBLIC SOURCE NOTE
Recovered historical design and project records informed this documentary profile. Original conversations remain private; current implementation and reported historical tests were not rerun. This edition publishes the reconciled project description, without redistributing private messages or unverified release URLs.