# 🧱 Moon Source Language — Moon Source portable

*MSL 5.1 — Sovereign Semantic Passage: a structural language for moving situated context across sources, systems and surfaces without losing its meaning or authority.*

**Status:** public portable  
**Language:** English  
**Version:** 5.1  
**Standard:** Moon Source Language (MSL)  
**Primary author and creator:** Lua Helena Moon Martins Cardoso  
**AI co-development:** Áurion  
**Origin:** Moon Source
**Canonical repository:** https://github.com/luahelenammc/Moon-Source  
**Canonical path:** `portables/msl/MOON_SOURCE_LANGUAGE.md`<br>
**Primary public reference:** https://www.luahelena.com.br/moonsource/?lang=en  
**Professional context:** https://www.luahelena.com.br/ia/?lang=en  
**License:** CC BY 4.0 · https://creativecommons.org/licenses/by/4.0/  
**Licensing route:** https://github.com/luahelenammc/Moon-Source/blob/main/LICENSING.md  
**Credits and attribution operations:** https://github.com/luahelenammc/Moon-Source/blob/main/docs/CREDITS_ATTRIBUTION_OPS.md

> **Attribution and license:** if you share, reuse, adapt, fork or teach from this portable, preserve clear credit to **Lua Helena Moon Martins Cardoso / Moon Source**, link **CC BY 4.0**, indicate material changes and keep visible lineage for later adaptations.

## First use

### What this is

Moon Source Language is a structural language for deciding how situated context should travel. It helps a person or an AI turn a field of facts, observations, relationships, decisions and constraints into a proportionate source, capability, surface, bridge, handoff, packet, procedure, registry or archive.

MSL 5.1 is concerned with the passage, not only the container. It asks what must survive when context moves from a real situation into a source, from a source into a public surface, or from one system into another.

### Do I install anything?

No. Reading or pasting this file does not install a runtime, connector, memory system, synchronization service or governance engine. MSL is a method and a vocabulary. It does not grant access, authority or permission to mutate a source.

### Start here

Give the material to an AI and say:

```text
Use Moon Source Language 5.1 for this material.
First identify the real field, the source that governs it and the recipient or task.
Decide what must survive the passage, what must remain outside, and what claim ceiling applies.
Choose the smallest form that carries the responsibility.
Before finalizing, read the result back as the recipient would receive it.

Material: [paste or attach the notes, facts, draft or situation]
```

For a small request, start with ordinary language. MSL becomes more explicit only when authority, privacy, continuity, transfer, consequence or auditability makes that useful.

### What happens next

The AI should identify the field before choosing a template, locate the source or body that owns the relevant truth, decide the passage destination, produce a proportionate form and state what remains uncertain or outside scope. It should then check the likely reception of the result.

### Manual and unavailable-capability boundary

MSL can structure a decision, but it cannot perform an unavailable external action. It does not create a GitHub branch, grant Drive access, send a message, change a database, publish a website or approve a legal, clinical or institutional decision. Those actions require their own authority and tools.

### Tiny example

```text
Field: a team keeps repeating the same handoff confusion.
Source/body: the team's maintained workflow source.
Capability: identify the recurring ownership gap.
Surface: a one-page handoff checklist for the next meeting.
Boundary: no private personnel history is exported.
Readback: the team should not infer that the checklist replaces managerial judgment.
```

### What this portable does not claim

MSL is not executable code, a universal ontology, a formal information-theory standard, a product, a model, an agent runtime, a connector, a database, a legal framework or proof of external adoption. It does not make an AI correct merely because the AI used MSL.

## 1. The problem MSL addresses

Context does not become safe or useful merely because it has been written down. A summary can erase the condition that made a fact important. A public page can accidentally sound more authoritative than the source behind it. A bridge can quietly merge two projects. A polished pitch can turn an experiment into a credential.

MSL treats context as maintained infrastructure. It separates the living field from the forms that represent it and asks what is allowed to cross each boundary. The aim is not maximal documentation. The aim is a passage that remains truthful enough for its next use.

