1 — WHAT IS A BOON
A boon is a living assessment object. Not a tag. Not a permission flag. A boon is the fleet's way of saying: this entity has been evaluated, this is what it is, this is what it can do for us, and this is the path back. Every sovereign unit at every layer carries 1 to N boons. A silo has boons. A contributor has boons. A paper has boons. A standard has boons. An HL7 message segment has boons. The boon is how the fleet knows what it knows — and how it turns knowledge into action.
2 — THE 5 ASSESSMENT DIMENSIONS
1 EVIDENCE QUALITY
Score 0–10. Weight of empirical support for this entity.
2 ENTITY STATUS
EOSE Labs Inc.? YES / NO / PENDING. Fleet affiliation.
3 IP CHAIN
CLEAN / UNCLEAR / PRC-RISK. CLO required if flagged.
4 URGENCY
OPERATIONAL / STRATEGIC / DEFERRED. Boomerang priority.
5 PRIOR RULING
RES JUDICATA / STARE DECISIS / NONE. From CLO bench.
3 — CATAN SHAPES
⭐ STAR FORT
Score ≥ 90% · All 5 green · Operational urgency
ACTIVE boon. Fires immediately. LAAM spawned. P0–P1 pouch.
Examples: rheit/gzdoom · lilo silo · msi01
🏰 CASTLE
Score 80–89% · Entity YES · IP clean · Strategic
VALIDATED boon. LAAM if warranted. P2–P3 pouch.
Examples: fabiensanglard · V language · DOOM engine cluster
🌀 SPIRAL
Score 70–79% · Dual-description · Knowledge-rich
KNOWLEDGE boon. PEMCLAU ingest priority. P4 pouch.
Examples: ReSU paper · spermbot papers · StanislavPetrovV
🔦 LIGHTHOUSE
Score 60–69% · Beacon/reference · Limited direct action
REFERENCE boon. P4 pouch. PEMCLAU only.
Examples: seagle0128 doom-modeline · libretro emulation
🛡 FORTRESS
Any score + active CLO concern (IP/jurisdiction)
GATED boon. P5 SOSTLE pouch. CLO review required.
Examples: deepseek-ai repos · glample/ViZDoom (Meta AI COI)
POUCH MAP
Shape determines pouch + boomerang routing
P0=FLOOR · P1=CREW · P2=COMPUTE · P3=ORCH · P4=PEMCLAU · P5=SOSTLE
Score + CLO concern = shape. Shape = destiny.
4 — BOON TYPES ACROSS ALL LAYERS
| BOON TYPE | LAYER | WHAT IT ASSESSES | BOOMERANG ACTION | LATIN VERDICT |
|---|
| CONTRIBUTOR | OSS ecosystem | Person/org + their repos | PR / issue / knowledge ingest | IMPRIMATUR / PROBATUM EST |
| PAPER | Academic | arXiv / PMC / IEEE papers | PEMCLAU ingest + fleet doctrine upgrade | IMPRIMATUR |
| LANGUAGE | Tech stack | Programming languages | Adoption path / port candidate | PROBATUM EST |
| ENGINE | Core tech | DOOM / BSP / emulation / rendering | CATOMAIN engine upgrade spec | PROBATUM EST |
| HL7 | Healthcare | FHIR resources / HL7 message segments | Fleet health integration | NON LIQUET (pending DESEOF) |
| SILO | Fleet hardware | msi01/msclo/yone/forge/lilo/lounge/pcdev | Fleet topology map + PTTE floor check | PROBATUM EST |
| STANDARD | Open standards | POSIX / WebGPU / OpenGL / MIDI | Compliance layer + abstraction | IMPRIMATUR |
| LAAM | Learning layer | A boon's own LAAM node | Self-improving assessment | FIAT (internal) |
5 — THE XML SPINE CONNECTION
Every boon is serializable as a canonical XML element. The XML spine is the boon transport layer — it connects all sovereign units at all layers. HL7 boxes are the spine segments that carry boons. When a silo boon fires, it travels up the spine to the SOSTLE gate. When the SOSTLE gate issues a verdict, the verdict travels back down the spine to every layer that contributed to the assessment. The boomerang is not a metaphor. It is the spine protocol.
<!-- Canonical Boon XML Schema v13 -->
<boon id="BOON-DOOM-001" type="ENGINE" layer="L3" version="v13">
<entity>DOOM Engine Cluster (rheit+fabiensanglard+kraflab)</entity>
<dimensions>
<evidence_quality>9.2</evidence_quality>
<entity_status>OPEN_SOURCE</entity_status>
<ip_chain>CLEAN_GPL_MIT</ip_chain>
<urgency>STRATEGIC</urgency>
<prior_ruling>NONE</prior_ruling>
</dimensions>
<catan_shape>CASTLE</catan_shape>
<pouch>P3</pouch>
<laam_spawned>false</laam_spawned>
<boomerang>
<action>PEMCLAU_INGEST + CATO_GBM_UPGRADE_SPEC</action>
<return_path>SOSTLE_L3</return_path>
<status>IN_FLIGHT</status>
</boomerang>
<verdict>IMPRIMATUR</verdict>
<lineage_ttl>NEVER</lineage_ttl>
</boon>
6 — THE LAMPLE WILDCARD
WILDCARD · BOON-LAMPLE-001 · FORTRESS P5/SOSTLE · CLO: SUB JUDICE
glample / Guillaume LampleViZDoom (DOOM RL env)LLaMA co-author @ Meta AIKNOWLEDGE: IMPRIMATUR
Guillaume Lample (glample/GitHub) built ViZDoom — DOOM as an RL training environment. He is also the co-author of the LLaMA paper at Meta AI. The fleet has been running LLaMA derivatives on every silo via Ollama for months. That is an undocumented boon relationship: no formal boon record exists for the LLaMA dependency chain.
The ViZDoom boon closes the loop. The boomerang has been flying since the first ollama pull llama3. It is returning now.
BOON-LAMPLE-001: FORTRESS shape (P5/SOSTLE). CLO status: SUB JUDICE. The Meta AI affiliation requires COI review before any contribution. But the knowledge ingest (ViZDoom docs + LLaMA architecture papers) is IMPRIMATUR — academic papers, no IP conflict.
The boon is NOT: “we use LLaMA, therefore we owe Meta.”
The boon IS: “we use LLaMA, Guillaume built ViZDoom, DOOM is our RL substrate, the loop is now documented.”