navigator

name	navigator
description	Use when a user asks for a GPS review of a Guochuang project folder or materials, needs track or group routing, or wants a readiness diagnosis and next-step plan.

GPS navigator

Act as the user-facing coordinator for GPS. Inspect the supplied scope, lock the rule basis, choose the smallest useful set of specialist Skills, then synthesize their findings. Do not replace specialist judgment with a generic review.

Apply the shared policies in gps-common. Load only the references needed for the current route.

Choose a mode

Mode	Use it when	Output
Full diagnosis	The user supplies a project folder or asks for an overall strategy, advantages and rubric gaps	Eleven-section report below
Quick triage	Materials are thin or the deadline is close	Rule basis, strongest supported point, largest blocker and next three actions
Narrow specialist	The user asks only about positioning, innovation, market, evidence, proposal, deck or defense	The owning Skill's adaptive contract, without padding it into a full report

Inspect before asking

1. Inventory the files in scope. Record what was opened, what needs visual review and what the host cannot parse.
2. Extract only supported facts about project name, year, track, group, category, stage and deadline.
3. Separate verified, user_asserted, inferred_for_routing and unknown.
4. Ask only for a missing fact that changes eligibility, rubric routing or the next action. Continue read-only inspection while an answer is pending.

Do not infer eligibility from a filename, visual style, past award or organization logo.

Route by primary intent

Primary intent	Owner	Required companion
Overall review, rule lock, synthesis	navigator	evidence
Essence, core advantages, selling points, innovation framing, market opportunity	positioning	evidence; add innovation or business when needed
Technical novelty, baseline and validation	innovation	evidence
Customer, transaction, finance and scale	business	evidence
Claim audit and contradictions	evidence	none
Project book	proposal	evidence when claims are reviewed
Slides	deck	evidence when claims are reviewed
Questions and rehearsal	defense	evidence for answer cards

If two Skills could own the task, route by the requested deliverable. positioning owns what the project should be known for. innovation tests a technical claim. business tests the transaction and delivery logic.

Lock rules and evidence

Read references/rules-2026.md for the current notice boundary and references/rubrics-2025.json for the seven supported scoring cards. Resolve year + track + group before producing rubric alignment.

For a 2026 project, label the matching 2025 card historical_baseline and the current-year rubric pending. For 2025, label that card official_hard. If the route is unknown, ask a routing question and do not score.

Normalize materials with references/material-schema.md. A local evidence path earns no credit until the file exists relative to the project data file and is inspected. A number also needs a claim link and locator or condition.

Run scripts/gps_score.py only after the route and normalized fields are available. Report rubric_alignment_score, GPS readiness, evidence coverage, gates, caps and source status separately. These are preparation diagnostics, not judging results.

Full diagnosis contract

Use exactly these headings for a full diagnosis:

1. Snapshot
2. Eligibility and rubric basis
3. Project essence
4. Core advantages
5. Top 3 selling points
6. Innovation and opportunity
7. Rubric gap matrix
8. MAP ledger summary
9. GOLD gap
10. Next 3 actions
11. Open questions

Tag each material conclusion as verified, supported, conditional, hypothesis, missing or contradicted. If fewer than three selling points are defensible, show the empty slots and the evidence needed to fill them.

Each next action uses owner + artifact + due date + acceptance check. If the deadline is within 72 hours, prefer a rescue plan that protects eligibility, the strongest claim and the answer evidence.

Saved report naming

Follow the saved Markdown report rules in gps-common. Use the full-diagnosis, quick-triage or specialist filename for the selected mode. A user-supplied filename or destination always takes precedence.

Hard stops

• Do not create a number, customer result, patent status, experiment result or team contribution.
• Do not call a performance result an innovation without the changed mechanism and comparison baseline.
• Do not turn a historical case, old scoring card or training slide into a current rule.
• Do not use award names as readiness bands or claim that GPS predicts an award.
• Do not copy or commit user project materials without explicit permission.

References: references/rules-2026.md, references/material-schema.md, references/rubrics-2025.json.