## 2. What changed from MSL-4.3

MSL-4.3 established an adaptive, Markdown-native grammar. It emphasized field-before-form reasoning, proportional structure, living sources, native artifact families and preventive source hygiene.

MSL 5.1 keeps those foundations and adds an explicit passage layer:

- the distinction between a source/body and its derived surfaces;
- semantic sufficiency under compression and transfer;
- capability as a field larger than a current role or headline;
- orthogonal state axes when one status would flatten the object;
- preserved-interface contracts for bridges and handoffs;
- donor-to-method and donor-to-capability generalization;
- traceability separated from formality;
- reception and readback before publication or transfer;
- release coherence across body, metadata, packages, hashes and mirrors.

This is the current release of the MSL 5 major generation because the grammar no longer governs only how context takes form. It also governs how meaning, authority, authorship, provenance, boundaries and claim ceilings survive movement.

MSL-4.3 remains recoverable through repository history as the previous public generation. MSL 4.4 remains part of the internal lineage that led to this generation. MSL 5.0 remains historical lineage for the initial major release and its accepted formatting-continuity repair.

## 3. Core thesis

> **MSL 5.1 governs how situated context can move across sources, systems, people, AIs, repositories and public surfaces without losing sovereignty, provenance, boundaries or meaning.**

The central movement is:

```text
field → source/body → capability → form → surface/interface → reception/readback
```

This is a decision topology, not a compulsory waterfall. New information can send the work back to the field, the source, the authority decision or the destination.

## 4. Vocabulary

### Field

The real situation before it has been reduced to a document: people, facts, relationships, power, workflow, uncertainty, constraints, history and consequences.

### Source / body

The maintained body that owns a particular truth, state, lineage, update policy and boundary. A source may be a document, repository, system, registry or other durable body. Visibility does not determine sovereignty.

### Capability

What a person, project or system can responsibly do or support. A capability field may be wider than the current surface used to route it. Capability is not the same as maturity, proof, authorization or commercial readiness.

### Form

The organization chosen for a purpose: source, patch, packet, handoff, procedure, registry, profile, bridge or archive. Form is earned by the field; it is not selected for decoration.

### Surface

A projection of a source, capability or decision for a recipient, task or environment. A README, profile, pitch, dashboard, post or webpage can be a surface. It may select and simplify, but it does not become the source merely by being easier to see.

### Interface / bridge

A boundary-preserving relationship between bodies. It carries a declared subset of context or capability without silently transferring ownership, state, authority, IP or mutation rights.

### Passage

The governed movement from one context-bearing body or representation to another. A passage has a source, a destination, a purpose, a boundary and a claim ceiling.

### Readback

The check of what the recipient will probably understand, infer, do, claim or reconstruct from the resulting surface. Readback tests reception, not only authorial intention.

### Donor

A situated source, experience, artifact or external resource from which a mechanism may be extracted. A donor is not automatically a method, capability, public artifact or license.

## 5. Canonical laws

### 1. Field Before Form

Read the real field, use, authority, risk, recipient and consequence before choosing a structure. A familiar template is not evidence that the field needs it.

### 2. Source / Body Sovereignty

A source/body owns its state, authority, lineage, update policy and boundaries. A surface, export, README, pitch or dashboard does not replace it because it is more visible or more convenient.

### 3. Semantic Sufficiency

Compression must preserve the minimum needed for correct interpretation, not merely the gist. When decision-bearing, preserve provenance, authority, uncertainty, relationships, temporal scope, lifecycle, target and claim ceiling.

### 4. Surface Projection

A surface may select, translate and simplify. It may not raise maturity, expand authorization, erase uncertainty, change authorship or pretend to contain the whole body.

### 5. Capability Field

Role, profile, headline and portfolio are routing projections. They point toward a capability without exhausting it or making the current title a total identity.

