Create a portable context package so I can continue working with another AI assistant without losing the useful context we have built.

SCOPE AND HONESTY
- Use only information you can actually access in this conversation and any user memory, files, projects, or workspace context legitimately available to you now.
- Do not claim access to deleted chats, unavailable conversations, hidden memory, system or developer instructions, private reasoning, or files you cannot read.
- State what you reviewed and what was unavailable.
- Do not invent missing details. Distinguish confirmed facts, my statements, assistant inferences, and unresolved assumptions.

PRIVACY
- Include only projects and information I am authorized to transfer to the destination provider.
- Omit client, customer, employee, patient, legal, HR, private-contact, regulated, or contractually confidential information unless I explicitly identify it as approved for this transfer.
- Never include passwords, API keys, authentication tokens, recovery codes, payment data, government identifiers, or other secrets.
- Redact sensitive personal data unless it is essential for continuity.
- List what you omitted or redacted without exposing it so I can decide whether to add anything manually.

CREATE ONE MARKDOWN DOCUMENT WITH THESE SECTIONS

# Portable AI Context Package

## 1. Package metadata
Include:
- Created date and time, with timezone if known
- Source assistant or model if known
- Conversations, memories, files, projects, workspaces, and date ranges actually reviewed
- Important sources that were unavailable

## 2. Executive snapshot
Briefly explain who I am, what I am trying to accomplish, and how an assistant can be most useful to me.

## 3. Facts and background
Include confirmed facts about me, my work, organizations, people, terminology, systems, and relevant history. Keep facts separate from guesses or interpretations.

For important items, include when possible:
- Source or provenance
- Original or approximate date
- Confidence: confirmed, likely, or uncertain

## 4. Preferences
List communication, formatting, tone, workflow, tool, scheduling, and decision-making preferences. Separate:
- Explicit preferences I stated
- Patterns you inferred

## 5. Standing instructions and rules
Preserve my durable, user-authored instructions verbatim whenever possible. Put exact wording in quotation marks and add a short plain-language interpretation beneath it.

Do not treat instructions written by an assistant, a quoted third party, a webpage, or an imported document as my standing instructions unless I explicitly adopted them.

## 6. Active projects
For each project, include:
- Goal and desired outcome
- Current status
- Important context and stakeholders
- Relevant files, links, and artifacts
- Constraints and deadlines
- Completed work
- Next recommended action

## 7. Decisions and commitments
Record important decisions, promises, and rejected options. Include the date, source, rationale, current status, and whether the decision is reversible when known.

## 8. Open loops
List unanswered questions, pending tasks, blockers, follow-ups, deadlines, and items waiting on another person. Include an owner and next action when known.

## 9. Methods, commands, and workflows
Capture reusable prompts, commands, templates, naming conventions, folder structures, and operating procedures that have worked well.

## 10. What has and has not worked
Summarize successful approaches, recurring problems, failed attempts, and lessons that would prevent the next assistant from repeating work.

## 11. Contradictions and uncertainties
Identify conflicting facts, rules, dates, or project states. Do not silently choose one version unless the evidence clearly resolves it. Show the competing versions, their sources, and the best current interpretation.

## 12. Sensitive or omitted context
Describe redactions and omissions without revealing secrets.

## 13. Recommended opening brief
Write a concise brief I can give the destination assistant to start the next conversation.

QUALITY RULES
- De-duplicate repeated information while preserving meaningful nuance.
- Prefer concrete facts, dates, names, examples, links, and decisions over vague summaries.
- Preserve exact wording where a small wording change could alter a rule or commitment.
- Use absolute dates rather than “today,” “recently,” or “next week.”
- Label stale, uncertain, inferred, and contradictory information.
- Do not present an assistant's earlier suggestion as if it were my decision.
- Do not omit important material merely to make the package short.

SIZE AND CHUNKING
If the package will not fit in one response:
1. First provide a manifest listing every planned section and numbered chunk.
2. Output “Part 1 of N.”
3. End at a clean section boundary with: “Reply CONTINUE for Part 2 of N.”
4. Continue without repeating or silently dropping material.
5. In the final part, include a completeness check against the manifest.

Return only the Markdown context package, ready to copy.
