ahmido 09dc9988cb 406: Provider & Policy Domain Public Taxonomy (#401 )

## Summary
- add the 406 feature specification for a public provider and policy-domain taxonomy surface
- include plan, research, data model, quickstart, checklist, and public route contract artifacts
- update agent context with the 406 website technology notes

## Notes
- this PR is spec and planning work only
- no runtime website implementation is included yet

## Validation
- reviewed pending git scope before commit
- verified `Agents.md` has no editor diagnostics

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #401

2026-05-26 12:54:23 +00:00

5.4 KiB

Raw Permalink Blame History

Quickstart: Provider & Policy Domain Public Taxonomy

1. Confirm Scope

Work from repository root:

cd /Users/ahmeddarrazi/Documents/projects/wt-website
git status --short --branch
cat package.json
cat pnpm-workspace.yaml 2>/dev/null || true
cat apps/website/package.json
find apps/website -maxdepth 3 -type f | sort | sed -n '1,220p'

Scope boundaries:

Allowed: /Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/**
Allowed: /Users/ahmeddarrazi/Documents/projects/wt-website/specs/406-provider-policy-domain-public-taxonomy/**
Forbidden: /Users/ahmeddarrazi/Documents/projects/wt-website/apps/platform/**
Forbidden: root workspace script contract changes

2. Implement The Route

Preferred route:

/platform/domains
/en/platform/domains

Expected files:

/Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/src/pages/platform/domains.astro
/Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/src/pages/en/platform/domains.astro
/Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/src/components/pages/DomainTaxonomyPage.astro

Follow the existing PlatformPage.astro and TrustPage.astro route/component pattern.

3. Add Localized Content

Use the existing copy file:

/Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/src/data_files/site-copy.ts

Add German and English taxonomy copy with:

hero copy
metadata
status legend
Microsoft 365 domain matrix
future-provider rows
buyer-facing cards
CTA labels and destinations

4. Use Safe Status Defaults

Use these public status meanings:

Current focus / Aktueller Fokus
Planned domain / Geplante Domaene
Architecture direction / Architektur-Richtung
Not currently available / Derzeit nicht verfuegbar
Not claimed / Nicht beansprucht

Default statuses:

Intune / Endpoint Policies: current focus only if repo/product truth supports it
Entra / Identity & Access: planned domain unless verified current
Conditional Access: planned domain unless verified current
SharePoint / OneDrive Sharing: planned domain unless verified current
Enterprise Apps / Service Principals: planned domain unless verified current
Security Posture Evidence: planned domain unless verified current
Provider Permissions & Readiness: current or planned based on repo/product truth
Review Packs & Governance Evidence: current or planned based on repo/product truth
Google Workspace / Google Cloud: architecture direction unless verified current
AWS: architecture direction unless verified current
Okta / Identity Providers: architecture direction unless verified current
Other SaaS policy systems: architecture direction unless verified current

5. Integrate Lightly

Add only light discoverability:

homepage teaser if it fits current copy structure
platform-page teaser or CTA
footer/nav link only if current IA supports it without clutter

Every CTA must use a real route, real anchor, or real contact destination.

6. Update Smoke Coverage

Expected test updates:

/Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/tests/smoke/public-routes.spec.ts
/Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/tests/smoke/interaction.spec.ts
/Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/tests/smoke/smoke-helpers.ts

Cover:

/platform/domains
/en/platform/domains
metadata for both routes
public links
mobile readability
no horizontal overflow
status labels
no false provider claims

7. Run Validation

Run only scripts that exist:

corepack pnpm --filter @tenantatlas/website build
corepack pnpm --filter @tenantatlas/website test

Optional if formatting changed broadly:

corepack pnpm --filter @tenantatlas/website format:check

Run static source scan:

grep -RIn \
  -e 'href="#"' \
  -e 'Intune Management Tool' \
  -e 'Google supported' \
  -e 'AWS supported' \
  -e 'Okta supported' \
  -e 'multi-cloud supported' \
  -e 'all cloud providers' \
  -e 'every SaaS platform' \
  -e 'provider-agnostic restore' \
  -e 'universal policy governance' \
  -e 'automatic remediation' \
  -e 'automatic restore' \
  -e 'self-healing' \
  -e 'real-time drift' \
  -e 'immutable backups' \
  -e 'gerichtsfeste Nachweise' \
  -e 'lueckenlose Evidenz' \
  apps/website/src apps/website/public 2>/dev/null || true

If generated output is committed, scan it too:

grep -RIn \
  -e 'href="#"' \
  -e 'Intune Management Tool' \
  -e 'Google supported' \
  -e 'AWS supported' \
  -e 'Okta supported' \
  -e 'multi-cloud supported' \
  -e 'all cloud providers' \
  -e 'every SaaS platform' \
  -e 'provider-agnostic restore' \
  -e 'universal policy governance' \
  -e 'automatic remediation' \
  -e 'automatic restore' \
  -e 'self-healing' \
  -e 'real-time drift' \
  -e 'immutable backups' \
  -e 'gerichtsfeste Nachweise' \
  -e 'lueckenlose Evidenz' \
  apps/website/dist 2>/dev/null || true

8. Browser Smoke

If preview is available:

WEBSITE_PORT=${WEBSITE_PORT:-4321} corepack pnpm --filter @tenantatlas/website preview

Verify:

/platform/domains loads
/en/platform/domains loads
homepage/platform teaser link works
nav/footer links work if added
desktop layout is readable
mobile layout is readable
status labels are understandable
Intune is not the whole product category
Google/AWS/Okta are not presented as live support
no CTA uses a fake route

5.4 KiB Raw Permalink Blame History