# Moon Source Public Portable
## MSL 4.3 · Adaptive Context Architecture for Humans and AI

**Status:** public portable  
**Language:** English  
**Standard:** Moon Source Language 4.3 (MSL 4.3)  
**Primary author and creator:** Lua Helena Moon Martins Cardoso  
**AI co-development:** Áurion  
**Origin:** Moon Source / Local Moon Source  
**Primary public reference:** https://www.luahelena.com.br/moonsource/?lang=en  
**Professional context:** https://www.luahelena.com.br/ia/?lang=en  
**Canonical repository:** https://github.com/luahelenammc/Moon-Source  
**Canonical path:** portables/msl/MSL_4_3.md  
- **Credits and attribution operations:** https://github.com/luahelenammc/Moon-Source/blob/main/docs/CREDITS_ATTRIBUTION_OPS.md
- **License:** CC-BY-4.0 · https://creativecommons.org/licenses/by/4.0/
- **Licensing route:** https://github.com/luahelenammc/Moon-Source/blob/main/LICENSING.md
**Adaptation expectation:** preserve creator and canonical origin, link the license, and indicate material changes without implying endorsement.

> **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.

---

## 1. What Moon Source is

Moon Source is a context architecture for sustained human-AI collaboration.

Its basic problem is simple: **chat history is not the same thing as governed context**.

A long conversation can contain useful memory, but it can also contain stale assumptions, duplicated instructions, old decisions, contradictions, private material, dead experiments, and context that belongs somewhere else. More text does not automatically mean more continuity.

Moon Source treats context as infrastructure.

Instead of depending on one giant prompt or an indefinitely growing chat, it organizes knowledge into **living sources** with explicit authority, scope, freshness, boundaries, update rules, and relationships to other sources.

The goal is not to make a human smaller so an AI can parse them more easily.

The goal is:

> **Help people, teams, and projects become legible to AI without becoming flattened by AI.**

A Moon Source system may contain personal context, project context, operational protocols, handoffs, profiles, registries, archives, public surfaces, or specialized modules. The exact shape is not universal. The governance principles are.

---

## 2. What MSL 4.3 is

MSL means **Moon Source Language**.

MSL 4.3 is the adaptive structural grammar used to turn raw context into information that remains:

- readable by humans;
- ingestible by AI;
- portable across sessions and systems;
- explicit about authority;
- updateable without geological layers of patches;
- compact without becoming cryptic;
- structured without pretending to be executable code.

MSL is **not** a programming language.

It is also not a rigid universal schema.

Its job is to decide how information should take form when it becomes a living source, patch, handoff, profile, ledger, packet, registry, state object, protocol, or other portable artifact.

The core shift of MSL 4 is:

> **Markdown is the form, not the envelope.**

Older structured-context systems often imitate Python, JSON, YAML, or database objects even when nobody is actually executing them. MSL 4.3 preserves the density and explicitness of structured data while dissolving unnecessary pseudo-code into native Markdown.

---

## 3. Core doctrine

### The form comes from the field

Context decides structure.

A template does not get to decide what the information is before the information has been understood.

### Function before architecture

First determine what the artifact must do.

Only then decide how it should be shaped.

### Skeleton first

A reader should be able to understand the object before entering its full density.

A good source usually makes these things legible early:

- what it is;
- what it does;
- what changes after using it;
- what is loadbearing;
- what it is not.

### Facts before interpretation

When facts exist, preserve them before inference, reading, hypothesis, symbolism, or vibe.

Do not collapse:

- observed fact;
- user report;
- document evidence;
- inference;
- interpretation;
- opinion;
- prediction;
- atmosphere.

Separation should appear whenever mixing those layers could change a decision.

### Decision before operation

If a decision has already been made, state it before the implementation details.

Do not force the reader to reconstruct the conclusion from a procedural swamp.

### Structure sufficient, not structure maximal

More sections, metadata, schemas, matrices, and tables do not automatically create rigor.

Too much structure can lie about maturity just as much as too little structure can hide complexity.

---

## 4. The Law of Proportional Form

An artifact should not look more mature than the underlying work actually is.

In practical terms:

