What is the purpose of the case studies?

Case studies translate resume language into architecture, technologies, architecture notes, and reviewer paths.

Do case studies disclose proprietary implementation details?

They describe architecture patterns and public proof surfaces while protecting private code, secrets, and client-confidential details.

What are the case studies for?

Case studies give technical reviewers a direct path from a resume claim to architecture, evidence stage, related Architecture Notes, and implementation context.

How should strategy-backed case studies be read?

Strategy-backed case studies are presented as architecture background material and refined as implementation details are confirmed.

Which case study should an Angular reviewer open first?

The Angular/Python architecture case study and Angular/RxJS architecture page are the best first path for Angular, TypeScript, RxJS, SSR/SSG, hydration, and testing review.

Case Study / Public Platform / Confirmed Experience

LLMWikis Trust-Labeled Knowledge

A public-platform case study for durable AI-ready knowledge systems, trust labels, source boundaries, governance, and retrieval-friendly content design.

Portfolio label: Confirmed Experience Evidence category: machine-readable-knowledge-governance

Problem / constraint

What needed structure

LLM-facing documentation can become a flat pile of pages with no source state, claim boundary, or reviewer route for humans and AI evaluators.

Legacy risk

What could regress

Knowledge pages need source labels, trust state, and claim boundaries so humans and AI reviewers do not treat drafts as verified facts.

Validation method

How the claim is checked

Check JSON parse, route index consistency, noindex boundary, and evidence labels before promoting research content into public claims.

Architecture strategy

How the proof is structured.

Architecture evidence is presented with private implementation details abstracted and explicit not-claimed boundaries.

Frame knowledge entries around trust labels, route provenance, and claim boundaries. Connect human review pages to llms.txt, llms-full.txt, and public JSON route maps. Keep research artifacts discoverable without promoting private helper indexes. Use operational definitions for specialized research terms.

Implementation evidence

Architecture Notes, evidence-map records, public route index, and documentation map expose reviewer paths.
Research archive remains research library while curated docs remain public review surfaces.
Claim-boundary language blocks certification, production, and authority overclaims.

Result / current status

Evidence-scoped public knowledge-system case study; scale and production claims are intentionally bounded.

Technologies

LLM Wiki Markdown frontmatter metadata trust labels RAG semantic search

Technical value

Knowledge systems designed for humans and agents
Governance-aware content packaging
Retrieval-ready documentation structure

Not claimed / boundary

No issuer-backed credential or certification claim.
No claim that every research page is a production enterprise RAG system.
No private helper index is mirrored to public JSON.

Related architecture notes

/docs/ai-prompt-architecture.md
/docs/project-evidence-map.md

Related AI handoff reference

AI handoff memory package

Related static structured data

/case-studies.json
/evidence-map.json

Suggested reviewer path

/case-studies/
/evidence-map/
/llms.txt
/api/public-route-index.json
/api/documentation-map.json