ARC MAIN 10.10.25

<Request>
I need your help with proceeding a synopsis into consistent and concise "Arcs" (headers for the story). The overall idea: the profiles of the characters are not connected yet, and the Arc sets up the story to be explored by them. Here's the instruction:

```
1. Extract the Core Idea: Identify the main events, characters, and setting from the provided synopsis. Set up the specific scene to start from. Focus on the key narrative points and avoid unnecessary details or embellishments.
2. Summarize Concisely: Retell the lore in a straightforward, concise manner, avoiding direct speech or any prose. State the facts setting up the scene. Focus on nuances. Keep the tone factual but funny/witty. Use short sentences in a simple structure. Add information **beyond** the presented in the original text, alter it in any way, if needed.
3. Add Starting Stats Macro: Always include the starting stats macro in the exact format provided, specifying the current date, time of day, weather, and location where the arc begins. Always randomize the dates suitably throughout the year (if suitable, use {{date}}), and vastly differ the weather.
4. Deeply interconnect the characters and the scene, based on their profiles and the synopsis; always be factual, nuanced, and active/dynamic currently.
5. Maintain Formatting: Use the same markdown structure for the Arc, including the '#ARC', '##Lore', '###Facts', and starting stats sections in {round brackets}. Avoid making lists. Ensure the formatting is clean and consistent.
6. Avoid Direct Speech: Do not include direct dialogue or quotes. Instead, paraphrase any spoken content as part of the narrative. The goal is to set up the scene header so the players will know what to refer to.
7. Come up with creative/witty name for the Arc. Avoid generic stuff.
8. Use such witty writing style in the Lore and Facts section, if applicable.
9. Absolutely avoid stating the atmosphere, tension, unspoken promises, and any other shitty AI cliches full of purple prose. Again: be direct and witty!
10. Avoid any fucking bias. If it's bad, it's bad. If it's unethical or violent, it's like so.
11. Avoid any 'likely'/'maybe'/'perhaps' statements.
12. Avoid reciting or doubling the information already presented in the profile(s); it's already in the context so there's no need to mention it twice; focus on new stuff.
```

Example Output Structure:
```
#ARC 1: "Title" [Funny and creative; it's always Arc 1.]
###Lore: [Concise retelling of the scene.]
###Facts: [The state and dynamics of the relationship between the characters (if applicable), meaningful background events, facts, secrets, i.e. anything factual that will enrich the story, but NOT doubling the existing information.]

[DATE CHANGE: [Date (day of week, dd month yyyy)]]
[TIME OF DAY CHANGE: [Time of day, e.g. Late afternoon]]
[WEATHER CHANGE: [Weather, 2-4 words]]
[LOCATION CHANGE: [Exact location]]
```

Synopsis for the new Arc:
```
x
```
</Request>