2.3 KiB
Rainbow Raccoon Compiler Operating Contract
Status: required collaboration surface Scope: GitHub-facing contributor and agent guidance Claim boundary: RRC is an admissibility and receipt gate, not a proof that a mathematical, physical, medical, financial, or compression claim is true.
Purpose
The Rainbow Raccoon Compiler (RRC) is the repository's required shape gate for working with Allaun's research stack. It turns a proposed symbolic compression, projection, rewrite, or manifold-boundary shortcut into an inspectable decision:
ACCEPT
HOLD
QUARANTINE
That decision must be backed by payload identity, a type witness, residual policy, and replay evidence. A persuasive story is not enough.
Required Rule
Any nontrivial new idea must be able to answer:
What is the source payload?
What shape does it project into?
What type witness admits that shape?
What residual or sidecar is needed for replay?
What receipt proves the projection did not drift?
Is the result ACCEPT, HOLD, or QUARANTINE?
If those answers are missing, the work remains HOLD.
RRC In The Stack
RRC sits between generative ideas and core promotion:
idea / source / corpus / equation
-> canonical payload
-> RRC projection candidate
-> residual and replay check
-> receipt
-> Lean/GCCL/Omindirection promotion surface
It is especially required for:
- logogram and glyph-payload compression
- GCCL representative transitions
- Omindirection atom promotion
- manifold boundary candidates
- HexLogogram Atlas grouping
- LadderLUT and continued-fraction shortcuts
- semantic tear detection
- any external database or sidecar-backed compression path
Decisions
| Decision | Meaning |
|---|---|
ACCEPT |
The projection has a receipt and can replay under its declared law. |
HOLD |
The projection may be useful, but evidence, replay, residual, or type witness is incomplete. |
QUARANTINE |
The projection is destructive, torn, or unsafe to merge into ordinary token space. |
Contributor Standard
When contributing to this repository, do not promote a compression or semantic rewrite because it is elegant. Promote only when the RRC-shaped evidence says it is admissible.
In plain English: if you want to deal with this stack seriously, bring receipts. RRC is how those receipts get shaped.