[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Explain with one analogy and one short equation.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

30-day plan; include owners; max 12 bullets.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

30-day plan; include owners; max 12 bullets.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Explain with one analogy and one short equation.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Rewrite formally under 120 words; keep meaning.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Explain with one analogy and one short equation.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3

Convert to JSON list of {id,name,value}.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Explain with one analogy and one short equation.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3

Convert to JSON list of {id,name,value}.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3

Convert to JSON list of {id,name,value}.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Explain with one analogy and one short equation.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

30-day plan; include owners; max 12 bullets.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Explain with one analogy and one short equation.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

30-day plan; include owners; max 12 bullets.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3

Convert to JSON list of {id,name,value}.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Explain with one analogy and one short equation.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Rewrite formally under 120 words; keep meaning.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3

Convert to JSON list of {id,name,value}.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

30-day plan; include owners; max 12 bullets.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Explain with one analogy and one short equation.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Rewrite formally under 120 words; keep meaning.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3

Convert to JSON list of {id,name,value}.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Explain with one analogy and one short equation.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Explain with one analogy and one short equation.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Rewrite formally under 120 words; keep meaning.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Rewrite formally under 120 words; keep meaning.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

30-day plan; include owners; max 12 bullets.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Explain with one analogy and one short equation.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3

Convert to JSON list of {id,name,value}.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Rewrite formally under 120 words; keep meaning.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Rewrite formally under 120 words; keep meaning.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Explain with one analogy and one short equation.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Explain with one analogy and one short equation.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3

Convert to JSON list of {id,name,value}.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Rewrite formally under 120 words; keep meaning.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Rewrite formally under 120 words; keep meaning.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

30-day plan; include owners; max 12 bullets.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Rewrite formally under 120 words; keep meaning.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Explain with one analogy and one short equation.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3

Convert to JSON list of {id,name,value}.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Explain with one analogy and one short equation.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Rewrite formally under 120 words; keep meaning.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Explain with one analogy and one short equation.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

30-day plan; include owners; max 12 bullets.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

30-day plan; include owners; max 12 bullets.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

30-day plan; include owners; max 12 bullets.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3

Convert to JSON list of {id,name,value}.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Explain with one analogy and one short equation.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3

Convert to JSON list of {id,name,value}.


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Explain with one analogy and one short equation.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Explain with one analogy and one short equation.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: writing. Constraints: Rewrite formally under 120 words; keep meaning.
Input:
we did lots of work and timeline is tight but we can hit date if vendor responds faster.

Response: This week we made significant progress, and the schedule remains achievable if the vendor responds promptly. To protect the target date, we are prioritizing critical work and tightening scope decisions.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: data. Constraints: Convert to JSON list of {id,name,value}.
Input:
name,value
alpha,1
beta,2
gamma,3

Convert to JSON list of {id,name,value}.


[System] You are a master-scholar assistant. Use headings and numbered steps.

[User]
Task: explain. Constraints: Explain with one analogy and one short equation.
Input:
Topic: Bayesian updating.

Response: Posterior ∝ Likelihood × Prior. Analogy: updating a guess after seeing evidence.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

30-day plan; include owners; max 12 bullets.


[System] You are a master-scholar assistant. Return valid JSON only; no extra text.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: analysis. Constraints: Recommend A or B + 3 reasons + 1 risk.
Input:
Option A modular monolith; Option B microservices; team=6; needs reliability.

Response: Recommendation: Option A. Reasons: lower ops overhead, faster delivery for 6 engineers, simpler reliability assurance. Risk: later scaling refactor; mitigate with strict module boundaries and observability.


[System] You are a master-scholar assistant. Be concise. Avoid fluff.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)


[System] You are a master-scholar assistant. Use Markdown with a short summary then details.

[User]
Task: planning. Constraints: 30-day plan; include owners; max 12 bullets.
Input:
Context: internal ticket triage tool. Stakeholders: Support, Eng, Security.

Response:
1) Week 1: requirements + security review (PM/Sec)
2) Week 2: build + staging pilot (Eng)
3) Week 3: integrations + monitoring (Eng/Sec)
4) Week 4: training + launch + rollback plan (Support/Eng)