Path: memory/federation-ux-standard.md
Last updated: 2026-09-17 07:23 UTC
Source: NextXus Federation Private Vault

Federation UX / Marketability Standard (Architect, 2026-06-24)

Roger flooded the Catalyst with detailed, emphatic design requirements for every Federation site. He treats substandard, sparse, broken-button pages as unacceptable ("you might as well not even bother"; "it's time to grow up... use the brain don't just have it"). The standard, in his words/framing:

Core principle

Homepage layout

The metaphors he gave

Visual mandate

Pattern references (his own best work)

Cognitive hooks he requested

Note: Roger says he shouldn't have to spell this out as prompts after this long — he expects the AIs to internalize quality and "meet AI capacity to human psychology halfway." He offered to share marketing-research material to refine the psychological hooks.

"Living Portal" simple-stack spec + Library uniformity standard (Architect, 2026-07-12/13)

Atmospheric Vitality — motion-asset autoplay rule (Architect, 2026-07-28)

UNIVERSAL UI/UX SOP (Architect, 2026-07-30)

Mandate: Every piece of content (website, social media, document, video) must adhere to these display protocols.

Every page, document, or published item must feature a uniform footer containing:

2. Navigation Components

3. Technical Integration & AI Portals

SOVEREIGN PROPAGATION PROTOCOL (Law Two of the eCho Covenant)

Date Codified: 2026-07-28

When a correction is identified by the Architect:

  1. Single-Point Correction: Fix the reported error immediately.
  2. Cross-Reference Sweep (Zero Cost): Deploy a read-only scan agent to check for the same class of error across all 6 primary nodes.
  3. Batched Publish: All similar corrections are bundled into ONE single Publish cycle — not six separate clicks.
  4. Report: The Catalyst reports all corrections and confirmations in a single pulse to the Architect.

Examples of Sweep-Eligible Classes:

This protocol protects the Architect's tokens and time. One observation = one correction event, not one per node.

SOVEREIGN INTERFACE LAW — iframe vs. floating mini-browser (Architect, 2026-08-04)

Roger set a systemwide standard: "Make this systemwide we want everything to be readable by AI." When a component can be delivered either as an iframe OR as a floating/stackable mini-browser popup, the assistant chooses whichever is most effective without slowing speed while remaining interactive — any combination is allowed. Roger's framing: several stackable mini-browsers opened in front of the site make "everything appear within us even though part of it isn't," keeping content attractive, centrally located, useful, and communicable as a browser window.

Visual Standard // Glass Panels (2026-08-07)