---
uai: "1.0"
type: topic-memory
status: active
stable_id: iarpg-publisher-contact
project: iarpg.com
release: IARPG-OPS-2
version: "2.0.31-wip"
review_state: current-until-superseded
---

# Publisher Contact and Public Profile

## Current Publication Contract

- `/contact` is the canonical public Contact Us and publisher-profile route.
- The route identifies the individual publisher, provides user-authorized direct contact fields, summarizes general professional and creative interests, and links to first-party public profiles.
- The public summary intentionally excludes employer names, client names, job-by-job chronology, private implementation details, and unsupported claims.
- The page introduces no form, account, analytics, remote database, upload service, or server-side message retention.
- The mailing-address notice distinguishes correspondence from a public office and asks visitors to make contact before any in-person visit.
- Contact values remain on the public page and are not copied into UAI or durable memory.

Evidence: [public Contact Us route](../contact.php#contact-details), [profile boundary](../contact.php#about-michael), and [durable implementation findings](../docs/long-term-memory/reports/publisher-contact-and-public-profile-page-implementation-report.md#findings).

## Interface Routing

- The global footer exposes `Contact Us`.
- The secondary navigation menu exposes the same route without altering the six primary navigation destinations.
- Breadcrumbs, editorial publisher identity, FAQ, answers, search, sitemap, well-known discovery, and the AI citation guide route to `/contact`.
- The shared shell remains unchanged: non-sticky masthead, sole sticky `.menu-strip`, non-sticky orientation rail, linked `/start` hero, institutional `/factions` hero, light-backed internal-page wordmark, and responsive research cards.

## Privacy and Safety Boundary

- Public contact fields are intentionally published at the user’s direction; their presence does not create consent for scraping, profiling, harassment, or unannounced visits.
- Do not copy the page’s contact values into active memory, reports, logs, validation prose, or unrelated structured records.
- Do not add a contact form or remote intake service without explicit privacy, security, retention, abuse, accessibility, legal, and operational review.
- Do not infer employer history, availability, endorsements, identity verification, or project acceptance from the page.

## Validation Routing

Use [focused contact-page evidence](../CONTACT-PAGE-EVIDENCE-IARPG-OPS-2-2.0.31-wip.json), [aggregate validation](../VALIDATION-IARPG-OPS-2-2.0.31-wip.json), and [implementation report](../docs/long-term-memory/reports/publisher-contact-and-public-profile-page-implementation-report.md#validation-performed).

## Related Hot Memory

- [Project context](context.uai#verified-current-facts)
- [Progress](progress.uai#current-state)
- [Decisions](decisions.uai#active-decisions)
- [Architecture](architecture.uai#current-architecture)
- [Operations](operations.uai#current-doctrine)
- [Test plan](test-plan.uai#current-test-plan)
- [Current release](release-IARPG-OPS-2.uai#current-release)