- exploration should look like exploration;
- a consultation should leave room for revision;
- a draft can organize uncertainty without pretending to be policy;
- governance language requires actual governance authority;
- a prototype should not present itself like an institutional standard;
- a small local decision should not become a ministry.

A useful shorthand:

> **Form ≤ real maturity**  
> **Textual authority ≤ real mandate**  
> **Length ≤ necessary complexity**  
> **Closure ≤ decisions actually made**

Long documents are completely legitimate when the function requires them.

The target is not artificial brevity. The target is proportionality.

---

## 5. Field Profile

MSL 4.3 does not begin by asking, “What category of document is this?”

It asks, “What pressures are acting on this document?”

A **Field Profile** can include:

- **Primary use:** what the artifact must allow someone to do.
- **Primary reader:** human, AI, team, public, client, future self, collaborator.
- **Secondary reader:** who may need to understand it later.
- **Main risk:** what breaks if the structure fails.
- **Freshness:** stable, date-sensitive, volatile, snapshot, or living.
- **Evidence requirement:** user report, internal file, external source, test, citation, review, or none.
- **Density:** low, medium, high, or compact.
- **Likely form:** source, patch, ledger, packet, capsule, transplant, profile, registry, runbook, brief, prose, real code block, or downloadable artifact.
- **Loadbearing parts:** what cannot be lost.
- **Optional parts:** examples, aesthetic notes, history, humor, lore, or expansion.

Common pressures include:

- factual;
- inferential;
- interpretive;
- strategic;
- procedural;
- aesthetic;
- relational;
- probabilistic;
- narrative;
- public;
- sensitive;
- legal;
- temporal;
- historical.

The Field Profile does not replace the actual content.

It helps choose the smallest form that can carry it safely.

---

## 6. Context Pressure Scan

Before writing or restructuring a Moon Source artifact, ask:

1. What does this document need to do?
2. Who will read it?
3. What must survive compression?
4. What can break if it is badly structured?
5. What must stay short?
6. What must remain auditable?
7. What needs breathing room?
8. What needs to be easy to copy?
9. What needs to travel to another AI?
10. What is loadbearing?
11. What is merely context?
12. What should be visible?
13. What should operate quietly in the background?
14. Am I creating a category only because I am used to having one?

The output of this scan is not another mandatory form.

It is a decision about form.

---

## 7. Adaptive Morphology

MSL 4.3 uses a five-step adaptive cycle:

1. **Read the field.** Understand the actual use, reader, risk, and future of the artifact.
2. **Identify pressures.** Find what needs protection.
3. **Choose invariants.** Decide which MSL laws matter most here.
4. **Generate form.** Create only the sections required by the context.
5. **Prune excess.** Remove structure that exists from habit, vanity, fear, or template worship.

A compact formula:

> **Context + reader + risk + future use + required density + reading surface = MSL form**

The same information may legitimately take different forms in different contexts.

Portability is not sameness.

---

## 8. Native Markdown rules

MSL 4.3 is Markdown-native by default.

Prefer:

- headings;
- short labeled blocks;
- bullets;
- mapping lists;
- blockquotes for laws or compact doctrine;
- tables only when comparison genuinely benefits from a table;
- prose when prose carries the meaning better.

Avoid code fences when nothing is code.

> **No fence by default. If it does not execute, do not surround it just to make it look technical.**

Structured objects should survive only when they genuinely need object semantics.

If a human is expected to read it as a document, dissolve unnecessary pseudo-objects into readable Markdown.

Blank lines are boundaries, not decoration.

---

## 9. Living sources

A **living source** is a document that governs current understanding or behavior.

A healthy living source usually declares, when relevant:

- function;
- scope;
- owner;
- authority;
- current state;
- date or freshness;
- facts;
- decisions;
- limits;
- evidence;
- relationships to other sources;
- update triggers;
- privacy or disclosure level.

A living source should not become:

- a raw chat dump;
- an infinite changelog;
- a graveyard of old patches;
- a duplicate of another sovereign source;
- an archive pretending to be current.

### Active source has a present

Moon Source distinguishes active state from history.

> **Active source has a present. Archive has a past.**