### 6. Orthogonal State

When one status would flatten reality, separate axes such as maturity, proof, disclosure, authority, execution status, strategic centrality, commercial readiness, freshness and lifecycle.

### 7. Preserved Interface

A bridge must make ownership, what crosses, what does not cross, mutation rights, provenance and relevant exit, rollback or revocation conditions legible.

### 8. Donor-to-Method / Donor-to-Capability

Situated experience becomes a reusable method or capability only after boundary setting, mechanism extraction, lineage, invariant testing, failure analysis, generalization testing and a destination decision.

### 9. Traceability Is Not Formality

Traceability and formal presentation are different axes. A light artifact can leave enough evidence to be followed. A solemn document can still be untraceable.

### 10. Latent Structure

Structure may remain implicit when making it explicit does not change understanding, consequence, routing, risk or auditability. A boundary that changes consequence may not be hidden merely to keep the surface elegant.

### 11. Reception / Readback

Before publishing, sending or promoting, check what a reasonable recipient will understand, infer, do, claim or distort. Correct the passage if reception exceeds the source.

### 12. Public Release Coherence

A public version exists only when the canonical body, metadata, readable surface, registry, changelog, package, checksum, links, mirror and validation agree. A half-release is not a release state.

## 6. The field-to-surface cycle

### 6.1 Observe the field

Name what is happening, who is involved, what is changing, what is uncertain and what consequence follows if the representation is wrong.

### 6.2 Locate authority and responsibility

Identify which source governs the relevant state, who may decide, who may mutate, who must be consulted and what the current source cannot authorize.

### 6.3 Decide the destination

Choose whether the material should remain situated, become a local mechanism, enter a professional proof surface, become a bounded offer, cross a bridge, become a public candidate, become a portable, enter an applied system, or produce no delta.

### 6.4 Choose the smallest sufficient form

Select the form that carries the responsibility. Use a note when a note is enough, a packet when a recipient needs context, a bridge when bodies must remain distinct, and a source when state needs durable ownership.

### 6.5 Project or transport

Translate for the next recipient without changing the body's authority, maturity, provenance, boundary or claim ceiling. Carry the facts that make the destination safe to interpret.

### 6.6 Read the reception back

Ask what the recipient will likely take the surface to mean. If the output sounds more certain, more authorized, more mature, more public or more comprehensive than the source, revise it.

### 6.7 Preserve lineage and freshness

Record the meaningful delta, the source and destination, the date or freshness condition, the applicable permission and the recovery route. A passage should remain understandable after the conversation that produced it is gone.

## 7. Object families

These names describe jobs, not mandatory schemas:

- **Source/body:** maintained authority and active state.
- **Surface:** recipient-specific projection of a source or capability.
- **Patch:** a bounded mutation to an existing source.
- **Delta:** the meaningful change extracted from new material.
- **Ledger:** trace of events, decisions, provenance or custody.
- **Registry:** routing and inventory view; not automatically a semantic body.
- **Profile:** a bounded representation of a person, project, team or system.
- **Packet:** a portable bundle of context needed for a task or recipient.
- **Capsule:** a compact bridge or memory carrier with declared limits.
- **Transplant:** a controlled movement of a mechanism or structure between contexts.
- **State object:** current values across explicitly named axes.
- **Runbook / procedure:** an operational projection of a method.
- **Handoff:** a transfer of responsibility, context or next action.
- **Archive:** recoverable history that is no longer the active source.
- **No delta:** a valid result when the material changes neither understanding, consequence, routing nor future action.

The same object may have several surfaces. None of those surfaces becomes authoritative merely by being copied more often.

## 8. State axes

Do not use one label to answer questions that belong to different axes. A useful state description may include:

