System Requirements Document for digital-marketing

1. Introduction

This document specifies the requirements for digital-marketing, a public website that presents a digital marketing agency's services to prospective clients and gives the agency a private workspace to review incoming inquiries and keep the published service and proof content current.

The product intent is derived from the authoritative requirement thread: "Create a website for digital marketing services." The website's purpose is to present digital marketing services to prospective clients, to let interested visitors make contact and request a consultation, and to give the agency-side owner of the site a way to review those inquiries and maintain the content that converts visitors into qualified leads.

The audience is twofold:

• Prospective Client — a business decision-maker evaluating digital marketing services who needs to understand the agency's offerings, credibility, and results, then make contact to request a proposal or consultation.
• Agency Marketing Lead — the agency-side owner of the public site who presents service offerings, case results, and positioning so prospective clients can evaluate the agency, keeps service and proof content current, and reviews incoming inquiries.

The site itself is treated as the agency's best case study: the visual confidence of the public surface is part of the product being sold.

2. System Overview

The system is a first-party web application with two delivery surfaces:

1. A public, anonymously reachable surface — a Landing page that explains the agency's digital marketing services, and a Contact page where interested visitors submit an inquiry or consultation request.
2. A protected agency workspace — a Login page for returning verification of the agency-side owner, a Leads workspace for reviewing incoming inquiries from prospective clients, and a Content workspace for maintaining the service and proof content presented on the website.

The application owns its identity: the Agency Marketing Lead is established through invitation or provisioning and verified on return so that inquiry review and content maintenance can be resumed. Protected state (Leads, Content) is unavailable until that identity is established. The public Landing and Contact surfaces require no identity.

Backend integration is required to persist inquiries submitted from Contact, to make them reviewable in Leads, and to persist and publish the service and proof content maintained in Content.

2a. Product Interpretation and Delivery Boundary

Current delivery. The current product is the website for digital marketing services described above: a public presentation of services with a contact path, plus a private agency workspace for inquiry review and content maintenance. All five destinations — Landing, Contact, Login, Leads, Content — are current.

Access ownership. Landing and Contact are public and anonymously reachable. Login is the anonymous entry boundary where the Agency Marketing Lead establishes or verifies identity; it does not itself require prior identity. Leads and Content are protected and role-restricted to the Agency Marketing Lead. Identity is application-owned and is established by invitation or provisioning, then verified on return. No differentiated permission tiers beyond the agency-side owner are established by the source.

Provider and external ownership. No provider-owned or external-only surface is specified. All accepted behavior is first-party.

Future boundary. No future-horizon requirements are stated in the authoritative thread. Nothing in this document authorizes adjacent capabilities such as campaign execution, analytics dashboards, billing, client portals, or multi-role permission management.

2b. Source Content Inventory

No reference directive in this request declares content_source authority, so no source content inventory is included.

2c. Page Content and Component Coverage

Landing

• Information and state: The agency's identity and positioning; the digital marketing services offered; proof of results; credibility signals; the primary path to make contact. Anonymous, no identity required.
• Primary actions: Navigate to Contact to request a consultation or proposal; move into the services and proof content.
• Supporting actions: Read service descriptions; read result and proof content; reach the Contact destination from any point on the page.
• Domain entities: Service offering, proof/result item, agency positioning content.
• Component responsibilities:
  • Hero: headline, primary call to action into Contact, art-directed prop imagery.
  • Services presentation: the agency's digital marketing services, each with its name and description.
  • Proof/results presentation: case results and credibility content.
  • Continuous results ticker: client names and result statistics.
  • Contact entry control: routes the visitor to Contact.
• States:
  • Loading: content placeholders while service and proof content is fetched.
  • Empty: if no service or proof content is currently published, the page still presents the agency's positioning and the path to Contact.
  • Success: services and proof content render; the visitor can reach Contact.
  • Error: if content cannot be loaded, the page presents the agency's positioning and the Contact path rather than failing silently.
  • Recovery: content is retried; the Contact path remains available throughout.

Contact

