Explanation example
Turn a vague technical question into a structured explanation.
Sample input
Explain what a release registry is for this site.
- Definition
- Why it matters
- What it does not prove
- Related official links
Static example only. Not live QEVARO output.
Planning example
Break a launch preparation task into phases.
Sample input
Plan the public launch readiness work.
- Now
- Next
- Later
- Launch criteria
- Risks
Example format may change before launch.
Checklist example
Convert readiness requirements into a status checklist.
Sample input
Check whether public API claims are allowed.
- Public API: not available
- SLA: not available
- Core service: not public
- Allowed claim: documentation available
Not a policy engine or live compliance system.
Code review style example
Summarize risks before shipping a route change.
Sample input
Review this 404 routing change.
- Risk
- Affected route
- Failure mode
- Suggested fix
- Verification
Static demonstration of output style only.
Product spec example
Draft a concise public product boundary.
Sample input
Write the QEVARO launch boundary.
- Audience
- Availability
- Non-goals
- User-facing copy
- Success criteria
Not a generated product commitment.
Decision matrix example
Compare release options without overstating readiness.
Sample input
Should the API be announced now?
- Option
- Benefit
- Risk
- Public claim allowed
- Decision
No autonomous business decision is implied.
Documentation draft example
Produce a structured public documentation section.
Sample input
Draft a limitations section.
- Status
- Known boundaries
- Unsupported claims
- Verification links
Static documentation preview, not live inference.