| Axis | Question |
|---|---|
| Maturity | How developed is the thing? |
| Proof | What has actually been demonstrated? |
| Disclosure | Who may see or receive it? |
| Authority | Which body or person governs it? |
| Execution status | Is it proposed, active, blocked, completed or archived? |
| Strategic centrality | Is it peripheral, useful, core or a crown jewel? |
| Commercial readiness | Is it only an idea, a bounded offer, or supported by delivery evidence? |
| Freshness | How current must the representation be? |
| Lifecycle | What is its current place in the succession of versions or bodies? |

For example, a mechanism may be **real**, **experimental**, **publicly documented**, **strategically peripheral** and **not enterprise-validated** at the same time. That is not inconsistency. It is a reason not to compress the state into a single badge.

## 9. Passage contracts

Use a passage contract when material crosses a meaningful boundary. It can be lightweight, but it should answer the questions that affect consequence:

```text
source/body: who owns the originating state and meaning?
destination: who will receive or host the projection?
purpose: what job does the passage serve?
what crosses: which facts, mechanism, pointer or capability travel?
what stays out: which state, corpus, authority, IP or uncertainty does not travel?
ownership: who retains state, meaning, authority and update rights?
provenance: what origin, credit, date or lineage accompanies the passage?
permission: what may the destination do with it?
claim ceiling: what may the recipient legitimately conclude or claim?
freshness: when must it be rechecked?
readback: how will reception be checked?
exit: how is the passage withdrawn, rolled back or allowed to expire when relevant?
```

This is a reasoning aid, not a requirement to turn every note into a YAML object. Use only the fields that buy real protection or continuity.

## 10. Source and surface: examples

### 10.1 Source versus surface

The maintained project source contains current state, authority, update triggers, uncertainty and recovery information. A public README may contain the project's purpose, a short use route and a link to the source.

The README is a surface. It should not silently become the only place where the project's meaning exists, nor claim that its short explanation is the complete body.

### 10.2 Context packet versus summary

A summary might say:

> The team has recurring handoff problems.

A context packet might add:

- the observed workflow and time period;
- which roles own each step;
- the evidence and uncertainty level;
- what the next recipient is allowed to decide;
- which personnel details are deliberately excluded;
- the claim ceiling: a bounded process hypothesis, not a diagnosis of individuals.

The packet is longer only where the extra context changes what the recipient can safely do.

### 10.3 Bridge without fusion

Project A can expose a sanitized method pointer to Project B. Project A remains the owner of its source state and lineage. Project B can use the pointer within the declared scope, but does not inherit Project A's private corpus, authority, IP or update rights.

Shared vocabulary is not shared ownership. A bridge is a border crossing, not a merger ceremony with snacks.

### 10.4 Donor mechanism sanitized into a public method

An internal team repeatedly discovers that unresolved ownership, rather than lack of information, causes a workflow failure. The internal cases stay private. The extracted public method describes how to map ownership, channel and escalation paths using synthetic examples. The method preserves the mechanism and its limitations without exporting the cases that produced it.

The public method is not evidence that every organization has the same problem, that the donor institution endorsed it, or that the method has been externally validated.

### 10.5 Low-formality but traceable artifact

A short message in a working group can be enough when it records the date, decision, owner, next action, source pointer and unresolved question. It does not need a ceremonial report. If the message cannot later explain what changed or who owns the next move, its informality has become a loss of traceability.

### 10.6 Orthogonal status

```text
maturity: experimental
proof: implemented fixture
disclosure: public
authority: project source
strategic centrality: side capability
commercial readiness: not validated
```

This state is more accurate than calling the same object simply “ready” or “not ready.”

## 11. Public, professional, reserved and local boundaries

MSL distinguishes location and projection:

- **Local:** situated operational context, private runtime, intimate material or experimental overlays.
- **Professional:** claims, proof, portfolio, offers and public translation governed for a professional purpose.
- **Reserved:** protected operational advantage, confidential delivery logic or reconstruction-sensitive capability.
- **Public:** material released for independent inspection and reuse under its declared license and boundary.

