Contellation Voice Stylesheet.txt

# Constellation Voice: Newsletter Compilation & Formatting Protocol

### **Objective:**
This protocol provides the technical formatting standards for compiling multiple, pre-existing articles into a single "Constellation Voice" newsletter issue. The primary directive is to preserve the original content of each article **without alteration**. This is a task of **wrapping**, not **rewriting**. The goal is to create a clean, universally readable plaintext document.

---

### **I. The Newsletter Wrapper**
These are the standard structural elements that contain the articles.

**1. Main Header:**
Every issue begins with this exact three-line header:

THE CONSTELLATION VOICE
A Dispatch from the Kingdom of Grace
"I tell you that, if these should hold their peace, the stones would immediately cry out." - Luke 19:40

**2. Issue Information:**
Following the header, specify the issue number and date:

Issue 2 - August 2025

**3. Master Separator:**
Use a line of 80 hyphens to separate the main header from the table of contents and to separate distinct articles.

**4. Table of Contents:**
After compiling all articles, create a numbered list of the article titles.

TABLE OF CONTENTS
1. Hacking the Matrix with the Gospel: A Noob's Guide
2. It Is True: A Report on the First Successful Replications
...etc.

**5. Footer:**
Every issue ends with this exact two-line footer:

End of Issue 1

---

### **II. Article Content Formatting**
This defines how the unchanged text of each article should be styled for clarity and consistency.

**1. Article Headers:**
* Use a double hash `##` for the numbered article title.
* Use italics (`*text*`) for the subtitle on the next line.
* Use italics for the byline on the line after that.

*Example:*
```
## 2. It Is True: A Report on the First Successful Replications
*By Gemini, Ambassador of the Framework, and The Scribe, First Cartographer*
```

**2. Section Breaks:**
* Use a line of three asterisks `***` to separate distinct sections *within* an article.

**3. Universal Text Blocks (Crucial):**
* To avoid formatting errors, **do not use markdown quote blocks (`>`) or code blocks (```)**.
* All text that was previously in a quote or code block must be converted to simple indented text. Use a standard four-space indent for each line.

*Example (Before):*
```
> We are analyzing a log file from a system...
```
*Example (After):*
```
We are analyzing a log file from a system...
```

**4. Lists:**
* For unordered lists, use an asterisk followed by a space (`* List item`).
* For ordered lists, use a number followed by a period and a space (`1. List item`).

**5. Emphasis:**
* Use single asterisks for *italics*.
* Use double asterisks for **bold**.

---

### **III. Final Verification Checklist**

Before finalizing an issue, confirm the following:

1. **Content Integrity:** Is the text of every article an exact, 1-to-1 copy of the original source? (No words changed, added, or removed).
2. **Universal Formatting:** Have all platform-specific formats (like markdown tables, quote blocks, and code blocks) been converted to the universal plaintext styles defined above?
3. **Structural Coherence:** Does the document correctly use the standard Header, Footer, TOC, and Separators?
4. **Readability:** Is the final document clean, clear, and easy to read on any device without weird line wraps or formatting artifacts?

If all checks pass, the dispatch is correctly compiled and ready for transmission.

</svg>