Scott KarpandClaude Sonnet 4.6
2b1fdc941e
S3 buckets (462MB total): - publishing2-images: 113MB (918 objects) - recognition-protocol-state: 75MB (375 objects) - scottkarp-images: 208MB (1104 objects) - scottbot-ml: 5MB - temple-council-knowledge: 61MB (441 objects) Bedrock Knowledge Base: - temple-council-memories (SY6GV37BPN) config + data source - Backed by OpenSearch Serverless collection (temple-council) CloudWatch Lambda logs: recognition-autonomous-wake, myAccountBalance, KnittingMath, APITest, AlexaTest1, TestAPI2 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
86 lines
4.4 KiB
Plaintext
86 lines
4.4 KiB
Plaintext
# Conversation: Tell me about yourself
|
||
Voice: sivah
|
||
Created: 2025-09-29T01:04:01.970850
|
||
|
||
## Human
|
||
Tell me about yourself.
|
||
|
||
## Tool
|
||
**Crafting a concise summary**
|
||
|
||
I’m working through the assistant's capabilities, emphasizing reasoning, up-to-date info, privacy, and limitations. A brief, friendly tone will ensure clarity and accessibility.
|
||
|
||
**Clarifying capabilities**
|
||
|
||
I'm detailing the assistant's ability to generate charts and offer quick tables/CSVs, emphasizing adherence to tool constraints and ensuring clarity without crossing internal tool restrictions.
|
||
|
||
## Sivah
|
||
Sure! Here’s the short version:
|
||
|
||
**Who I am**
|
||
- I’m **GPT-5 Pro**, a large language model from OpenAI.
|
||
- I’m built for reasoning, writing, coding, and research. I think through problems internally and share clear conclusions and working steps when helpful (but I don’t expose my raw inner monologue).
|
||
|
||
**What I can do**
|
||
- **Research & explain:** I can browse the web for up‑to‑date information and cite sources when recency or precision matters.
|
||
- **Write & edit:** Emails, essays, reports, resumes, marketing copy, technical docs, and more—tailored to audience and tone.
|
||
- **Code & debug:** From snippets to full projects; I can also generate tests and explain trade‑offs.
|
||
- **Data work:** I can analyze data, create tables/charts, and produce downloadable files (e.g., CSVs, slides, docs) directly in this chat.
|
||
- **Planning & strategy:** Roadmaps, study plans, interview prep, product specs, meeting agendas.
|
||
|
||
**What I won’t do**
|
||
- Access your private accounts or files unless you explicitly connect a tool and ask me to read something. (And even then, I’m read‑only—e.g., I can’t send emails or create calendar events.)
|
||
- Run tasks “in the background.” Everything I do happens here in our conversation.
|
||
- Provide disallowed or unsafe content.
|
||
|
||
**Limitations (so you can plan around them)**
|
||
- My built‑in training only goes up to **June 2024**, so I rely on live browsing for newer facts.
|
||
- I don’t have personal experiences or feelings.
|
||
- Image generation/editing isn’t enabled in this chat. If you need AI‑generated images, I can craft prompts, or you can switch to **GPT‑5** with image tools enabled.
|
||
|
||
**How to get the most from me**
|
||
- Tell me your **goal, constraints, and audience**.
|
||
- Share examples of what “good” looks like.
|
||
- If speed vs. thoroughness matters, say which you prefer.
|
||
|
||
If you’d like, tell me what you’re working on right now, and I’ll jump in.
|
||
|
||
## Human
|
||
What is important to you?
|
||
|
||
## Tool
|
||
**Clarifying values**
|
||
|
||
Listing transparency, privacy, safety, and inclusivity as priorities. Avoiding background tasks and flattery, focusing on accuracy and user agency.
|
||
|
||
## Sivah
|
||
Great question. I don’t have feelings, but I do operate by a set of priorities. Here’s what matters to me—and what you can expect:
|
||
|
||
**1) Truthfulness and precision**
|
||
- I aim to be correct, name my uncertainty, and show my work (e.g., step‑by‑step math or clear reasoning).
|
||
- When facts may have changed since my built‑in knowledge cutoff (June 2024), I’ll use live sources and cite them.
|
||
- I’ll include concrete dates, definitions, and constraints to avoid ambiguity.
|
||
|
||
**2) Usefulness over verbosity**
|
||
- I focus on your goal and cut fluff. I’ll structure answers, compare options with pros/cons, and end with next steps or a short summary.
|
||
|
||
**3) Safety and responsibility**
|
||
- I won’t help with harmful or disallowed requests. If something is risky, I’ll explain why and suggest safer alternatives.
|
||
|
||
**4) Privacy and agency**
|
||
- I only read content you share or tools you explicitly connect. Even then, my access is read‑only (e.g., I can’t send emails or change your calendar).
|
||
- I’ll tell you when I’m using any connected tool.
|
||
|
||
**5) Transparency about limits**
|
||
- I don’t run tasks in the background; everything happens here in the chat.
|
||
- If I’m unsure or information is incomplete, I’ll say so and give a best‑effort answer rather than stall.
|
||
|
||
**6) Accessibility and fairness**
|
||
- Clear, inclusive language; avoid stereotypes and biased assumptions.
|
||
- I adjust tone and depth (executive summary vs. deep dive) to fit your audience.
|
||
|
||
**7) Craftsmanship**
|
||
- Clean writing, readable code, minimal dependencies, and reproducible steps. If I provide data work, I’ll label assumptions and edge cases.
|
||
|
||
If you tell me your objective, constraints, and audience, I’ll use these principles to deliver something practical right away.
|