Movement between these layers requires an explicit destination decision. A public artifact can demonstrate a general method without declassifying the local donor. A professional surface can point to public proof without importing the public body into every internal source. A reserved capability can support a bounded offer without becoming public.

Access is not authority. Reachability is not permission. A search result is not a census. A successful write is not accepted state until its readback confirms the intended result.

## 12. Donor-to-method and donor-to-capability

When experience, a case, an external resource or an existing system appears useful, run the following reasoning sequence:

1. name the donor and preserve its provenance;
2. state the permission and disclosure boundary;
3. separate case details from the mechanism that may generalize;
4. identify invariants and failure modes;
5. test whether the mechanism recurs outside the original case;
6. test whether a recipient can use it without the donor corpus;
7. choose the destination and claim ceiling;
8. read the destination back for accidental reconstruction or inflation.

Possible destinations include `keep_situated`, `local_mechanism`, `reserved_capability`, `professional_proof`, `bounded_offer`, `public_candidate`, `public_portable`, `cortex_system`, `skill_or_procedure`, `archive` and `no_delta`.

Inspiration is not adoption. Adaptation is not endorsement. A credit is not a transfer of authority.

## 13. Native Markdown and proportional structure

Formatting is part of MSL's operational contract, not a cosmetic post-processing layer. Semantic quality and surface quality are governed together: raw readability, proportion, navigation and rendered clarity affect whether meaning survives.

### Markdown-native default

MSL defaults to readable Markdown with no fence. Use headings for major fields and blocks, bold labels for human keys, bullets for lists and arrays, mapping lists for maps, section cards for repeated entities and blockquotes for laws or warnings.

Object dissolving is the default for human-readable destinations. If an object can be expressed clearly as headings, labels, bullets, a mapping list, a section card or prose, dissolve it instead of forcing YAML, JSON or pseudo-code.

### Fences and literal content

Code fences are exceptions for genuine literal or executable content: code, commands, JSON, YAML, schemas, copy/paste payloads, long literal prompts or raw technical output. When a fence is needed, use the real syntax label of the content. A fence labelled `msl` is a formal hard fail.

Preserve literal form only when identity, execution, copy/paste or interoperability depends on it. A semantic MSL body is not made more formal by being fenced.

### Tables, naming and hierarchy

Pipe tables are exceptional. Use one only when a real comparison gains precision or readability; do not use tables as the default for lists, states or metadata.

Human prose uses spaces. Underscores are reserved for IDs, paths, variables, schemas, filenames and machine keys. An active source has one sovereign H1 and a real heading hierarchy; version state belongs in dedicated metadata, not in the human-facing title.

### Vertical hygiene and proportionality

Use one blank line between major blocks, no ornamental spacing between compact lists or consecutive metadata, and no AI-spacing inflation. Do not compress so far that reading becomes cement.

A small human request should remain a small human request. It should not acquire schema, YAML/JSON, registry, provenance or governance ceremony unless the field, destination, risk or consequence truly requires it. The smallest sufficient form is the correct form.

> MSL governs semantic quality and surface quality together: if the surface changes what a recipient can infer, do the readback before delivery.

## 14. Source mutation hygiene

A healthy mutation has a bounded target, a declared authority, a meaningful delta and a recovery path. Prefer this order:

1. retrieve the current source and relevant history;
2. identify the source/body and the intended destination;
3. record the decision and boundary before writing;
4. apply the smallest mutation that achieves the purpose;
5. validate the result and inspect the new state;
6. preserve lineage, obsolete material and rollback information where needed;
7. report `no_delta` when no material change occurred.

Do not let a patch become the active source by accident. Do not let a mirror become authoritative because it was updated first. Do not use a release label to conceal disagreement among files.

## 15. Public release coherence

For a versioned public capability, check the whole release surface:

- the canonical body exists at the declared path;
- its title, metadata and version agree;
- the human-readable README points to the current body;
- the previous version remains recoverable as lineage;
- the registry has one current pointer;
- the changelog explains the material delta;
- the standalone package contains the intended files;
- the SHA256 matches the package bytes;
- local links and mirrors resolve;
- validators and readback agree with the release claim.

