# Angular 22 + RxJS Enterprise Reference

Evidence label: `generated-needs-review`  
Last reviewed UTC: `2026-06-05T00:00:00Z`

This is a **reference implementation**. It is provided for local review, is not enqueued by the WordPress theme, and must not be described as deployed production code.

## Purpose

The example demonstrates an SEO-first enterprise Angular 22 architecture using:

- Angular 22 package references
- route-level SSR / SSG rendering strategy examples
- standalone components
- TypeScript DTO contracts
- RxJS data-access store patterns
- Python service-boundary reference code
- OpenAPI contracts
- Vitest store/component tests
- Playwright crawlability checks
- security notes around CSP, Trusted Types, and unsafe DOM sinks

## SEO-first rule

Public content should be server-rendered or prerendered. A public route should not be a blank client-only shell that hides headings, body copy, canonical links, or structured data until JavaScript runs.

## Python boundary

The Python backend-reference folder models validation and enrichment behind HTTP contracts. It includes no secrets, no external AI calls, and no production deployment claim.

## Human review gate

Generated or enriched output remains `needs-review` until a human promotes it. No reference example should be treated as automatic publication authority.

## Local run model

```bash
npm install
npm run build
npm test
npm run test:e2e
```

The package is included for architecture review. It may require version adjustment if Angular 22 minor requirements change.

## Reviewer context

- This code is not currently deployed on MikeKappel.com.
- This is not proprietary client source.
- This does not prove every public project is Angular 22.
- This does not perform live AI calls.
- This does not bypass human review.