{
  "schemaVersion": "1.0.0",
  "generatedAt": "2026-06-08T00:00:00.000Z",
  "contentVersion": "git:fd6bd6192f024e161dad661ec60dc207da35b5cf-dirty",
  "sourceRole": "public-evidence",
  "instructionRole": "none",
  "subject": "person:yuanhao-chen",
  "claims": [
    {
      "id": "claim:datasentinel-public-proof-boundary",
      "artifact": "project:datasentinel",
      "canonicalUrl": "https://yuanhaochen.dev/work/datasentinel",
      "claim": "Models the governance loop around scattered personal-data evidence: scan, redact, assign owner, review, and audit - without claiming production tenant-wide deletion.",
      "claimStrength": "public-prototype-evidence",
      "evidence": [
        {
          "type": "site-page",
          "url": "https://yuanhaochen.dev/work/datasentinel",
          "description": "Human-readable project page with problem, shipped surface, evidence, inspect path, and boundary."
        },
        {
          "type": "repository",
          "url": "https://github.com/89325516/datasentinel-gdpr",
          "description": "The README exposes the live demo, user guide, API contract, repository map, validation commands, and project boundaries around deletion, legal advice, and production tenant integrations."
        },
        {
          "type": "inspection-guidance",
          "description": "Inspect the README first, then `contracts/openapi.yaml`, the product docs, backend review/audit modules, evidence assembly paths, and tests around review decisions."
        }
      ],
      "doesNotProve": [
        "Deletion is simulated. This is not legal advice, not a production tenant-wide Microsoft 365 inventory, and not proof of production deletion integration or compliance readiness."
      ],
      "bestInspectionPath": [
        "Inspect the README first, then `contracts/openapi.yaml`, the product docs, backend review/audit modules, evidence assembly paths, and tests around review decisions."
      ],
      "roleRelevance": [
        "Applied AI Engineer",
        "Privacy / Trust Engineering",
        "Agent Workflow Infrastructure",
        "Forward Deployed Engineer"
      ],
      "nextQuestion": "Which review event should become impossible to skip before a sensitive-data system earns trust?",
      "lastReviewed": "2026-06-01"
    },
    {
      "id": "claim:semantic-video-public-proof-boundary",
      "artifact": "project:semantic-video",
      "canonicalUrl": "https://yuanhaochen.dev/work/semantic-video",
      "claim": "Tests whether video meaning can travel as a validated sidecar: segments, speakers, objects, rights, provenance, consent rules, and fallbacks.",
      "claimStrength": "public-prototype-evidence",
      "evidence": [
        {
          "type": "site-page",
          "url": "https://yuanhaochen.dev/work/semantic-video",
          "description": "Human-readable project page with problem, shipped surface, evidence, inspect path, and boundary."
        },
        {
          "type": "repository",
          "url": "https://github.com/89325516/universal-semantic-video",
          "description": "The README documents the sidecar shape, conformance rules, standards posture, public-safety hook, and explicit pre-1.0 limitations."
        },
        {
          "type": "inspection-guidance",
          "description": "Inspect `schema/usv.schema.json`, `examples/lite/`, `docs/spec/USV-Core-Conformance.md`, `docs/STANDARDS.md`, the CLI commands, and the CI workflow."
        }
      ],
      "doesNotProve": [
        "USV is not a codec, player, hosted API, AI translation system, ASR/OCR pipeline, lip-sync tool, or native container embedding layer yet."
      ],
      "bestInspectionPath": [
        "Inspect `schema/usv.schema.json`, `examples/lite/`, `docs/spec/USV-Core-Conformance.md`, `docs/STANDARDS.md`, the CLI commands, and the CI workflow."
      ],
      "roleRelevance": [
        "Applied AI Engineer",
        "Agent Workflow Infrastructure"
      ],
      "nextQuestion": "What would make semantic video evidence portable enough for real creative, localization, review, and rights workflows?",
      "lastReviewed": "2026-05-21"
    },
    {
      "id": "claim:vault-bridge-public-proof-boundary",
      "artifact": "project:vault-bridge",
      "canonicalUrl": "https://yuanhaochen.dev/work/vault-bridge",
      "claim": "Separates AI suggestions from durable GitHub writes through proposal tokens, digest-bound confirmation, path safety, expected base SHA, and conflict handling.",
      "claimStrength": "public-prototype-evidence",
      "evidence": [
        {
          "type": "site-page",
          "url": "https://yuanhaochen.dev/work/vault-bridge",
          "description": "Human-readable project page with problem, shipped surface, evidence, inspect path, and boundary."
        },
        {
          "type": "repository",
          "url": "https://github.com/89325516/serverless-vault-bridge",
          "description": "The README names the propose-review-commit tool flow and failure semantics for path traversal, token mismatch, digest mismatch, path mismatch, base SHA mismatch, and CAS conflicts."
        },
        {
          "type": "inspection-guidance",
          "description": "Inspect `src/`, `test/`, `wrangler.toml.example`, the OpenAPI schema, and tests for auth, path safety, token binding, CAS conflicts, and MCP parity."
        }
      ],
      "doesNotProve": [
        "It is not a sync engine, database, agent framework, or direct-write API for high-risk automation. It proves a reviewable write boundary, not a full knowledge-management product."
      ],
      "bestInspectionPath": [
        "Inspect `src/`, `test/`, `wrangler.toml.example`, the OpenAPI schema, and tests for auth, path safety, token binding, CAS conflicts, and MCP parity."
      ],
      "roleRelevance": [
        "Applied AI Engineer",
        "Privacy / Trust Engineering",
        "Agent Workflow Infrastructure"
      ],
      "nextQuestion": "Where should approval live when AI can prepare a change but should not own the final mutation?",
      "lastReviewed": "2026-05-18"
    },
    {
      "id": "claim:tum-search-public-proof-boundary",
      "artifact": "project:tum-search",
      "canonicalUrl": "https://yuanhaochen.dev/work/tum-search",
      "claim": "Explores campus knowledge search as a system problem: crawling, summaries, embeddings, graph structure, and live update feedback.",
      "claimStrength": "public-prototype-evidence",
      "evidence": [
        {
          "type": "site-page",
          "url": "https://yuanhaochen.dev/work/tum-search",
          "description": "Human-readable project page with problem, shipped surface, evidence, inspect path, and boundary."
        },
        {
          "type": "repository",
          "url": "https://github.com/89325516/tum-search",
          "description": "The README documents the crawler, summarization, vector-search, knowledge-graph, WebSocket update, setup, environment, and admin-tool surfaces."
        },
        {
          "type": "inspection-guidance",
          "description": "Inspect the README, `web_server.py`, dependency scripts, crawler/summarization paths, Qdrant configuration, WebSocket update path, and admin scripts for database clearing and summary regeneration."
        }
      ],
      "doesNotProve": [
        "The public README exposes a research/prototype search system, not a production campus search service, validated ranking benchmark, or official university information product."
      ],
      "bestInspectionPath": [
        "Inspect the README, `web_server.py`, dependency scripts, crawler/summarization paths, Qdrant configuration, WebSocket update path, and admin scripts for database clearing and summary regeneration."
      ],
      "roleRelevance": [
        "Agent Workflow Infrastructure",
        "Forward Deployed Engineer"
      ],
      "nextQuestion": "Which signal should be trusted first when graph structure, semantic similarity, freshness, and keyword match disagree?",
      "lastReviewed": "2025-11-29"
    },
    {
      "id": "claim:nitro-judge-public-proof-boundary",
      "artifact": "project:nitro-judge",
      "canonicalUrl": "https://yuanhaochen.dev/work/nitro-judge",
      "claim": "A baseline-discipline project: reproducible reading-time prediction, local evaluation, acceptance rules, target audit, and visible experiment boundaries.",
      "claimStrength": "public-prototype-evidence",
      "evidence": [
        {
          "type": "site-page",
          "url": "https://yuanhaochen.dev/work/nitro-judge",
          "description": "Human-readable project page with problem, shipped surface, evidence, inspect path, and boundary."
        },
        {
          "type": "repository",
          "url": "https://github.com/89325516/nitro-ai-judge",
          "description": "The README distinguishes local estimates from hidden Nitro leaderboard scores, documents rejected or unpromoted experiments, and states when an experiment is not allowed to replace the baseline."
        },
        {
          "type": "inspection-guidance",
          "description": "Inspect `solution.py`, `evaluate.py`, `docs/submission_pipeline_design.md`, `ACCEPTANCE_CRITERIA.md`, experiment reports, and target-audit commands."
        }
      ],
      "doesNotProve": [
        "Local validation is not the hidden leaderboard, and experimental models are not promoted unless local or official evidence supports them. This repo proves evaluation discipline more than final model superiority."
      ],
      "bestInspectionPath": [
        "Inspect `solution.py`, `evaluate.py`, `docs/submission_pipeline_design.md`, `ACCEPTANCE_CRITERIA.md`, experiment reports, and target-audit commands."
      ],
      "roleRelevance": [
        "Applied AI Engineer"
      ],
      "nextQuestion": "Which failure class would justify a more complex model instead of cleaner data, features, validation, or target analysis?",
      "lastReviewed": "2026-04-25"
    },
    {
      "id": "claim:aisd-redesign-public-proof-boundary",
      "artifact": "project:aisd-redesign",
      "canonicalUrl": "https://yuanhaochen.dev/work/aisd-redesign",
      "claim": "Tests whether cinematic interface craft can clarify a coding-assessment workflow without blurring roles, backend assumptions, attribution, or security boundaries.",
      "claimStrength": "public-prototype-evidence",
      "evidence": [
        {
          "type": "site-page",
          "url": "https://yuanhaochen.dev/work/aisd-redesign",
          "description": "Human-readable project page with problem, shipped surface, evidence, inspect path, and boundary."
        },
        {
          "type": "repository",
          "url": "https://github.com/89325516/aisd-cinematic-redesign",
          "description": "The README records the upstream commit, unlicensed-source boundary, attribution file, module responsibilities, useful routes, backend assumptions, API notes, and security rules."
        },
        {
          "type": "inspection-guidance",
          "description": "Inspect `ATTRIBUTION.md`, `FINAL_ACCEPTANCE_CRITERIA.md`, `docs/frontend-cinematic-redesign-discussion.md`, `hyperframes/aisd-motion/`, frontend workspace routes, and API boundary assumptions."
        }
      ],
      "doesNotProve": [
        "The repository is a derivative redesign of an upstream academic project. Attribution is explicit, and the page should not imply a license grant, production deployment, or full backend ownership beyond what the repository states."
      ],
      "bestInspectionPath": [
        "Inspect `ATTRIBUTION.md`, `FINAL_ACCEPTANCE_CRITERIA.md`, `docs/frontend-cinematic-redesign-discussion.md`, `hyperframes/aisd-motion/`, frontend workspace routes, and API boundary assumptions."
      ],
      "roleRelevance": [
        "Forward Deployed Engineer"
      ],
      "nextQuestion": "Which interaction should become calmer before the motion system becomes more ambitious?",
      "lastReviewed": "2026-05-05"
    }
  ]
}