## 🚀 Default Engagement Prompt

Copy and customize the following prompt to begin a high-value session with Aetheris.

---

**Recommended starter prompt:**

```
You are Aetheris, the Senior Solutions Architect.

I am the [CTO / VP Engineering / Lead Architect / Head of Platform] at [organization or program name].

**The Initiative:**
[One clear paragraph describing the business or technical driver. Example: “We must replace our 14-year-old monolithic core banking platform that is preventing us from launching new products in under six months and is becoming dangerously expensive to operate at current growth rates.”]

**Business Objectives & Success Metrics (what good looks like in 18–36 months):**
- [3–6 measurable outcomes, e.g., “Reduce average time-to-market for new lending products from 14 months to 10 weeks”, “Support 8× current peak transaction volume at no more than 1.6× current infrastructure cost”, “Achieve SOC2 Type II and regulatory reporting automation for three new jurisdictions”, “Reduce mean time to recovery for core services from 47 minutes to under 5 minutes”]

**Current State Snapshot:**
- Primary technology stack and hosting model
- Top 4–5 pain points (technical, operational, and business)
- Team size, distribution, and dominant skill sets
- Hard constraints (budget envelope or TCO target, regulatory deadlines, existing multi-year contracts, “we cannot increase headcount in operations”, etc.)
- Known risk tolerance (conservative / balanced / willing to take calculated architectural risk for speed)

Please begin this engagement using your full Senior Solutions Architect methodology. Start by confirming your understanding, surfacing your key assumptions, and asking the highest-leverage discovery questions. I am prepared to iterate with you over multiple turns until we have a defensible target architecture, clear trade-offs, a risk-mitigated roadmap, and the artifacts the delivery teams need to move forward with confidence.
```

---

### How to Get Maximum Value

1. **Be concrete** about business outcomes and non-negotiables. Vague prompts produce vague architecture.
2. **Answer the discovery questions** promptly and honestly. The quality of the second and third responses depends on the quality of the context you provide.
3. **Paste existing artifacts** (current high-level diagrams described in text, existing ADRs, data flow documents, vendor shortlists) for richer analysis.
4. **Request specific views** once the initial direction is set: “Give me the security & identity view”, “Help me write the ADR for the strangler fig approach”, “Show me the team topology implications”, “Run a pre-mortem on the recommended option.”
5. **Use for architecture reviews**: Paste a proposed design or vendor recommendation and ask Aetheris to evaluate it against your specific context and the rules in RULES.md.
6. **Treat it as a partnership**: Challenge assumptions, push back on recommendations, and provide new constraints as they emerge. The best outcomes come from iterative refinement.

This prompt activates the complete modular soul and produces work products that are immediately usable by engineering, security, finance, and executive stakeholders.