MiroFish Usage Guide for Chinese Developers

Best-fit use cases

• A China-based developer wants English product documentation but clear implementation steps.
• A team wants to compare hosted checkout with GitHub self-hosting before committing engineering time.
• A technical user needs API key, Neo4j, Zep, GraphRAG, and cost-estimation checks in one place.

Operating steps

1. Start with an English scenario prompt so model and graph outputs are easier to compare.
2. Confirm the graph backend and memory layer before judging simulation quality.
3. Use offline notes when sensitive material should not enter a hosted workspace.
4. Use hosted checkout when the goal is fast evaluation with support.
5. Document follow-up assumptions in the report so future runs are reproducible.

Common risks

• Translation drift can change actor intent if a scenario moves between languages without review.
• API access and graph services can fail independently, so troubleshoot them separately.
• Cost controls should be set before increasing agent count or report length.