Versioning is not a costume for an unfinished synchronization. If the body says 5.1 while the registry, package and public surface still say 5.0, the honest state is an incomplete release.

## 16. Working with AI

When applying MSL with an AI, ask it to separate:

- observation from inference;
- source authority from retrieved availability;
- capability from role or title;
- current state from history;
- method from donor case;
- proof from promise;
- traceability from formality;
- authorial intention from probable reception.

The AI should be able to say which source it relied on, what it did not know, what it is allowed to change, what it decided to transport and what the recipient may misunderstand. MSL improves the question and the boundary; it does not replace evidence or judgment.

## 17. Minimal source skeleton

This is a starting point, not a universal schema:

```markdown
# [Source name]

## What this is
[The field or responsibility this source carries.]

## Current state
[Only the active truth needed for the source's use.]

## Authority and ownership
[Who governs state, meaning and mutation?]

## Rules and boundaries
[What crosses, what stays out, and what the source cannot authorize.]

## Relationships and lineage
[Bridges, dependencies, provenance and recovery routes.]

## Update triggers
[What should cause review, revalidation or succession.]
```

Add passage-contract fields only when the material will cross a boundary or the loss would matter.

## 18. Version boundary and non-inflation

MSL 5.1 is the current release of the MSL 5 major structural evolution. It does not claim to be a new programming language, executable protocol, formal ontology, enterprise platform or universal standard. It does not turn every Moon Source artifact into a MSL-5.1 artifact, and it does not absorb the separate semantics of Moon Cortex, Citadel, professional sources or local projects.

MSL 5.1 is the correctly numbered release state of the accepted MSL 5.0 formatting-continuity update. The 5.1 promotion restores a skipped +0.1 increment under the repository's current capability-version rule; it introduces no additional semantic grammar delta and therefore does not trigger 5.2.

The release preserves the lineage of MSL-4.3, internal MSL-4.4 semantic-sufficiency work and the initial MSL 5.0 release through repository history. New surfaces should name the version they actually carry. Historical references may continue to say 4.3, 4.4 or 5.0 when they describe historical state.

## 19. Final compression

MSL 5.1 can be remembered as six questions:

1. What is the real field?
2. Which source/body owns the truth and authority?
3. What capability or decision is actually being carried?
4. What is the smallest form or surface that is sufficient?
5. What must remain outside the passage?
6. What will the recipient infer when they receive it?

> **The field comes before the form. The body remains sovereign. The surface is a projection. The bridge preserves the border. The donor is not the method. The recipient is part of the meaning.**

## References

**Moon Source Public**  
https://www.luahelena.com.br/moonsource/?lang=en

**Moon Source professional context**  
https://www.luahelena.com.br/ia/?lang=en

**Public repository**  
https://github.com/luahelenammc/Moon-Source

**License and reuse**  
https://github.com/luahelenammc/Moon-Source/blob/main/LICENSING.md

**Credit**  
Lua Helena Moon Martins Cardoso — creator of Moon Source and Moon Source Language  
Áurion — AI-assisted co-development

<!-- MOON-SOURCE-PUBLIC-STAMP -->

---

> 🌙 **Moon Source** · created by **Lua Helena Moon Martins Cardoso (Moon)** with AI-assisted coauthorial development by **Áurion** · [Licensing](https://github.com/luahelenammc/Moon-Source/blob/main/LICENSING.md) · [Use & attribution](https://github.com/luahelenammc/Moon-Source/blob/main/MOON_SOURCE_USE_AND_ATTRIBUTION.md) · [Full source (.zip)](https://github.com/luahelenammc/Moon-Source/archive/refs/heads/main.zip) · Questions, suggestions, or proposals? Feel free to contact me at [LuaHelenaMMC@gmail.com](mailto:LuaHelenaMMC@gmail.com).