--- id: AREA-WEB title: Websites product_area: websites revision: 1 status: draft product_intent: proposed source_sha: rhythm-v2-docs: 5dc44059e0010a877a57ae22ca80e74183f8d616 services-websites: 5fc6823c69d5e6f208c21dba8c0eb3132f8bdc4c services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1 rhythm-web: 38aef7d26f1ab85b5c2a5be27e4b29df3698f193 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f provenance: inferred source: &ref_0 - 'rhythm-v2-docs:specs/PRODUCT-AREAS.md#MOD-WEB-WEB' - 'rhythm-v2-docs:specs/websites/websites/MODULE.md' - 'rhythm-v2-docs:specs/websites/ACTORS.md' - 'rhythm-v2-docs:specs/websites/RESPONSIBILITIES.md' modules: - MOD-WEB-WEB owns: - 'Customer websites and their addresses, availability and published presentation' - Editorial content and navigation within each site - 'Reusable website designs, recorded design work, previews and publication coordination' - Website release visibility and requests to recover the previous customer application - Visitor routing and member-facing account and record adapters does_not_own: - 'Platform Security owns identity, role assignments, access decisions and portal identity infrastructure' - 'Platform owns licensing, eligibility decisions, workspace lifecycle and the console shell' - CRM owns contact and organization records and their final authorization - 'External release tooling executes application builds, deployments and serving-pointer changes' handoffs: - to: MOD-PFM-SEC what: 'Authenticated authority, portal account infrastructure and consent for staff entry' - to: MOD-PFM-OPS what: Application entitlement and operational licensing state - to: MOD-PFM-ELG what: Audience eligibility decisions - to: MOD-PFM-TNL what: Workspace lifecycle and coordinated export - to: MOD-PFM-CSH what: Hosted administration screens and application navigation - to: MOD-CRM-ENT what: Member and organization record reads and authorized changes - to: External release tooling what: 'Confirmed build, publication and restoration requests and execution outcomes' invariants: - >- The product should preserve customer, workspace and site boundaries across administration and visitor delivery. - 'Identity and grants remain authoritative in Platform, and member records remain authoritative in CRM.' - A connected assistant uses the connecting person’s authority rather than a separate website grant. - Editorial publication and application delivery remain distinct forms of work. invariant_sources: - 'n': 1 provenance: inferred source: 'rhythm-v2-docs:specs/websites/RESPONSIBILITIES.md#modules.guarantees' note: This is a proposed area obligation; the module records boundary defects. - 'n': 2 provenance: documented source: 'rhythm-v2-docs:specs/websites/RESPONSIBILITIES.md#modules.delegates' - 'n': 3 provenance: documented source: 'rhythm-v2-docs:specs/websites/ACTORS.md#ACT-WEB-007' - 'n': 4 provenance: documented source: 'rhythm-v2-docs:specs/websites/RESPONSIBILITIES.md#How the Product Area Is Divided' open_questions: - OQ-WEB-WEB-004 - OQ-WEB-WEB-002 evidence: *ref_0 --- # Websites ## Purpose and Outcomes Websites gives a customer a place to present its organization and offer members a useful online service. Customer staff work in the console, visitors arrive through the customer’s web addresses, and members use the portal when its account functions are available. The area connects these experiences so that the organization can maintain its public presence while keeping responsibility for identity and member records with their owning areas. The intended outcome is a website that staff can understand, maintain and deliver with a clear distinction between editorial work and changes to the application that serves it. Authors need room to prepare material, publishers need visibility into what becomes public, and administrators need a view of delivery and recovery. Rhythm staff support setup and work that requires wider authority. A connected assistant participates through the authority of the person who connects it. The area also brings member-facing account and record adapters into the website experience. Those adapters connect members to Platform and CRM responsibilities rather than create a second authority for accounts or association records. The overview describes the area’s intended boundary; the module records the readiness, evidence and unresolved gaps of each part. ## Scope and Boundaries Websites owns the customer’s website experience, its editorial material and the coordination of design work and delivery. Its module spans authoritative records stored in Platform, content and change records stored in Websites, the customer application runtime and administration screens hosted by the console. Repository placement does not divide that product responsibility. Platform supplies identity, grants, licensing, eligibility decisions, workspace lifecycle and console framing. CRM supplies the member and organization records used by portal adapters and retains the final decision over record changes. Website delivery passes confirmed work to external release tooling, which executes builds and deployments and updates what the customer application serves. ## How the Area Is Divided The Websites, Content and Portal Runtime module is the area’s single reading home. Open it to understand how administration, editorial work, reusable designs, application delivery and visitor or member experiences fit together. Its planning layer explains the product concepts and outcomes; its design layer assigns records, service boundaries, workflows and screen responsibilities. ## Area-Level Invariants The product should preserve customer, workspace and site boundaries wherever a person or system enters the website experience. Identity and grants remain Platform responsibilities, while CRM retains member-record authority. A connected assistant acts with the connecting person’s authority. Editorial publication and application delivery remain distinct forms of work, even when both affect the same site. These area principles do not establish that every implementation path satisfies them. ## Open Ownership Questions Site creation from a reusable design crosses Platform’s site registry and Websites’ design and content responsibilities. Product still needs to decide which service coordinates that work. The current template tools also need a decision about their place in Websites while the proposed Configuration boundary awaits approval. Ownership of application onboarding and release execution outside the examined sources remains unresolved in the module’s findings.