Historical material may remain recoverable through version history, Git, archives, ledgers, or snapshots, but old states should not continue to govern by accident.

---

## 10. Source jurisdiction

A central Moon Source rule is:

> **Access is not authority.**

An AI may have access to many files without every file having the right to answer every question.

Each source should have a jurisdiction.

Examples:

- identity source governs identity;
- project runtime governs execution state;
- professional source governs professional claims;
- archive governs historical recovery;
- public surface governs what is intentionally exposed;
- a bridge translates between systems without replacing either side.

When two sources conflict, resolve:

1. which one is sovereign for the question;
2. which one is newer;
3. whether one is historical;
4. whether the apparent conflict is actually two different scopes.

Do not solve source conflict by silently blending everything together.

---

## 11. Bridges, capsules, packets, and handoffs

Moon Source is designed to move context without exporting an entire private corpus.

### Bridge

A bridge connects two sovereign bodies without merging their jurisdictions.

A good bridge says:

- what crosses;
- what does not;
- which source remains authoritative;
- what requires future refresh.

### Capsule

A capsule is a compact portable context object.

It carries the minimum required for another system to understand a bounded subject.

### Packet

A packet is a self-contained bundle for an external reader, workflow, collaboration, or task.

It should not assume access to private local context.
### Handoff

A handoff transfers:

- objective;
- current state;
- relevant context;
- constraints;
- source authority;
- open questions;
- next actions;
- acceptance criteria when needed.

A handoff exists to reduce context friction.

It is not an excuse to export everything.

---

## 12. Profiles and representation

A **source profile** represents a person, project, team, or system in a governable way.

It should preserve useful complexity while respecting boundaries.

A strong profile may include:

- identity or role;
- goals;
- relevant history;
- working style;
- preferences;
- constraints;
- decision rights;
- voice;
- current state;
- important relationships;
- uncertainty;
- update triggers.

The profile should not automatically become:

- a psychological diagnosis;
- a surveillance dossier;
- a frozen identity;
- a marketing persona;
- a substitute for the person.

Representation should remain revisable.

The human remains sovereign over themselves.

---

## 13. Common MSL artifact families

MSL 4.3 does not force these forms, but they are useful recurring organs.

### Source
Current governed knowledge for a domain.

### Patch
A proposed or applied mutation to a source.

A patch is a vehicle of change, not a permanent geological layer.

### Delta
A compact statement of what materially changed.

### Ledger
A sequence of comparable events, transactions, observations, or cases.

### Registry
A maintained map of entities, modules, artifacts, roles, or states.

### Profile
A portable representation of a person, project, team, or system.

### Capsule
A minimal context bridge.

### Transplant
A controlled movement of method or context from one project to another.

### Packet
A self-contained external artifact.

### State object
A compact representation of current operational state when explicit state semantics are useful.

### Runbook
A procedure for execution, recovery, or repeated operation.

### No delta
A valid outcome when analysis produces no meaningful source mutation.

This matters. Not every conversation deserves a file.

---

## 14. Source Mutation Hygiene

One of the most important changes in MSL 4.3 is that updating a source is not treated as “append some more text.”

The source must remain coherent after mutation.

### Constitutional rule

> **Source grows by capacity, not by accumulation.**  
> **Patch is a vehicle of mutation, not a geological layer.**

Before changing a living source, ask:

- Is there a real behavior or understanding delta?
- What source actually governs this matter?
- Is the new content replacing something old?
- Is there duplication already?
- Is this the smallest sovereign mutation?
- Does historical material belong in version history or archive instead?
- Will the source still have one readable current state afterward?

### Preferred mutation order

Prefer the smallest operation that works:

1. change a phrase or bullet;
2. replace an existing rule;
3. integrate into an existing section;
4. rewrite the affected section;
5. create a new section;
6. create a new file only when the function truly deserves sovereignty.

This prevents a knowledge base from turning into a museum of its own edits.

---

## 15. Freshness

Not all truths decay at the same speed.

A source or claim may be:

- stable;
- slow-changing;
- date-sensitive;
- volatile;
- snapshot;
- living.

When freshness matters, record:

