# Publisher Contact and Public Profile Page Implementation Report

## Status

Current implementation report for IARPG-OPS-2 2.0.31-wip. The release remains work in progress.

## Purpose

Document the addition of a direct Contact Us route and a bounded public profile for the individual publisher of iarpg.com. The page is intended to make publisher identity, contact pathways, general professional focus, and first-party profile routes easy to find without reproducing employer history or turning private project details into public claims.

## Findings

1. The global footer now contains an explicit `Contact Us` link and the secondary navigation menu exposes the same route without changing the six-item primary navigation.
2. `/contact` is a dedicated ProfilePage with a named maintainer, direct user-authorized contact fields, a general professional biography, public profile links, and a clear source and privacy boundary.
3. The public biography is limited to general, first-party professional themes: enterprise software architecture, legacy modernization, Microsoft and data systems, typed web applications, automated testing, human-reviewed AI-assisted engineering, evidence-backed documentation, discoverability, mentoring, and visual creativity.
4. Employer names, client names, job-by-job chronology, private implementation details, and unsupported certifications or metrics are intentionally excluded.
5. The page uses semantic contact links, an address element, responsive cards, visible focus, reduced-motion, forced-colors, and print behavior. It introduces no form, account, analytics, remote database, upload service, or server-side message retention.
6. The mailing-address notice distinguishes correspondence from a public office or drop-in location and asks visitors to make contact before any in-person visit.
7. The route is integrated into breadcrumbs, editorial publisher identity, FAQ and answer discovery, local search, sitemap, well-known discovery, AI citation guidance, and structured data.
8. Contact values are deliberately not copied into active UAI memory or durable reports. Those records route to the public page and describe only the implementation and privacy boundary.

## Implementation

The page is implemented in `contact.php` and uses the shared layout, hero, answer-brief, footer, security-header, and structured-data contracts. The page publishes a `ProfilePage` with a nested `Person` record, first-party public profile routes, general areas of expertise, and user-authorized contact fields. The surrounding site uses the canonical clean route `/contact`.

The CSS in `assets/css/site.css` adds reusable contact cards, a two-column profile layout, a professional-focus grid, and a public-profile link collection. The component collapses to one column on narrow screens and uses existing design tokens rather than introducing a page-specific theme or a new sticky surface.

## Source and Privacy Boundary

General profile language was reviewed against the publisher’s first-party professional website. The user directly supplied the public full-name spelling and the mailing-address field for this page. The public website supplied the general professional and creative themes and the direct contact channels used for cross-checking.

The page does not imply that the mailing address is a staffed office, that unsolicited visits are welcome, that a response is guaranteed, or that a visitor should send confidential information. It provides no contact form and therefore does not create a new IARPG data-collection or retention system.

## Validation Performed

Focused validation checks the existence and footer visibility of `/contact`, exact user-authorized public fields, semantic `mailto:` and `tel:` actions, ProfilePage and Person structured data, source and employer-exclusion statements, private-residence notice, absence of a form or remote submission endpoint, responsive CSS, reduced-motion, forced-colors, print handling, clean-route behavior, and preservation of the sole sticky `.menu-strip` contract.

Broader release validation also checks PHP syntax, static resources, schemas, memory links, UAI mirrors, search, answers, sitemap, staging routes, accessibility structure, delivery budgets, deterministic finalization, and flat-package equality. Those checks prove only their recorded technical conditions, not human preference, response availability, privacy-law compliance, or the accuracy of third-party profile services.

## Decisions or Recommendations

- Keep `Contact Us` in the global footer even if additional publisher links are added elsewhere.
- Keep employer chronology on the publisher’s primary professional site rather than duplicating it into iarpg.com.
- Keep contact fields out of UAI and durable memory; route memory to `/contact` and this report instead.
- Do not add a server-side contact form without a separate privacy, security, retention, abuse, accessibility, and operational review.
- Treat public profile service links as first-party routing aids, not endorsements by the linked platforms.
- Reconfirm direct contact values with the publisher before any future stable promotion or material profile redesign.

## Risks and Limitations

- Publishing a residential mailing address creates real privacy and unwanted-visit risk even when the publisher has explicitly requested publication.
- The primary professional website can change after the recorded review date.
- Automated checks do not establish that every visitor understands the private-residence warning or uses the contact channels appropriately.
- Structured data can be crawled or republished by third parties outside the control of iarpg.com.
- The absence of a contact form avoids new server-side retention but does not control data retained by a visitor’s email, telephone, browser, or telecommunications provider.

## Related Durable Documents

- [Site Identity and Onboarding Clarity Report](site-identity-and-onboarding-clarity-report.md#findings)
- [UI, UX, SEO, AEO, and GEO Improvement Report](ui-ux-seo-aeo-geo-improvement-report.md#findings)
- [Production Edge Security and Accessibility Validation Report](production-edge-security-and-accessibility-validation-report.md#findings)

## Memory References

- [Publisher contact and profile hot memory](../../../.uai/publisher-contact.uai#current-publication-contract)
- [Hot-memory index](../../../.uai/index.uai#current-topic-routing)
- [Current context](../../../.uai/context.uai#verified-current-facts)
- [Current progress](../../../.uai/progress.uai#current-state)
- [Active decisions](../../../.uai/decisions.uai#active-decisions)
- [Current architecture](../../../.uai/architecture.uai#current-architecture)
- [Operations](../../../.uai/operations.uai#current-doctrine)
- [Current test plan](../../../.uai/test-plan.uai#current-test-plan)
- [Durable pointer ledger](../../../.uai/long-term-memory.uai#publisher-contact-and-public-profile)

## Related Public Routes

- [Contact Us](/contact)
- [Editorial and Evidence Policy](/editorial#publisher-contact)
- [Answer Center](/faq#faq-who-maintains-iarpg-com-and-how-can-i-contact-him)
- [AI discovery guide](/llms.txt)

## Supersession Status

Current beginning with 2.0.31-wip. A later profile or contact implementation may supersede the interface details only if it preserves a direct public route, explicit privacy and data-handling boundaries, user-authorized fields, footer discoverability, and the rule against copying contact details into UAI or durable memory.