{
  "status": {
    "comingSoon": "Coming soon",
    "rag": "RAG chat",
    "streaming": "Streaming first",
    "trialCode": "Trial code"
  },
  "hubRow": {
    "eyebrow": "ai talk",
    "title": "AI Talk Entry Hub",
    "description": "This page is the public entry for the AI capabilities: establish RAG knowledge chat, resume guidance, and avatar presentation first, then grow into real trial-code access, streaming answers, and admin-side governance.",
    "plan": {
      "1": {
        "title": "RAG knowledge / persona Q&A",
        "description": "Use the published resume, project history, and future knowledge sources as the basis for recruiter-facing Q&A."
      },
      "2": {
        "title": "Resume guidance",
        "description": "Generate improvement ideas and analysis on top of the current resume structure and future AI workflows."
      },
      "3": {
        "title": "Avatar introduction",
        "description": "Reserve a dedicated media route and contract first, then add real audio/video and avatar interaction later."
      }
    },
    "profile": {
      "eyebrow": "Profile Snapshot",
      "nextTitle": "What lands next?",
      "nextDescription": "The next milestone focuses on trial-code chat, the admin governance loop, and then grows the advisory and avatar capabilities into dedicated workspaces."
    }
  },
  "featureCards": {
    "rag": {
      "front": {
        "eyebrow": "Entry One",
        "title": "RAG knowledge / persona Q&A",
        "description": "Turn the published resume and future knowledge sources into a traceable public Q&A entry.",
        "badge": "Chat entry",
        "status": "Not open yet"
      },
      "back": {
        "eyebrow": "Knowledge chat",
        "title": "RAG chat workspace",
        "description": "This route currently shows product planning only. Trial code and live chat are not open yet.",
        "tags": {
          "one": "Trial code",
          "two": "10 turns"
        },
        "details": {
          "one": "Resume data, project history, and future knowledge sources become one retrieval context.",
          "two": "Answers surface source snippets and remaining quota so the rationale is easy to inspect."
        },
        "cta": "Not open yet"
      }
    },
    "resumeAdvisor": {
      "front": {
        "eyebrow": "Entry Two",
        "title": "Resume guidance",
        "description": "Use the current resume structure and AI analysis to produce more actionable improvement suggestions.",
        "badge": "Admin feature",
        "status": "Public info only"
      },
      "back": {
        "eyebrow": "AI guidance",
        "title": "Resume guidance",
        "description": "This capability builds on the current resume structure, while the real workflow still lives in the admin workbench.",
        "tags": {
          "one": "AI + RAG",
          "two": "Structured guidance"
        },
        "details": {
          "one": "Inputs stay grounded in `StandardResume`, published snapshots, and analysis outputs.",
          "two": "Later it can grow into markdown / PDF output, diff previews, and apply flows."
        },
        "cta": "View public overview"
      }
    },
    "avatar": {
      "front": {
        "eyebrow": "Entry Three",
        "title": "Avatar / self-introduction",
        "description": "A dedicated route for media presentation, self-introduction, and future avatar interaction.",
        "badge": "Dedicated route",
        "status": "coming soon"
      },
      "back": {
        "eyebrow": "Media route",
        "title": "Avatar introduction",
        "description": "The avatar grows in its own route. This round keeps the entry, copy, and media boundary in place.",
        "tags": {
          "one": "Dedicated media route",
          "two": "coming soon"
        },
        "details": {
          "one": "Later this route can own video, TTS, posters, and media playback state.",
          "two": "The page will keep expanding around persona data, assets, and control zones."
        },
        "cta": "Open avatar entry"
      }
    }
  },
  "resumeAdvisorPage": {
    "eyebrow": "resume advisor",
    "title": "Resume guidance",
    "description": "This is the public explainer route: clarify the capability boundary, input baseline, and advanced direction first, while the real generation workflow stays in admin.",
    "badges": {
      "one": "Structured baseline",
      "two": "Admin workbench"
    },
    "blocks": {
      "overview": {
        "eyebrow": "Capability",
        "title": "What does it do now?",
        "description": "It works from the current resume structure, published snapshots, and AI analysis instead of starting over from an unstructured block of text."
      },
      "workflow": {
        "eyebrow": "Phase one",
        "title": "How does the first version land?",
        "description": "The base version focuses on suggestion summaries, rewrite directions, and export references. One-click apply and field-level diff flows stay in the advanced phase."
      },
      "boundary": {
        "eyebrow": "Boundary",
        "title": "Why is this page only an explainer?",
        "description": "Because the real governance and review loop belongs in admin. The public site currently keeps a lightweight overview so visitors understand the upcoming capability."
      }
    },
    "primaryCta": "Back to AI Talk hub",
    "secondaryCta": "Open RAG chat"
  },
  "introPage": {
    "eyebrow": "ai intro",
    "title": "AI Intro · Unlock {name}",
    "description": "A standalone guided AI intro page: start with curated questions, then let the portrait map light up piece by piece as answers land.",
    "badges": {
      "guided": "Guided questions",
      "fragments": "10 fragments"
    },
    "chat": {
      "title": "Guided chat window",
      "description": "The first version only exposes preset questions, keeping the experience focused and easy to sync with the portrait map.",
      "resetAction": "Reset progress",
      "messages": {
        "1": "Hi, I can guide you through this resume in 10 focused questions.",
        "2": "Choose one question below to start; each completed answer updates the progress map on the right."
      }
    },
    "questions": {
      "profile": "Who are you, and what direction are you focused on now?",
      "latestProject": "What was your latest project?",
      "stack": "What technologies do you mainly use?",
      "aiPractice": "How do you use AI in real projects?",
      "ragAgent": "What have you practiced around RAG or Agent work?",
      "engineering": "How do you keep projects maintainable?",
      "collaboration": "What collaboration or delivery experience do you have?",
      "hobbies": "What do you enjoy outside work?",
      "writing": "What articles, notes, or public output do you have?",
      "future": "What do you want to explore next?"
    },
    "answers": {
      "profile": "I started from frontend work and have gradually grown into full-stack and AI engineering practice, with a current focus on combining product delivery, RAG, and Agent learning.",
      "latestProject": "Recently I have been building my-resume around public AI Chat, RAG knowledge, resume import recognition, and admin-side governance loops.",
      "stack": "My main stack includes Next.js, React, NestJS, TypeScript, Drizzle, HeroUI, and AI engineering pieces around providers, embeddings, and RAG.",
      "aiPractice": "I treat AI as a real product capability: define boundaries first, then add logs, structured output, citations, and reversible frontend/backend contracts.",
      "ragAgent": "On RAG, I have built resume knowledge, user document ingestion, explainable Q&A, and citation display. Agent work is now growing through LangGraph and AGUI-style practice.",
      "engineering": "I care about types, tests, development logs, and branch flow. The goal is not to build everything at once, but to keep every issue verifiable and reversible.",
      "collaboration": "I tend to split complex work into milestones and issues with clear acceptance criteria, while recording risks and tradeoffs during implementation.",
      "hobbies": "Outside work I enjoy music and badminton. They help me keep rhythm and energy, and make the profile feel more human than a list of technical tags.",
      "writing": "I turn AI Agent, RAG, and full-stack practice into learning notes and project docs, so the process can be reviewed and later shaped into tutorials.",
      "future": "Next I want to go deeper into LangGraph, multi-domain RAG, AGUI-style interaction, and a more expressive AI resume intro page."
    },
    "unlock": {
      "eyebrow": "unlock map",
      "title": "Persona fragment map",
      "description": "This is the static shell first: later answers will light up each theme and turn the page into a collectible discovery path.",
      "progressTitle": "Unlock progress",
      "progressText": "{completed} / {total} fragments unlocked",
      "progressAria": "{completed} of {total} persona fragments unlocked",
      "noteTitle": "Current stage",
      "noteDescription": "This issue only establishes the route and layout shell. The question state machine, real answers, and unlock logic continue in follow-up issues.",
      "completeTitle": "Full persona map unlocked",
      "completeDescription": "All 10 themes are complete, and the right-side map has entered its full state. Next, these unlock results can feed richer cards and real answers.",
      "topics": {
        "profile": "Profile",
        "latestProject": "Latest project",
        "stack": "Tech stack",
        "aiPractice": "AI practice",
        "ragAgent": "RAG / Agent",
        "engineering": "Engineering",
        "collaboration": "Collaboration",
        "hobbies": "Hobbies",
        "writing": "Writing",
        "future": "Future"
      },
      "keywords": {
        "profile": "Full-stack",
        "latestProject": "my-resume",
        "stack": "TypeScript",
        "aiPractice": "AI engineering",
        "ragAgent": "RAG",
        "engineering": "Quality",
        "collaboration": "Planning",
        "hobbies": "Rhythm",
        "writing": "Notes",
        "future": "Agent"
      },
      "summaries": {
        "profile": "Profile unlocked: starting from frontend and growing into full-stack and AI engineering practice.",
        "latestProject": "Latest project unlocked: my-resume now carries AI Chat, RAG, and resume workflow practice.",
        "stack": "Tech stack unlocked: Next.js, NestJS, TypeScript, and AI engineering are the current backbone.",
        "aiPractice": "AI practice unlocked: boundaries, logs, structured output, and traceable citations matter.",
        "ragAgent": "RAG / Agent unlocked: explainable Q&A is growing toward LangGraph and AGUI.",
        "engineering": "Engineering unlocked: types, tests, logs, and small issues keep the system maintainable.",
        "collaboration": "Collaboration unlocked: complex work starts with milestones, issues, and acceptance criteria.",
        "hobbies": "Hobbies unlocked: music and badminton add rhythm beyond technical labels.",
        "writing": "Writing unlocked: learning and project practice are continuously turned into reviewable material.",
        "future": "Future unlocked: LangGraph, multi-domain RAG, and AGUI interaction are the next focus."
      }
    },
    "primaryCta": "Back to AI Talk hub",
    "secondaryCta": "Open current chat entry"
  },
  "entry": {
    "eyebrow": "ai talk",
    "title": "AI Talk Hub",
    "description": "This becomes the public AI entry for the site: establish RAG chat, avatar intro, and session history first, then plug in real trial-code access, streaming Q&A, and knowledge-base governance.",
    "path": {
      "eyebrow": "Current Stage",
      "title": "Establish the entry and sub-route semantics first",
      "lineOne": "The hub explains what the product can and cannot do before the real conversation backend lands.",
      "lineTwo": "The real Q&A flow will live in dedicated chat and session workspaces so future interaction complexity does not force a structural rewrite.",
      "lineThree": "The avatar entry keeps its own page, media contract, and control-zone boundary from day one."
    },
    "prompts": {
      "eyebrow": "Prompt Direction",
      "title": "Questions it should answer later",
      "one": "What projects has he focused on in recent years?",
      "two": "Is he more frontend-oriented or full-stack?",
      "three": "What should an interviewer ask about next?"
    }
  },
  "cards": {
    "chat": {
      "eyebrow": "Entry One",
      "title": "RAG Chat",
      "description": "This card is currently informational only. Trial code and live chat are not open yet.",
      "badge": "SSR entry + sub-route workspace",
      "cta": "Not open yet"
    },
    "avatar": {
      "eyebrow": "Entry Two",
      "title": "Avatar Introduction",
      "description": "A dedicated page for video, TTS, and future media interaction. This round only establishes the page boundary and contract.",
      "badge": "Dedicated media page",
      "cta": "Open avatar entry"
    },
    "sessions": {
      "eyebrow": "Entry Three",
      "title": "Session History",
      "description": "Later every real conversation will get a dedicated session page with remaining turns, source snippets, and history playback.",
      "badge": "Coming soon",
      "helper": "This round only keeps the information architecture. The revisit entry arrives once the real chat flow exists."
    }
  },
  "chat": {
    "eyebrow": "rag chat",
    "title": "RAG Chat Entry",
    "description": "This page currently serves as a capability preview. Live Q&A is not open yet.",
    "badgeQuota": "10-turn quota",
    "badgeStreaming": "Streaming response",
    "steps": {
      "code": {
        "eyebrow": "Step One",
        "title": "Trial code redemption",
        "description": "The input flow is reserved for now. Trial code redemption will be enabled in a future release."
      },
      "session": {
        "eyebrow": "Step Two",
        "title": "Session start",
        "description": "Once the quota is confirmed, a dedicated session is created and the user moves into the real conversation workspace."
      },
      "citations": {
        "eyebrow": "Step Three",
        "title": "Source snippets",
        "description": "Answers should expose source snippets, supporting context, and the remaining-turn status as early as possible."
      }
    },
    "workspacePreview": {
      "eyebrow": "Next Step",
      "title": "Preview the future session workspace",
      "description": "The real chat pipeline is not open yet, and this page currently previews the future session workspace.",
      "primaryCta": "Preview session workspace",
      "secondaryCta": "Back to AI Talk hub"
    }
  },
  "session": {
    "eyebrow": "session workspace",
    "title": "Session Workspace · {sessionId}",
    "description": "The real message timeline, cited sources, and remaining-turn status will all live here. For now this page only establishes its responsibility boundary.",
    "badgeTimeline": "Message timeline",
    "badgeSources": "Source snippets",
    "blocks": {
      "messages": {
        "eyebrow": "Conversation",
        "title": "Message timeline",
        "description": "This area later renders user prompts, streaming answers, and feedback actions."
      },
      "sources": {
        "eyebrow": "Retrieval",
        "title": "Source snippets",
        "description": "RAG citations, matched documents, and explanation notes will be grouped here."
      },
      "quota": {
        "eyebrow": "Status",
        "title": "Quota and state",
        "description": "Remaining turns, linked trial-code metadata, and error states will live here for demos and future auditing."
      }
    },
    "backToChat": "Back to RAG chat",
    "backToHub": "Back to AI Talk hub"
  },
  "avatar": {
    "eyebrow": "avatar intro",
    "title": "Avatar Introduction",
    "description": "The avatar route will own self-introduction, media playback, and future interaction controls. This round keeps it as a contract-first placeholder.",
    "intro": {
      "eyebrow": "Self-introduction",
      "lineOne": "Phase one starts with a short self-introduction and capability framing so visitors know this is not just a static video page.",
      "lineTwo": "Later this page can grow into voice, video, or avatar-driven playback without mixing those concerns into the chat workspace.",
      "lineThree": "The route is intentionally reserved for persona data, media assets, playback state, and future control panels."
    },
    "contract": {
      "eyebrow": "Route Contract",
      "title": "Reserve clear boundaries for future media features",
      "items": {
        "role": {
          "title": "Role metadata",
          "description": "Reserve structured persona data, intro scripts, and presentation tone for the avatar route."
        },
        "media": {
          "title": "Media assets",
          "description": "Reserve poster, audio, video, and cover slots so real media capabilities can be added later."
        },
        "controls": {
          "title": "Control panel",
          "description": "Reserve playback, mute, replay, and future action controls instead of pushing them into generic content cards."
        }
      }
    },
    "backToHub": "Back to AI Talk hub"
  }
}
