{
  "generatedAt": "<generated-at>",
  "source": "examples/ai-frontend-architect/sample-profile.yml",
  "rubricSlug": "ai-frontend-architect",
  "rubricName": "AI Frontend Architect Rubric",
  "profile": {
    "name": "Sample AI Frontend Candidate",
    "targetOccupation": "AI Frontend Architect",
    "targetRoles": [
      "AI Frontend Engineer",
      "Angular Architect",
      "Copilot UI Engineer"
    ],
    "weeklyHours": 10,
    "links": {
      "github": "https://github.com/example",
      "portfolio": "https://example.com",
      "linkedin": "https://linkedin.com/in/example"
    },
    "currentPositioning": "Angular frontend engineer building AI copilot UI proof projects.",
    "currentProof": [
      "Angular AI copilot starter",
      "Reusable copilot SDK concept",
      "AI frontend patterns cookbook"
    ],
    "strongSkills": [
      "Angular",
      "TypeScript",
      "enterprise UI architecture"
    ],
    "developingSkills": [
      "MCP tool execution UX",
      "RAG citation UI",
      "agent observability dashboards"
    ],
    "constraints": [
      "Avoid fake production claims",
      "Use mock services where backend integrations are not ready"
    ]
  },
  "summary": {
    "title": "AI Frontend Architect Proof Roadmap",
    "audience": "AI/frontend engineers repositioning into flagship proof-driven roles",
    "positioning": "Angular frontend engineer building AI copilot UI proof projects.",
    "scoreTen": 8.5,
    "scorePercent": 85,
    "strengths": [
      "Enough public proof artifacts exist",
      "GitHub is part of the recruiter path",
      "Portfolio or public case-study surface exists",
      "Proof mentions AI UI patterns recruiters expect",
      "Tool execution and approval flows are visible",
      "Core frontend depth is visible",
      "Interview-ready architecture narrative exists",
      "Truthfulness constraints are explicit"
    ],
    "missingSignals": [
      "The profile headline does not clearly state the AI frontend target yet."
    ],
    "headlineRewrite": "AI Frontend Architect building Angular and TypeScript interfaces for AI copilots, RAG citation workflows, tool execution UX, approval-safe agentic systems."
  },
  "scorecard": [
    {
      "id": "target-positioning",
      "label": "Target role is explicit in public positioning",
      "weight": 15,
      "passed": false,
      "evidence": [],
      "score": 0,
      "gap": "The profile headline does not clearly state the AI frontend target yet.",
      "nextAction": "Rewrite the GitHub profile README and summary so AI frontend architecture is visible in the first screen."
    },
    {
      "id": "proof-volume",
      "label": "Enough public proof artifacts exist",
      "weight": 12,
      "passed": true,
      "evidence": [
        "Lists 3 proof artifacts."
      ],
      "score": 12,
      "gap": null,
      "nextAction": null
    },
    {
      "id": "github-surface",
      "label": "GitHub is part of the recruiter path",
      "weight": 8,
      "passed": true,
      "evidence": [
        "Found github link."
      ],
      "score": 8,
      "gap": null,
      "nextAction": null
    },
    {
      "id": "portfolio-surface",
      "label": "Portfolio or public case-study surface exists",
      "weight": 8,
      "passed": true,
      "evidence": [
        "Found portfolio link."
      ],
      "score": 8,
      "gap": null,
      "nextAction": null
    },
    {
      "id": "streaming-rag-proof",
      "label": "Proof mentions AI UI patterns recruiters expect",
      "weight": 14,
      "passed": true,
      "evidence": [
        "Profile mentions copilot, rag, streaming."
      ],
      "score": 14,
      "gap": null,
      "nextAction": null
    },
    {
      "id": "tool-and-approval-proof",
      "label": "Tool execution and approval flows are visible",
      "weight": 14,
      "passed": true,
      "evidence": [
        "Profile mentions tool, approval, agent."
      ],
      "score": 14,
      "gap": null,
      "nextAction": null
    },
    {
      "id": "skill-depth",
      "label": "Core frontend depth is visible",
      "weight": 11,
      "passed": true,
      "evidence": [
        "Lists 3 strong skills."
      ],
      "score": 11,
      "gap": null,
      "nextAction": null
    },
    {
      "id": "interview-readiness",
      "label": "Interview-ready architecture narrative exists",
      "weight": 10,
      "passed": true,
      "evidence": [
        "Profile mentions architecture, tradeoff, dashboard."
      ],
      "score": 10,
      "gap": null,
      "nextAction": null
    },
    {
      "id": "truthful-constraints",
      "label": "Truthfulness constraints are explicit",
      "weight": 8,
      "passed": true,
      "evidence": [
        "Profile mentions truth, mock, avoid fake."
      ],
      "score": 8,
      "gap": null,
      "nextAction": null
    }
  ],
  "validators": [
    {
      "id": "github-readme-quality",
      "label": "GitHub profile README quality",
      "status": "warn",
      "detail": "GitHub link exists, but the README headline and proof-first framing still need manual review."
    },
    {
      "id": "proof-project-completeness",
      "label": "Proof project completeness",
      "status": "pass",
      "detail": "Profile lists 3 proof artifacts."
    },
    {
      "id": "screenshot-demo-presence",
      "label": "Screenshot/demo presence",
      "status": "warn",
      "detail": "No screenshot or demo asset is named in the current proof list yet."
    },
    {
      "id": "project-description-clarity",
      "label": "Recruiter-readable project descriptions",
      "status": "pass",
      "detail": "Project names should state what they prove, not only a repository title."
    },
    {
      "id": "truthfulness-claim-risk",
      "label": "Truthfulness claim risk",
      "status": "pass",
      "detail": "Current profile language stays within proof-oriented claims."
    }
  ],
  "metrics": {
    "proofDensity": 75,
    "claimSupportRatio": 89,
    "portfolioClarity": 100,
    "recruiterScanReadiness": 100
  },
  "backlog": [
    {
      "priority": 1,
      "title": "Target role is explicit in public positioning",
      "gap": "The profile headline does not clearly state the AI frontend target yet.",
      "nextAction": "Rewrite the GitHub profile README and summary so AI frontend architecture is visible in the first screen."
    }
  ],
  "projects": [
    {
      "title": "Angular AI Copilot Starter",
      "problem": "Most frontend portfolios do not prove streaming AI UX, cited responses, and safe action flows in one coherent artifact.",
      "solution": "Build a local-first Angular demo with streaming chat, RAG citation cards, tool timeline, and human approval states.",
      "recruiterTakeaway": "This project proves the candidate can design AI product interfaces beyond a basic chatbot shell.",
      "interviewTalkingPoints": [
        "Partial token rendering without layout jank",
        "How citations signal trust and confidence",
        "How to represent tool execution visibly",
        "Why risky actions require approvals"
      ]
    },
    {
      "title": "UI-Aware Agent Demo",
      "problem": "Most AI demos show a chat panel, not an agent participating in the visible workflow.",
      "solution": "Build a demo with context inspector, suggested actions, approval checkpoints, and recovery states.",
      "recruiterTakeaway": "This proves the candidate understands agent-aware product UX and operational legibility.",
      "interviewTalkingPoints": [
        "Difference between chat UI and UI-aware agents",
        "Recovery states after interrupted steps",
        "How visible context changes trust",
        "How approval friction is balanced"
      ]
    },
    {
      "title": "Enterprise Agent Approval Workflow",
      "problem": "Enterprise AI tooling needs governance-grade action review, not only delight-driven UI.",
      "solution": "Build an approval queue, risk tiers, reviewer roles, and an audit log around simulated agent actions.",
      "recruiterTakeaway": "This proves enterprise judgment, not only frontend polish.",
      "interviewTalkingPoints": [
        "What makes approval UX different from a confirm dialog",
        "How to classify action risk tiers",
        "How audit trails affect interface design",
        "How to keep governance flows usable"
      ]
    }
  ],
  "githubPlan": {
    "headlineRewrite": "AI Frontend Architect building Angular and TypeScript interfaces for AI copilots, RAG citation workflows, tool execution UX, approval-safe agentic systems.",
    "repoTopics": [
      "angular",
      "typescript",
      "ai-frontend",
      "copilot-ui",
      "rag",
      "tool-execution",
      "agentic-ui",
      "enterprise-ai"
    ],
    "readmeChecklist": [
      {
        "item": "Lead with what the project proves, not just the stack.",
        "done": false
      },
      {
        "item": "Show one screenshot, GIF, or concrete visual in the first screen.",
        "done": false
      },
      {
        "item": "Add a 'mocked vs real' section that is unambiguous.",
        "done": false
      },
      {
        "item": "Explain architecture decisions in recruiter-readable language.",
        "done": false
      },
      {
        "item": "Add a roadmap that separates built work from planned work.",
        "done": false
      },
      {
        "item": "Make local setup copy-paste simple and verified.",
        "done": false
      }
    ]
  },
  "interviewMap": [
    {
      "topic": "Streaming response UX",
      "proofPrompt": "Prepare one real example that proves streaming response ux."
    },
    {
      "topic": "RAG citation trust states",
      "proofPrompt": "Prepare one real example that proves rag citation trust states."
    },
    {
      "topic": "Tool-call timeline design",
      "proofPrompt": "Prepare one real example that proves tool-call timeline design."
    },
    {
      "topic": "Human approval before risky actions",
      "proofPrompt": "Prepare one real example that proves human approval before risky actions."
    },
    {
      "topic": "Enterprise-safe agent interfaces",
      "proofPrompt": "Prepare one real example that proves enterprise-safe agent interfaces."
    },
    {
      "topic": "Moving from mocks to real backends",
      "proofPrompt": "Prepare one real example that proves moving from mocks to real backends."
    }
  ],
  "weeklyPlan": {
    "weeklyTheme": "Convert current frontend experience into visible AI proof.",
    "weeklyHours": 10,
    "outcomes": [
      "Tighten one public profile surface.",
      "Ship one stronger proof artifact.",
      "Write one interview-safe explanation of a real decision."
    ],
    "dailyPlan": [
      {
        "day": "Monday",
        "task": "Rewrite the GitHub profile README and summary so AI frontend architecture is visible in the first screen.",
        "proofArtifact": "Target role is explicit in public positioning"
      },
      {
        "day": "Tuesday",
        "task": "Rewrite one project summary so it states what the project proves.",
        "proofArtifact": "Proof inventory refresh"
      },
      {
        "day": "Wednesday",
        "task": "Capture one screenshot, GIF, or annotated walkthrough for the flagship project.",
        "proofArtifact": "Visual proof"
      },
      {
        "day": "Thursday",
        "task": "Draft one STAR story from a real project decision.",
        "proofArtifact": "Interview narrative"
      },
      {
        "day": "Friday",
        "task": "Add a mocked-vs-real section and recruiter takeaway to the flagship README.",
        "proofArtifact": "README clarity"
      }
    ]
  },
  "truthfulnessGuardrails": [
    "Do not claim production usage unless the public artifact proves it.",
    "Label mock services as mock services in every README and demo.",
    "Separate built evidence from planned roadmap work.",
    "Do not invent metrics, user counts, stars, or contribution outcomes.",
    "Only publish claims you can defend in a recruiter screen or interview."
  ],
  "comparison": [
    "Use occupation-ops when the main problem is weak public proof before applying.",
    "Use job-search pipeline tools when the main problem is scanning, tracking, or operationalizing active applications.",
    "Occupation-ops is not a tracker, scanner, or mass-apply workflow; it is a proof engine for candidate credibility."
  ]
}