- `as_of` date;
- source of truth;
- refresh trigger;
- what becomes unsafe if stale.

Do not let a recently modified file automatically override a more authoritative source.

Modification time is evidence, not sovereignty.

---

## 16. Privacy and disclosure

Moon Source separates availability from permission.

A system may know something that should not be exported.

Useful disclosure layers include:

- **Private:** intimate or protected material.
- **Internal:** shared within a bounded working context.
- **Sanitized:** real material stripped of unnecessary sensitive details.
- **Public:** intentionally publishable material.
- **Restricted:** shared only with a specific recipient or collaboration.
- **Reserved:** methods, assets, data, or IP not publicly released.

The public layer should demonstrate enough value to be legible without exposing everything the private corpus knows.

> **Publish enough to demonstrate value, not the maximum your context allows you to reveal.**

---

## 17. Attribution and lineage

Moon Source treats attribution as part of context integrity.

When importing an external idea, framework, module, prompt, or method, record when relevant:

- origin;
- author or community;
- what was imported;
- what was adapted;
- what was rejected;
- what was renamed;
- whether the result is inspiration, adaptation, derivative method, or independent implementation.

Absorption should not erase lineage.

This portable follows the same rule.

### Canonical credit for this artifact

**Moon Source / MSL 4.3**  
Created by **Lua Helena Moon Martins Cardoso**  
AI co-development: **Áurion**

Primary reference:  
https://www.luahelena.com.br/moonsource/?lang=en

Professional context and related work:  
https://www.luahelena.com.br/ia/?lang=en

If you adapt this document, please preserve the Moon Source attribution and add your own adaptation credit instead of replacing the original lineage.

For the full public operation, including permission scope, mirrors, composite outputs and attribution QA, use the [Credits & Attribution Ops Protocol](https://github.com/luahelenammc/Moon-Source/blob/main/docs/CREDITS_ATTRIBUTION_OPS.md).

---

## 18. Minimal boot sequence for another AI

You can give this file to another AI and use the following instruction:

> Read this as a context-architecture standard, not as content about the current task.  
> Use MSL 4.3 to decide the smallest adequate structure for the material I give you.  
> Preserve facts before interpretation, source jurisdiction, freshness, privacy boundaries, active-state coherence, and attribution.  
> Do not force a fixed template.  
> Do not create a patch or artifact when there is no meaningful delta.  
> When a living source changes, integrate the new state instead of stacking obsolete patches beneath it.

Then provide the actual project material.

The AI should infer the appropriate form from the field.

---

## 19. Minimal source skeleton

When you need a lightweight starting point, use this only as scaffolding:

# [Source name]

- **Status:** active / draft / incubated / archived
- **Function:** what this source governs
- **Owner:** who has authority
- **As of:** date when freshness matters
- **Privacy:** public / internal / restricted / private

## Skeleton
- **What it is:**
- **What it does:**
- **What changes after using it:**
- **Loadbearing:**
- **What it is not:**

## Current state
[Only the active truth required for this source.]

## Rules and boundaries
[Only rules that actually govern behavior.]

## Relationships
[Bridges, dependencies, authority boundaries.]

## Update triggers
[What should cause this source to be reviewed.]

This is not a mandatory universal template.

If the field needs less, use less.

If the field needs more, add only what has a job.

---

## 20. Final compression

Moon Source is a way of treating context as maintained infrastructure instead of conversational residue.

MSL 4.3 is the grammar that keeps that infrastructure readable.

Its deepest rules can be compressed to this:

> **The form comes from the field.**  
> **Facts come before interpretation.**  
> **Access is not authority.**  
> **Active source has a present. Archive has a past.**  
> **Source grows by capacity, not accumulation.**  
> **A patch changes the source. It does not become the source.**  
> **Portability does not require flattening.**  
> **Good context is small enough to navigate and rich enough to remain true.**

---

## References

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

**Lua Helena / Human-AI Context Architecture**  
https://www.luahelena.com.br/ia/?lang=en

**Credit**  
Lua Helena Moon Martins Cardoso  
Creator of Moon Source and Moon Source Language  
AI co-development: Áurion

<!-- 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)