• Information and state: The inquiry and consultation-request form; the agency's contact context. Anonymous, no identity required.
• Primary actions: Submit an inquiry or consultation request.
• Supporting actions: Review entered details before submitting; return to Landing.
• Domain entities: Inquiry (prospective client's submitted request), including the visitor's identifying and contact details and the substance of the request.
• Component responsibilities:
  • Inquiry form: captures the visitor's details and request.
  • Validation feedback: identifies missing or malformed entries before submission.
  • Submission control: commits the inquiry.
  • Confirmation state: confirms receipt to the visitor.
• States:
  • Loading: submission in progress, with the control reflecting the pending state.
  • Empty: the form is presented with no entries.
  • Success: the inquiry is accepted and the visitor sees confirmation that it was received.
  • Error: validation failure identifies the specific fields to correct; submission failure preserves the visitor's entries and offers retry.
  • Recovery: the visitor can correct and resubmit without re-entering everything; a failed submission never silently discards the inquiry.

Login

• Information and state: The identity entry boundary for the agency-side owner. Anonymous entry; establishes or verifies the Agency Marketing Lead's identity.
• Primary actions: Establish identity from an invitation or provisioning, or verify identity on return.
• Supporting actions: Recover from an invalid or expired entry; return to the public site.
• Domain entities: Agency Marketing Lead identity, invitation/provisioning credential, verification credential.
• Component responsibilities:
  • Identity entry: accepts the credential supplied by invitation/provisioning or the returning credential.
  • Verification control: submits the credential for verification.
  • Error feedback: states clearly when a credential is invalid or expired.
• States:
  • Loading: verification in progress.
  • Empty: the identity entry is presented with no entries.
  • Success: identity is established and the Agency Marketing Lead continues to the protected workspace.
  • Error: an invalid or expired credential is reported without revealing protected state.
  • Recovery: the Agency Marketing Lead can retry entry; an expired invitation or provisioning credential is reported as such rather than as a generic failure.

Leads

• Information and state: The list of incoming inquiries submitted by prospective clients, with each inquiry's details and its current review state. Protected; role-restricted to the Agency Marketing Lead.
• Primary actions: Review an incoming inquiry and its details.
• Supporting actions: Move through the inquiry list; return to an inquiry after leaving.
• Domain entities: Inquiry (as submitted from Contact), inquiry review state.
• Component responsibilities:
  • Inquiry list: presents incoming inquiries with enough detail to identify and prioritize them.
  • Inquiry detail: presents the full submitted content of a selected inquiry.
  • Review-state control: records the Agency Marketing Lead's review of an inquiry.
• States:
  • Loading: the inquiry list is being fetched.
  • Empty: no inquiries have been submitted yet; the workspace states this plainly rather than appearing broken.
  • Success: inquiries are listed and their details are readable.
  • Error: if inquiries cannot be loaded, the failure is stated and retry is offered.
  • Recovery: retry restores the list; a review action that fails does not lose the inquiry.

Content

• Information and state: The service and proof content presented on the public website, in its current published form. Protected; role-restricted to the Agency Marketing Lead.
• Primary actions: Maintain the service and proof content presented on the website.
• Supporting actions: Review current content before changing it; return to content maintenance after leaving.
• Domain entities: Service offering content, proof/result content, publication state.
• Component responsibilities:
  • Content list: presents the service and proof items currently maintained.
  • Content editor: accepts changes to an item's content.
  • Publication control: commits maintained content to what the public website presents.
• States:
  • Loading: current content is being fetched.
  • Empty: no content items exist yet; the workspace states this and allows the first item to be created.
  • Success: changes are saved and reflected in what the public website presents.
  • Error: a failed save is reported and the Agency Marketing Lead's edits are preserved for retry.
  • Recovery: retry re-commits the change; the previously published content remains presented until a change succeeds.

3. Functional Requirements

Each requirement is a distinct story point with provenance, lifecycle facts, and observable acceptance.

FR-1 — Public presentation of digital marketing services (explicit) As a Prospective Client, I should be able to view a website that presents the agency's digital marketing services, so that I can understand what the agency offers.

• Trigger/input: The visitor opens the public site.
• Observable result: The Landing page presents the agency's digital marketing services.
• Access state: Anonymous; no identity required.
• Failure/recovery: If service content cannot be loaded, the page still presents the agency's positioning and the path to contact.
• Continuation: The visitor moves into the services and proof content, or proceeds to Contact.

FR-2 — Evaluation of credibility and results (explicit) As a Prospective Client, I should be able to review the agency's proof and results content, so that I can judge whether the agency is credible and effective.

• Trigger/input: The visitor reads the proof/results presentation on Landing.
• Observable result: Case results and credibility content are presented alongside the services.
• Access state: Anonymous.
• Failure/recovery: If proof content is unavailable, the services and contact path remain intact.
• Continuation: The visitor decides whether to make contact.

FR-3 — Initiating an inquiry or consultation request (explicit) As a Prospective Client, I should be able to submit an inquiry or consultation request, so that I can start a conversation with the agency about a proposal.

• Trigger/input: The visitor opens Contact and submits the inquiry form.
• Observable result: The inquiry is accepted and the visitor sees confirmation that it was received.
• Access state: Anonymous; no identity required.
• Failure/recovery: Validation failure identifies the fields to correct; submission failure preserves the visitor's entries and offers retry.
• Continuation: The Agency Marketing Lead can review the inquiry in Leads.

FR-4 — Agency-side identity establishment (required_inference) As an Agency Marketing Lead, I should be able to establish my identity from an invitation or provisioning, so that I can reach the protected workspace that holds inquiry review and content maintenance.

• Trigger/input: The Agency Marketing Lead opens Login with an invitation or provisioning credential.
• Observable result: Identity is established and the protected workspace becomes reachable.
• Access state: Login is anonymously reachable; protected state remains unavailable until identity is established.
• Failure/recovery: An invalid or expired credential is reported without revealing protected state; the Agency Marketing Lead can retry.
• Continuation: The Agency Marketing Lead proceeds to Leads or Content.

FR-5 — Agency-side returning verification (required_inference) As an Agency Marketing Lead, I should be able to verify my identity on return, so that I can resume inquiry review and content maintenance.

• Trigger/input: The returning Agency Marketing Lead opens Login and submits the returning credential.
• Observable result: Identity is verified and the previously held workspace state is reachable again.
• Access state: Anonymous entry; protected destinations remain unavailable until verification succeeds.
• Failure/recovery: An invalid credential is reported and entry can be retried.
• Continuation: The Agency Marketing Lead resumes Leads or Content.

FR-6 — Reviewing incoming inquiries (required_inference) As an Agency Marketing Lead, I should be able to review incoming inquiries from prospective clients, so that I can respond to qualified leads.

• Trigger/input: The Agency Marketing Lead opens Leads.
• Observable result: Incoming inquiries are listed with their details and review state.
• Access state: Protected; role-restricted to the Agency Marketing Lead.
• Failure/recovery: If inquiries cannot be loaded, the failure is stated and retry is offered; a failed review action does not lose the inquiry.
• Continuation: The Agency Marketing Lead records the review and moves to the next inquiry.

FR-7 — Maintaining service and proof content (required_inference) As an Agency Marketing Lead, I should be able to maintain the service and proof content presented on the website, so that what prospective clients evaluate stays current.

• Trigger/input: The Agency Marketing Lead opens Content and edits an item.
• Observable result: The change is saved and reflected in what the public website presents.
• Access state: Protected; role-restricted to the Agency Marketing Lead.
• Failure/recovery: A failed save is reported and the edits are preserved for retry; previously published content remains presented until a change succeeds.
• Continuation: The Agency Marketing Lead continues maintaining other items or returns to Leads.

FR-8 — Conversion of visitors into qualified leads (required_inference) As an Agency Marketing Lead, I should be able to present service offerings, case results, and positioning so that prospective clients can evaluate the agency, so that the site converts visitors into qualified leads.

• Trigger/input: The Agency Marketing Lead maintains the public content in Content.
• Observable result: The public site presents current offerings, results, and positioning, and inquiries arrive in Leads.
• Access state: Content maintenance is protected; the resulting public presentation is anonymous.
• Failure/recovery: If maintained content fails to publish, the previously published content remains presented.
• Continuation: Inquiries submitted by prospective clients appear in Leads for review.

4. User Personas

Prospective Client

• Product context: A business decision-maker evaluating digital marketing services. They arrive at the public site without an account and without prior relationship to the agency, typically while comparing several agencies.
• Primary goal: Understand the agency's offerings, credibility, and results, then make contact to request a proposal or consultation.
• Distinct accepted responsibilities: Comparing service options and initiating an inquiry. Their recurring responsibility is the evaluation-and-inquiry cycle: read what the agency offers, judge whether the agency is credible and effective, and decide whether to start a conversation.
• Relevant inputs or decisions: Which services matter to them; whether the proof and results content is convincing; whether to submit an inquiry or consultation request.
• Interactions with other accepted participants: Their submitted inquiry becomes the object the Agency Marketing Lead reviews in Leads. The Prospective Client does not interact with the agency workspace and never sees protected state.
• Observable success: An inquiry or consultation request is submitted and confirmed as received.
• What makes this role different: This persona is entirely anonymous and read-and-submit oriented. They never hold durable private state, never return to a workspace, and their only committed action is a single inquiry submission. Their success is measured by whether they choose to make contact at all.

Agency Marketing Lead

• Product context: The agency-side owner of the public site. They are accountable both for what the site says and for what happens to the inquiries it produces.
• Primary goal: A site that converts visitors into qualified leads.
• Distinct accepted responsibilities: Keeping service and proof content current, and reviewing incoming inquiries. These are two distinct recurring responsibilities with different working contexts: content maintenance changes what the public sees, while inquiry review acts on what the public sent.
• Relevant inputs or decisions: Which services and results to present and how to position them; which incoming inquiries to review and how to record that review.
• Interactions with other accepted participants: They are the recipient of the Prospective Client's inquiry and the author of the content the Prospective Client evaluates. They are the only participant who reaches protected state.
• Observable success: The public site presents current offerings, results, and positioning, and incoming inquiries are reviewed.
• What makes this role different: This persona holds durable, private, resumable state. Their work is maintenance and response rather than evaluation, it persists across sessions, and it is the only work in the product that requires identity. Their two responsibilities are separated by working context — one edits what the site presents, the other acts on what the site receives.

5. Core User Flows

Flow A — Prospective Client evaluates the agency and submits an inquiry

1. The Prospective Client opens the public site and lands on Landing (anonymous; no identity required).
2. They read the agency's positioning and the presented digital marketing services.
3. They review the proof and results content to judge the agency's credibility and effectiveness.
4. They decide the agency is worth contacting and use the contact entry control to move to Contact.
5. On Contact, they complete the inquiry form with their details and the substance of their request.
6. They submit the inquiry.
7. Observable result: The inquiry is accepted and the Prospective Client sees confirmation that it was received.
8. Failure/recovery: If validation fails, the specific fields to correct are identified and their entries are preserved. If submission fails, their entries are preserved and they can retry without re-entering everything.
9. Next step: The inquiry becomes available to the Agency Marketing Lead in Leads. The Prospective Client's journey ends here; they hold no account and no workspace state.

Flow B — Agency Marketing Lead establishes identity and reviews incoming inquiries

1. The Agency Marketing Lead receives an invitation or provisioning for the agency workspace.
2. They open Login (anonymously reachable) and enter the credential from that invitation or provisioning.
3. Observable result: Identity is established and the protected workspace becomes reachable.
4. Failure/recovery: If the credential is invalid or expired, this is reported without revealing protected state, and they can retry.
5. They open Leads (protected; role-restricted to the Agency Marketing Lead).
6. They review the list of incoming inquiries submitted by prospective clients, including the inquiries produced by Flow A.
7. They open an individual inquiry and read its full submitted content.
8. They record their review of that inquiry.
9. Observable result: The inquiry's review state reflects their review.
10. Failure/recovery: If the inquiry list cannot be loaded, the failure is stated and retry is offered. If a review action fails, the inquiry is not lost.
11. Next step: They move to the next inquiry, or continue to content maintenance in Flow C.

Flow C — Agency Marketing Lead maintains service and proof content

1. The returning Agency Marketing Lead opens Login and verifies their identity.
2. Observable result: Identity is verified and their previously held workspace state is reachable again.
3. Failure/recovery: If verification fails, the failure is reported and entry can be retried.
4. They open Content (protected; role-restricted to the Agency Marketing Lead).
5. They review the service and proof items currently presented on the public website.
6. They edit an item's content.
7. They commit the change through the publication control.
8. Observable result: The change is saved and reflected in what the public website presents.
9. Failure/recovery: If the save fails, the failure is reported and their edits are preserved for retry. The previously published content remains presented until a change succeeds.
10. Next step: They continue maintaining other items, or return to Leads. The updated content is what the next Prospective Client evaluates in Flow A.

Flow D — Agency Marketing Lead converts visitors into qualified leads

1. The Agency Marketing Lead maintains the public site's service offerings, case results, and positioning through Content (Flow C).
2. Observable result: The public site presents current offerings, results, and positioning to anonymous visitors on Landing.
3. Prospective clients evaluate that presentation and submit inquiries through Contact (Flow A).
4. Observable result: Those inquiries arrive in Leads for review.
5. The Agency Marketing Lead reviews them (Flow B).
6. Failure/recovery: If maintained content fails to publish, the previously published content remains presented, so the public path to Contact is never broken.
7. Next step: The cycle continues — reviewed inquiries inform what content is maintained next.

6. Visuals Colors and Theme

The creative direction is authoritative for this section. Muse: Jessica Walsh. Headline idea: the site itself is the agency's best case study — colour-saturated confidence, art-directed like a campaign.

Colour tokens (light mode):

Proportion roughly 55% peach, 25% pink, 10% lime, 10% white/ink. Lime never carries small text on peach — pair lime only with ink type.

Typography:

• Headings: Archivo Black, uppercase or sentence case, tight leading 0.92, tracking -0.02em, deliberately oversized and allowed to wrap to 2–3 lines. Occasional single words flipped to italic or rotated 2–3° as a sticker gesture. No thin weights anywhere.
• Body: Manrope.
• Scale (1.5 modular): display clamp(48px, 11vw, 168px) / h2 clamp(32px, 5vw, 72px) / h3 28px / body 18px / label 13px uppercase tracked +0.12em. Mobile display bottoms out at 48px so "MARKETING" still fits at 375px.

Shape language: Big radii (24–40px) on cards and image frames; fully pill buttons; sticker shapes with hard offset shadows (6px 6px 0 ink); circular badges; colour-block section edges cut on a diagonal rather than a soft curve. No glassmorphism, no gradient blobs.

Layout: Colour-blocked full-bleed sections stacked like campaign posters — peach hero, full-pink services band, lime ticker strip, white case-study cards on peach, ink footer. Asymmetric two-column editorial grids with type breaking the column boundary; oversized numerals (01–04) pinned to the left edge of each service row. Navigation is a thin ink top bar with the wordmark in a pink pill, plus a sticky lime "Book a call" pill bottom-right on mobile.

Imagery: Art-directed surreal props photographed on flat colour grounds — an oversized chrome "thumb" sculpture, a giant pink megaphone, a hand holding a lime arrow, a stack of eyeballs as a metaphor for attention — plus high-contrast duotone portraits of the team in pink/ink. Vector sticker icons: stars, arrows, "SOLD OUT"-style bursts repurposed as "CASE STUDY". No stock office photography, no abstract gradient art.

Readable-text integrity: Headlines, wordmarks, labels, numbers, card text and controls stay entirely inside the viewport and their container at 375px, 768px and 1280px, wrapping or scaling to fit, with no other element covering them. Imagery, decoration and motion may be cropped, bled, rotated, overlapped or cut as the direction asks, provided they cover no readable text or control. Moving and scrollable content may cross the viewport edge by design and is judged by whether it moves and whether every item becomes fully readable as it passes.

7. Signature Design Concept

The hero as a campaign poster that breaks its own grid.

The public entry (Landing) is a peach full-bleed hero. The headline "WE MAKE BRANDS IMPOSSIBLE TO IGNORE" is set in Archivo Black at clamp(48px, 11vw, 168px), left-aligned, occupying the left 7 of 12 columns and deliberately running past the grid into the right column. Behind its last line sits a solid hot-pink rectangle block that the type knocks out of. Bottom-right of the hero, a lime pill CTA "Book a strategy call" sits directly on the pink block edge, and a circular pink badge reading "RESULTS IN 90 DAYS" overlaps the headline's baseline at the right. A single art-directed prop image — a giant pink megaphone — is cropped hard by the right viewport edge. There is no centred stack and no subtext paragraph under the headline; the proof numbers sit in a lime ticker strip immediately below the fold line.

This concept recomposes only accepted content and controls: the headline states the agency's positioning, the CTA routes to the accepted Contact destination, the badge and ticker present accepted proof and result content, and the prop image is decoration. It introduces no new behaviour, page, or destination.

8. Interaction Model & Motion Direction

Interaction Model: Animated Motion Tempo: expressive Hero Dimensionality: layered_2d

Landing Hero Motion Brief

• Focal subject: The oversized Archivo Black headline "WE MAKE BRANDS IMPOSSIBLE TO IGNORE" knocking out of a solid hot-pink block, with the giant pink megaphone prop cropped by the right viewport edge.
• Input → transformation → outcome thesis: As the visitor arrives, the headline reveals word by word; the pink block and the lime CTA settle into place on the block edge; the circular "RESULTS IN 90 DAYS" badge springs in over the headline baseline. The outcome is a composed campaign poster in which the agency's positioning, its proof, and the path to Contact are all legible in the first frame.
• Motion vocabulary: Staggered word-by-word reveal on the hero headline (60ms stagger, 400ms ease-out); colour-flip on hover where a card's peach ground swaps to pink and text to white; an infinite lime ticker of client names and result stats that scrolls continuously; bouncy scale-ins (spring, 1.04 max) on sticker badges. No parallax, no 3D.
• Composed first frame: Peach ground; headline left-aligned and breaking into the right column; hot-pink block behind the last line; lime pill CTA on the pink block edge; circular pink badge overlapping the baseline; megaphone prop cropped by the right edge; lime ticker strip at the fold line.
• Reduced-motion state: The headline appears fully composed with no stagger; the lime ticker stops and wraps into static rows so every client name and result stat is whole and readable; sticker badges appear at rest without spring scale-ins; hover colour-flips resolve instantly.

9. Non-Functional Requirements

• NFR-1 — Public reachability (explicit): Landing and Contact must be reachable without identity, since the website's purpose is to present services to prospective clients and accept their inquiries.
• NFR-2 — Protected workspace isolation (required_inference): Leads and Content must not expose inquiry or content state to anyone who has not established the Agency Marketing Lead identity. Login must not reveal protected state on a failed attempt.
• NFR-3 — Inquiry durability (required_inference): A submitted inquiry must not be lost by a failed submission, a failed review action, or a failed load. Visitor entries must survive validation and submission failures.
• NFR-4 — Published-content continuity (required_inference): A failed content save must not remove or corrupt the currently published content; the public site must continue to present the last successfully published content.
• NFR-5 — Readable-text integrity across viewports (explicit, from creative direction): Headlines, wordmarks, labels, numbers, card text and controls must remain whole and uncovered at 375px, 768px and 1280px.
• NFR-6 — Reduced-motion compliance (explicit, from creative direction): Under prefers-reduced-motion, the continuous ticker must stop and present whole items as wrapped rows or a horizontally scrollable row, and other motion must resolve to a static composed state.
• NFR-7 — Backend persistence (required_inference): Inquiries submitted from Contact must persist so they are reviewable in Leads, and content maintained in Content must persist so it is presentable on Landing.

10. Tech Stack

• Frontend: React — a first-party custom UI is required for the public site and the protected workspace.
• Backend: Python / FastAPI — backend integration is required to persist inquiries and maintained content.
• Storage: A persistent datastore appropriate to inquiry records and maintained content items.
• Containerization: Docker / docker-compose for local and deployment packaging.
• Kubernetes: Not required by any stated constraint; omit unless deployment demands it.

No source-specified technology choices were provided beyond the requirement to build a website; the above are the minimal stack consistent with the accepted behavior and the required backend integration.

11. Assumptions and Constraints

• A-1 (assumption): The agency's specific service offerings, proof items, and positioning copy are supplied as content through the Content workspace rather than fixed in this document.
• A-2 (assumption): The Agency Marketing Lead identity is established by invitation or provisioning rather than open self-registration, since the source establishes a single agency-side owner of protected work.
• A-3 (assumption): No differentiated permission tiers exist beyond the agency-side owner; Leads and Content are role-restricted to the Agency Marketing Lead.
• A-4 (constraint): Landing and Contact require no identity; Leads and Content require established Agency Marketing Lead identity.
• A-5 (constraint): The creative direction is authoritative for palette, typography, shape, layout, imagery, and motion. The generic indigo/blue-on-white SaaS template is forbidden.
• A-6 (constraint): No future-horizon requirements are stated; nothing in this document authorizes campaign execution, analytics dashboards, billing, client portals, or multi-role permission management.
• A-7 (constraint): Readable text and controls take precedence over cropping, clipping, covering, or running off an edge; such gestures are carried by imagery and decoration instead.

12. Glossary

• Agency Marketing Lead — The agency-side owner of the public site; the only participant who reaches protected state, responsible for content maintenance and inquiry review.
• Content — The protected workspace where service and proof content presented on the public website is maintained.
• Contact — The public destination where a prospective client submits an inquiry or consultation request.
• Inquiry — A request submitted by a prospective client through Contact, reviewable by the Agency Marketing Lead in Leads.
• Landing — The public entry surface presenting the agency's digital marketing services, proof, and results.
• Leads — The protected workspace where incoming inquiries from prospective clients are reviewed.
• Login — The anonymously reachable identity boundary where the Agency Marketing Lead establishes identity from an invitation or provisioning, or verifies identity on return.
• Prospective Client — A business decision-maker evaluating digital marketing services who may submit an inquiry or consultation request.
• Proof content — Case results and credibility material presented on the public site so prospective clients can evaluate the agency.
• Publication control — The control in Content that commits maintained content to what the public website presents.