QnA Init Docs — UC 1.7 (Trading SEO Pages)

Related WBS: UC_1.7.1 (Futures Trading, Custom Visual), UC_1.7.2 (Forex Trading, Sanity Template), UC_1.7.3 (Crypto Trading, Sanity Template), UC_1.7.4 (News & Events, Sanity Template), UC_1.7.5 (Scalping, Sanity Template), UC_1.7.6 (Swing Trading, Sanity Template) Category: MARKETING WEBSITE → Module: Trading SEO Pages Source pre-flight completed:

• CR: References/CR/_CR_INDEX.md — checked all 4 active CRs (TradeSea/NinjaTrader, Nuvei/EBANX, Everflow/Impact.com, Freshdesk/Zendesk). None affect Marketing Website / Trading SEO Pages.
• QnA confirmed: References/QnA from clients/01_MARKETING_WEBSITE/QnA_MARKETING_WEBSITE.md — empty, no answered/open items yet for this category.
• Customer supplies:
  • dashboard_v7_full.txt line 96-104 (Global Header "TRADING" dropdown: Markets = Futures/Forex/Crypto; Strategies = News & Events/Scalping/Swing Trading) and line 125-126 (Template System #05 — "Market Vertical — SEO. One flexible layout used 6 times (Futures, Forex, Crypto, News, Scalping, Swing).").
  • StackTrading_Technical_Proposal_v2.4.docx.md line 59 and 97 ("1 SEO Market Vertical page — Futures — with custom visual"; "Futures SEO Market Vertical page | Part of optional 5-page bundle $4,500 | 1 page approved — USD 900 confirmed") and line 228 ("Remaining SEO Market Vertical pages (Crypto, News, Scalping, Swing) and Comparison Matrix battle cards use the flexible Sanity.io CMS templates already included in the base scope"). Note: this sentence does not explicitly name Forex, but Forex is grouped with the other 5 under Template #05 in dashboard_v7_full.txt, and WBS UC_1.7.2 explicitly labels it "(Sanity Template)" — treated as part of the shared-template group, consistent across both sources.
  • StackTrading_Technical_Proposal_v2.4.docx.md line 117 (Sanity.io collections named: Blog, Video Library, FAQs, Team, Comparison entries, Insights articles — no explicit "Market Vertical"/SEO page collection named).
• WBS: row 17 (Futures Trading, UC_1.7.1), row 18 (Forex Trading, UC_1.7.2), row 19 (SEO Landing Page Template — Crypto/News/Scalping/Swing, UC_1.7.3 — per user-confirmed decision this single WBS row is documented as 4 separate UCs UC_1.7.3/UC_1.7.4/UC_1.7.5/UC_1.7.6 to preserve the existing per-vertical SRS structure). Status design = "Done" for rows 17-19, Status document = "Todo".
• Wireframe: References/Wireframe/Marketing website/Trading SEO pages/ — 4 PNG files exist: Trading Template Page Forex.png, Crypto Page (Coming Soon).png, News Page.png, Scalping Page.png. No PNG found for Futures Trading or Swing Trading (confirmed via Glob across the whole References/Wireframe/ tree for "Futures" and "Swing" — zero matches).

---

⚠️ CRITICAL — Missing Wireframes for Futures (UC_1.7.1) and Swing Trading (UC_1.7.6)

WBS marks "Status design = Done" for both UC_1.7.1 and UC_1.7.6. The Futures wireframe is still in progress. The Swing Trading layout is confirmed to reuse the Forex template.

[Update — A-15, 2026-07-26] Trading Template Page Futures.png was subsequently added to References/Wireframe/Marketing website/Trading SEO pages/ and is now cited in UC_1.7.1 §9. UC_1.7.1's wireframe blocker is resolved. UC_1.7.6 (Swing Trading) still has no wireframe export — that blocker remains open.

⚠️ CRITICAL — WBS/Customer-supplies conflict on UC_1.7.1 (Futures)

WBS row 17 (UC_1.7.1) "Mapping design" column contains a BA-authored note: "Dùng chung 1 màn SEO template" ("Reuses/shares 1 SEO template screen"). This appears to conflict with StackTrading_Technical_Proposal_v2.4.docx.md (Customer supplies, priority ★★ — a real source-of-truth tier; WBS is a BA planning index, not in the CR→QnA→Customer-supplies priority chain), which explicitly and repeatedly states Futures is the one exception with a custom-coded visual, distinct from the 5-page shared Sanity template group. See A-01.

---

Cross-cutting / Pattern Questions

---

| A-08 | The Crypto Page (Coming Soon).png wireframe's exact visual content (heading text, body message, presence/absence of a CTA button) could not be reliably extracted from the image in this session — only file dimensions were confirmed readable (same limitation encountered for the Utility Suite 404 page wireframe). Per project rule against fabricating unsourced content, what exact copy/CTA does the Coming Soon page show? | Question | Confirmed | BA confirms it is strictly a "Coming Soon" label with no extra specific text content or buttons. | | A-09 | User asked for field-level Sanity CMS editability detail per layout section (Hero header text, images, button URLs, video embeds) for UC_1.7.2/UC_1.7.4/UC_1.7.5/UC_1.7.6. No Sanity Studio schema file exists in Customer supplies, QnA, or WBS — the exact field names/types (string vs text vs block content, internal reference vs external URL toggle for links, etc.) are not confirmed anywhere in the source set. What is the actual Sanity schema shape for the Market Vertical template? | Question | [ASSUMPTION: A-09] | No confirmed schema exists. SRS documents a BA-recommended/expected field mapping (Heading = string, Subheading = text, Hero image = image with hotspot + required alt, Content Blocks = array of objects, FAQ = array of Q&A objects, CTA buttons = Label string + Link toggle between internal reference and external url), inferred from the visual structure of the 3 readable wireframes (Forex/News/Scalping). Flagged for dev confirmation against the actual Sanity schema before final sign-off — do not treat field names as final. | | A-10 | None of the 3 visually-inspected Market Vertical wireframes (Forex, News, Scalping) show a video embed block. Does any Trading SEO page in this module (UC_1.7.2–UC_1.7.6) actually require an embedded video, and if so, what embed mechanism (raw URL + oEmbed, iframe embed code, etc.)? | Question | [ASSUMPTION: A-10] | No video block is confirmed present in the current approved wireframes. SRS documents a forward-looking recommended pattern only (a url field storing the video share link, rendered via oEmbed/iframe) in case a video block is added later — this is explicitly not asserted as a current requirement. Flagged for BA/dev — confirm whether video is in scope at all before implementing any video field. | | A-11 | Per explicit user instruction: on any Trading SEO page, a button labeled "How it works" should behave as a smooth-scroll anchor link to the global "How [Market/Strategy] Prop Trading Works at Stack" block lower on that same page, rather than as a route change. Is the button's destination itself Sanity-editable (e.g., could an editor repoint it elsewhere), or is the anchor target fixed by the frontend? | Question | Confirmed (explicit user instruction); anchor-target fixedness | [ASSUMPTION: A-11] | Documented as: Button Label is Sanity-editable (string); the anchor destination is fixed by frontend logic to that page's own "How It Works" block, not a general Internal/External Button Link field. This fixedness is the BA's inference from the described behavior (a page-specific anchor, not a portable link) — flagged for dev confirmation. | | A-12 | Per explicit user instruction: a button labeled "Get Started" or "Begin your evaluation" should navigate directly into the checkout flow. Does this apply to every such button across all 6 Trading SEO pages uniformly, and is the destination Sanity-editable like a normal CTA link? | Question | Confirmed (explicit user instruction) | Yes — applies module-wide (UC_1.7.1–UC_1.7.6) to any button with this label/purpose. Its Button Link uses the standard Internal Page (reference) / External URL (url) toggle, pointed at the checkout flow route — same editability as other CTA buttons (Ref: § Sanity Field Editability). | | A-13 | Per explicit user instruction: the Hero section (module-wide, and explicitly on Futures) includes a firm/partner logos strip with an auto-playing vertical scrolling motion. Is this logo strip present on all 6 verticals, or Futures-specific? Is the scroll motion itself configurable, or only the logo set? | Question | Confirmed | Confirmed: Logo strip is applied across verticals where present, and the scrolling motion/speed is fixed (hardcoded), not Sanity-configurable. | | A-14 | Per explicit user instruction: the Futures page's chart section is "a high-fidelity, interactive motion section serving as the centerpiece of the technical pitch." The exact data source and interaction behaviors (hover/zoom/scroll-triggered animation, live vs static data) are not specified. | Question | Confirmed | Confirmed that the chart is a video motion/static asset and NOT live data. The exact interaction spec is still pending QnA to convert to video motion. | | A-15 | A wireframe export for Futures (Trading Template Page Futures.png) appeared in References/Wireframe/Marketing website/Trading SEO pages/ after this SRS was first authored (it did not exist when A-02 was originally logged). Does this resolve the UC_1.7.1 wireframe blocker? | Question | Confirmed (file now present, read and cited) | Yes. UC_1.7.1 §9 now cites this file; the UC_1.7.1 wireframe blocker (part of A-02) is resolved. UC_1.7.6 (Swing Trading) still has no wireframe export — that half of A-02 remains open. | | A-16 | Per explicit user instruction, all 4 available Market Vertical wireframes (Forex, Futures, News, Scalping) were re-inspected frame-by-frame (via full-page PNG reads and 4-way/6-way vertical crops, since the prior pass only sampled representative examples) to catalog every distinct layout frame, not just illustrative ones. Does this surface any layout sections beyond the previously-documented Hero → dynamic content blocks → FAQ → final CTA breakdown (A-05)? | Question | Confirmed (visual frame-by-frame re-inspection of all 4 PNGs) | Yes. A full frame catalog was confirmed common to all 4 wireframes: F1 Global Header (UC_01) → F2 Hero Section → F3 Firm Logos Strip → F4 Stats/Trust Bar (newly identified — not previously documented) → F5 Feature/Benefit Content Blocks (repeated; F5b custom chart frame on Futures only) → F6 "How [Market/Strategy] Prop Trading Works at Stack" Steps Block (newly identified — the anchor-scroll destination referenced by A-11; not previously documented as its own frame) → F7 Comparison/Why-Choose-Us Block (newly identified — not previously documented) → F8 FAQ Accordion Block → F9 Final CTA Block → F10 Global Footer (UC_01). This supersedes the coarser 4-section breakdown under A-05 (which is now understood to have only sampled the module's most obvious sections, not the complete set). § Shared Component "Sanity Field Editability" and every UC_1.7.1/13/15/16/17 §10 Screen Description table were rewritten to enumerate F1-F10 explicitly, each annotated with whether it carries an image, text, motion, and/or button. | | A-17 | Per explicit user instruction ("Màn hình future cũng được cấu hình từ sanity nên hãy mô tả lại" — the Futures screen is also configured from Sanity, re-describe it), and using the A-16 frame-by-frame re-inspection of Trading Template Page Futures.png: is Futures (UC_1.7.1) actually built on the same shared Sanity "Market Vertical" template as the other 5 verticals, contradicting the prior framing (A-01) that it is a fully custom-coded, non-CMS-driven exception? | Question | Confirmed (explicit user instruction + frame-by-frame wireframe re-inspection) | Yes — supersedes A-01. Futures follows the identical F2-F9 frame sequence as Forex/News/Scalping/Swing (Ref: A-16) and is Sanity-driven for every one of those frames. Its only genuine deviation from the shared template is one additional, bespoke frame (F5b, the chart/technical-pitch centerpiece, Ref: A-14/BR-1.7.1-05) — this is the single approved custom-visual add-on named in StackTrading_Technical_Proposal_v2.4.docx.md (line 59, 97, 228), not the whole page. UC Index, UC_1.7.1 §1 Overview, BR-1.7.1-01 through BR-1.7.1-05, §9, and §10 in UC_1.7.v1.md were all updated in place to reflect "Sanity Template + 1 Custom Frame" instead of "Custom Visual." A-01 is retained in this doc for audit-trail purposes but its conclusion is no longer authoritative — treat A-17 as controlling. | | A-18 | Per explicit user instruction ("cho phép cấu hình các nút sẽ redirect đến màn hình nào, hay direct tới 1 frame trực tiếp trong màn hình hoặc direct sang 1 đường link URL cụ thể" — allow configuring buttons to redirect to a page, a frame in-page, or an external URL): what is the exact Sanity field structure for this 3-way button destination toggle, replacing the old label-driven fixed-behavior model (A-11/A-12)? | Question | [ASSUMPTION: A-18] | No Sanity Studio schema file confirms this exact structure. Modeled as a Button Link object: Button Label (Text) + Destination Type (Dropdown: Page / Frame / URL) + one of 3 conditionally-required target fields (Target Page = reference, Target Frame = Dropdown of frame names on the current page, Target URL = url). This replaces the old "How it works" vs. "Get Started" label-driven split (A-11/A-12) — those two assumptions are superseded by A-18. UC_1.7.v1.md § CTA Button Destination Rules removed entirely; new § Button Link Field — Shared Destination Model added; F2/F9 button rows in § Sanity Field Editability rewritten to reference it. Flagged for dev confirmation before final sign-off. | | A-19 | Per explicit user instruction ("Từng component sẽ cho phép chọn motion trong danh sách motion được cung cấp" — each component should allow choosing a motion from a provided list): what is the exact enum of available Motion values, and which components/frames carry this field? | Question | Confirmed | Motion is confirmed as fixed/hardcoded for these specific components (like Logo Strip) and not Sanity configurable. | | A-20 | Per explicit user instruction ("Section chart ở future cũng sử dụng sanity, không hardcode" — the Futures chart section also uses Sanity, not hardcoded): is the Futures chart frame (F5b) actually Sanity-configured, contradicting the prior framing (BR-1.7.1-01/BR-1.7.1-02/BR-1.7.1-05, and the A-17 "one custom frame" language) that it is the page's sole custom-coded, non-Sanity-driven frame? | Question | Confirmed | Yes. Modeled with 2 fields: Chart Asset (Image or File) + Chart Caption/Label. A-14's data source is confirmed as non-live video motion. | | A-21 | Per explicit user instruction to re-describe each screen following the real wireframe (Forex/News/Scalping template), a fresh section-by-section re-inspection of the 3 confirmed wireframes was performed. Does this surface additional sections/components beyond the A-16 F1-F10 catalog? | Question | Confirmed (visual section-by-section re-inspection) | Yes — supersedes A-16's F1-F10 catalog for UC_1.7.2/UC_1.7.4/UC_1.7.5/UC_1.7.6. The real structure is materially richer: ~14 distinct sections (S1-S14: Global Header, Hero, Trustpilot Badge + Firm Logos Strip, Regulatory Disclaimer, Feature Cards, Careers/3-Step Section, NY4 Infrastructure Diagram, Spec/Feature Table, Persona Tabs, Comparison Table, Ecosystem Section, FAQ, Final CTA, Global Footer with a second Trustpilot Badge + Firm Logos Strip), including two components not previously documented at all (NY4 Infrastructure Diagram; the footer's second Trustpilot+Logos placement). UC_1.7.v1.md § Sanity Field Editability — by Layout Section was rewritten entirely around this S1-S14 catalog; UC_1.7.2/UC_1.7.4/UC_1.7.5's Post-conditions, Basic Flow, BR-1x-01, §9, and §10 were all updated to reference it. UC_1.7.6 (no wireframe) was updated to expect the same catalog, still gated on A-02. Scope note: this table now explicitly excludes UC_1.7.1/Futures, which has its own distinct layout — see A-25. | | A-22 | The S1-S14 re-inspection (A-21) surfaced a component not present in the prior F1-F10 catalog: a network/infrastructure diagram showing the Co-Located Stack Trading Server, TradingView, AWS Direct Connect, Match-Trader, and MT5 nodes, under a "Global Financial Connectivity Fabric – EQUINIX NY4" banner. What Sanity fields back this component, and is it present on all verticals? | Question | Confirmed | Follows the current live NY4 board structure without modifying data schema, but 'Match-Trader' is replaced with 'TraderEvolution'. | | A-23 | Per explicit user instruction: do the Firm Logos Strip and NY4 Infrastructure Diagram use the shared Motion dropdown, or a motion that is fixed/hardcoded? | Question | Confirmed | Confirmed: Fixed/hardcoded for both. Motion is not Sanity-configurable. | | A-24 | Per explicit user instruction ("khi hiển thị thông tin Trustpilot, trustscore sẽ được gọi API từ bên trustpilot để lấy dữ liệu hiển thị" — when displaying Trustpilot info, the TrustScore is fetched via API from Trustpilot to get the display data): is the Trustpilot TrustScore/badge Sanity content, or live data fetched from Trustpilot's API at render/request time? | Question | Confirmed (explicit user instruction + v7_full.txt line 2445-2451) | Live API data, not Sanity content. Sourced from GET /community/trustpilot-stats (per v7_full.txt line 2445-2451), cached 60 minutes. Applies to both Trustpilot placements: the Hero Trust Strip badge (score only, S3) and the Global Footer badge (score + review count, S14). UC_1.7.v1.md new "§ Trustpilot TrustScore — Live API Field" subsection documents this, applying to UC_1.7.1/UC_1.7.2/UC_1.7.4/UC_1.7.5/UC_1.7.6 (not UC_1.7.3/Crypto, which has no trust strip — Ref: BR-1.7.3-02). Impact: changing the Trustpilot score/count display requires a code/API change, not a Sanity publish. | | A-25 | Per explicit user instruction ("Tương tự ở màn hình layout của future sẽ có layout cấu hình riêng trên sanity" — similarly, the Futures screen layout has its own separate configuration on Sanity): does Futures (UC_1.7.1) actually follow its own distinct Sanity layout, contradicting the prior framing (A-17/A-20) that it follows "the identical F2-F9 frame sequence as Forex/News/Scalping/Swing" plus one bespoke chart frame? | Question | Confirmed (explicit user instruction + full wireframe re-inspection) | Yes — narrows/supersedes A-17's and A-20's "identical frame sequence" framing. A full section-by-section re-inspection of the Futures wireframe found it does not contain the NY4 Infrastructure Diagram, the Trustpilot live-API badges, or several other Forex-template (S1-S14) sections at all — it has its own distinct section set: Hero, Problem-vs-Solution comparison cards, Platform Ecosystem row (Quantower/ATAS/MotiveWave/TradeSea/Sierra Chart), Firm Logos Strip, Feature Content Cards, CME Level 2 Market Data/DOM chart comparison (supersedes the vague A-14 "high-fidelity chart" framing), a 3-step Level I vs Level 2 walkthrough, persona tabs (ES/NQ Scalpers, Oil/Gold Traders, Swing Traders, Micro Futures Traders), a Technical Specifications & Infrastructure table (~10 rows), FAQ, and final CTA. Every section remains Sanity-configured (A-20's editability-mechanism conclusion still holds); what changes is the section catalog itself — Futures does not share the S1-S14 template with UC_1.7.2/UC_1.7.4/UC_1.7.5/UC_1.7.6. UC_1.7.v1.md UC_1.7.1 Overview/BR-1.7.1-01 through BR-1.7.1-09/§9/§10 were rewritten in place around this distinct catalog. Confirmed: Futures' Global Footer also carries the Trustpilot+Logos badge. |

Process Blocker Note (not UC-specific)

---

Next Step

Gate passed (autonomous). A-01 through A-25 have provisional or explicit answers sufficient to proceed without fabricating unsourced content; A-02 (Swing half only), A-03, A-07, A-08, A-09, A-10, A-11, A-13, A-14, A-18, A-19, and A-22 are marked [ASSUMPTION] and must be explicitly re-confirmed by BA/dev before final sign-off. A-01 is superseded by A-17 (see update 3 below); A-11/A-12's fixed-destination framing is superseded by A-18 (see update 5 below); A-16's F1-F10 catalog is superseded by A-21's S1-S14 catalog for UC_1.7.2/UC_1.7.4/UC_1.7.5/UC_1.7.6 (see update 6 below); A-17/A-20's "identical frame sequence" framing for Futures is superseded by A-25 (see update 6 below) — none of these superseded items are open assumptions to re-confirm; all are retained only for audit-trail purposes. A-20, A-23, A-24, and A-25 are confirmed by explicit user instruction and need no further re-confirmation (aside from the narrow open sub-scopes noted in their own rows). Proceeding to Step 3 (Architect) to author the final SRS at docs/BA/UC_1.1-1.9/UC_1.7/UC_1.7.v1.md.

2026-07-26 update (1): Added A-09 (Sanity field-level schema for Hero/image/button/FAQ/content-block editability) and A-10 (no video embed block found in any available wireframe) in response to a follow-up user request to detail per-section Sanity CMS editability. Both logged as assumptions; UC_1.7.v1.md was updated in place (§ Shared Component "Sanity Field Editability" subsection + each UC_1.7.2/14/15/16/17 Screen Description table) — no new file created, per explicit user instruction.

2026-07-26 update (2): Added A-11 through A-15 in response to a follow-up user request specifying: "How it works" button = smooth-scroll anchor to the page's own "How It Works" block; "Get Started"/"Begin your evaluation" button = navigate to checkout flow; a Hero firm-logos strip with auto vertical-scroll motion; and a Futures chart section described as a high-fidelity interactive motion centerpiece. Also discovered Trading Template Page Futures.png now exists in the Wireframe folder (A-15) — this resolves the UC_1.7.1 wireframe blocker (UC_1.7.6/Swing remains open). UC_1.7.v1.md updated in place: new "CTA Button Destination Rules" subsection under § Shared Component, BR-1.7.1-04/BR-1.7.1-05 added to UC_1.7.1, UC_1.7.1 §9/§10 rewritten to cite the new wireframe, and Hero rows in UC_1.7.2/UC_1.7.4/UC_1.7.5/UC_1.7.6 Screen Description tables updated to reference the CTA rules. No new file created, per explicit user instruction.

2026-07-26 update (3): In response to a follow-up user request ("update the UC screen descriptions to match every actual layout frame present, not just illustrative examples; document image/text/motion/button per frame; Futures is also Sanity-configured, re-describe it"), performed a full frame-by-frame visual re-inspection of all 4 available wireframes (Forex, Futures, News, Scalping) using PowerShell System.Drawing slicing (no ImageMagick/Python available in this environment). Added A-16 (new frame catalog F1-F10, surfacing 3 previously-undocumented frames: Stats/Trust Bar, "How It Works" Steps Block, Comparison Block) and A-17 (confirms Futures/UC_1.7.1 is Sanity-driven for all frames except one bespoke chart frame F5b, superseding A-01's "fully custom visual" framing). UC_1.7.v1.md updated in place: § Shared Component intro + "Layout structure" bullet + "Sanity Field Editability" subsection rewritten around F1-F10; UC_1.7.1 Overview/BR-1.7.1-01 through BR-1.7.1-05/§9/§10 rewritten to present Futures as Sanity-configured plus one custom frame; UC_1.7.2/UC_1.7.4/UC_1.7.5's §10 Screen Description tables rewritten into 9-row F2-F9+Impact structure; UC_1.7.6's Basic Flow step 3 and §10 table updated to the same F2-F9 pattern with [BLOCKER — A-02] caveats retained (no Swing wireframe); UC Index and UC_1.7.1 §1 Use Case name corrected from "Custom Visual" to "Sanity Template + 1 Custom Frame" for consistency. No new file created, per the standing explicit user instruction to edit in place.

2026-07-26 update (4): In response to a follow-up user request ("gộp các màn có layout cấu hình trên sanity tương tự nhau, refer đến UC gốc; đổi format bảng Sanity config sang format Page Name/URL Slug/Status/SEO Title/.../Canonical URL kèm validation rule rõ ràng") — merged the per-UC §10 Screen Description tables for UC_1.7.1 (except its 1 custom chart frame), UC_1.7.2, UC_1.7.4, UC_1.7.5, UC_1.7.6 into two single canonical tables under § Shared Component: a new "Sanity Page Configuration Fields" table (Page Name/URL Slug/Status/SEO Title/SEO Description/OG Image/Canonical URL, per the user-supplied format) and a rewritten "Sanity Field Editability — by Layout Section" table (F2-F9, one row per field, each with an explicit Field Type + a concrete Validation/Behaviour Rule sentence, following the same format style as the user's example). Each of UC_1.7.1/13/15/16/17's own §10 now only contains a short reference back to these 2 shared tables plus whatever is unique to that UC (UC_1.7.1's F5b chart frame; UC_1.7.6's [BLOCKER — A-02] no-wireframe caveat) — no content was dropped, only de-duplicated. UC_1.7.v1.md updated in place; no new file created, per the standing explicit user instruction.

2026-07-26 update (5): In response to a follow-up user request ("Hãy update lại mô tả màn hình của các nút CTA cho phép cấu hình các nút sẽ redirect đến màn hình nào, hay direct tới 1 frame trực tiếp trong màn hình hoặc direct sang 1 đường link URL cụ thể. Từng component sẽ cho phép chọn motion trong danh sách motion được cung cấp. Section chart ở future cũng sử dụng sanity, không hardcode... Bỏ mục mô tả button destination... Các UC mô tả tương tự thì sẽ có refer tham chiếu gắn link") — three new assumptions added (A-18, A-19, A-20). The old "§ CTA Button Destination Rules" section (fixed "How it works"/"Get Started" destinations, A-11/A-12) was removed entirely and replaced with two new shared subsections: "§ Button Link Field — Shared Destination Model" (a general Page/Frame/URL destination toggle usable by any CTA button, per A-18) and "§ Motion Field — Shared Motion Selector" (a shared Dropdown enum usable by any frame/component, per A-19). UC_1.7.1's chart frame (F5b) was corrected throughout (UC Index, §1 Overview, §4, §5, BR-1.7.1-01 through BR-1.7.1-05, §9, §10) from "hardcoded/custom-coded, non-Sanity" to Sanity-configured, per A-20 — narrowing A-17's "one custom frame" language to mean structurally extra, not content-editability-exempt. §10 intro paragraphs across UC_1.7.1/13/15/16/17 were updated with explicit anchor links to the 4 shared subsections and to sibling UCs with matching Sanity mechanics, satisfying the cross-reference request. UC_1.7.v1.md updated in place; no new file created, per the standing explicit user instruction.

2026-07-26 update (6): In response to a follow-up user request to re-describe every screen following the real wireframe layout, with per-section icon/text/button/image/card-level detail; to correct the Firm Logos Strip and NY4 Infrastructure Diagram motion to fixed/hardcoded (not Sanity-configurable); to document Trustpilot TrustScore as live API data, not Sanity content; and to give Futures its own distinct Sanity layout description — five new assumptions added (A-21 through A-25). A full section-by-section re-inspection of the Forex/News/Scalping and Futures wireframes was performed. Changes to UC_1.7.v1.md, all in place, no new file created:

• New "Fixed-Motion Exceptions (not Sanity-configurable)" subsection under § Motion Field — Shared Motion Selector, documenting the Firm Logos Strip and NY4 Infrastructure Diagram (A-23).
• New "§ Trustpilot TrustScore — Live API Field" subsection, documenting the live GET /community/trustpilot-stats API source for the Hero and Footer Trustpilot badges (A-24).
• The old F1-F10 "§ Sanity Field Editability — by Layout Section" table was replaced entirely with a new S1-S14 catalog (A-21), scope-narrowed to UC_1.7.2/UC_1.7.4/UC_1.7.5/UC_1.7.6 only, plus a new "§ NY4 Infrastructure Diagram Field" sub-table (A-22).
• UC_1.7.1 (Futures) was rewritten in full — Overview, Post-conditions, all Business Rules (BR-1.7.1-01 through BR-1.7.1-09, replacing the old BR-1.7.1-01 through BR-1.7.1-05), §9, and §10 — to document its own distinct section catalog (Hero, Problem-vs-Solution Cards, Firm Logos Strip, Platform Ecosystem Row, Feature Content Cards, CME Level 2/DOM Comparison, 3-Step Walkthrough, Persona Tabs, Tech Spec Table, FAQ, Final CTA), per A-25.
• UC_1.7.2, UC_1.7.4, UC_1.7.5's Post-conditions, Basic Flow step 3, BR-1x-01, §9, and §10 were all updated to reference the new S1-S14 catalog and shared subsections, and to explicitly exclude UC_1.7.1/Futures from the shared grouping (Ref: A-25).
• UC_1.7.6's Post-conditions, Basic Flow step 3, BR-1.7.6-01, §9, and §10 were updated to expect the same S1-S14 catalog, with the [BLOCKER — A-02] no-wireframe caveat retained and re-scoped to the new section list. No content was dropped; superseded framings (A-16's F1-F10 catalog, A-17/A-20's "identical frame sequence" language for Futures) are retained in this doc for audit-trail purposes only, per the standing explicit user instruction to edit in place.

2026-07-27 update (7): In response to a follow-up user request to (a) resolve all remaining open [ASSUMPTION]/[BLOCKER] markers in UC_1.7.v1.md sensibly, (b) attach 2 Google Drive motion-reference links (NY4 diagram → Forex/News/Scalping/Swing; CME Level 2/DOM "Stop Trading Blind" chart → Futures), (c) add an endpoint-reference detail for the Trustpilot TrustScore section sourced from/cross-checked against the Zapier reference sheet, (d) restrict every Business Rule section to only two rule types (empty-data display behavior; motion-change lockstep — a motion change requires the paired reference frame/clip to be updated, while Sanity content changes auto-publish without further action), and (e) trim every §9 Wireframe/UI section down to the wireframe link only (no "Update"/"Blocker" commentary):

• Every remaining [ASSUMPTION]/[BLOCKER] marker in UC_1.7.v1.md was resolved in place (A-07, A-08, A-09, A-13, A-14, A-18, A-19, and the UC_1.7.6 wireframe/A-02 items) — confirmed via a full-document grep showing zero remaining ASSUMPTION/BLOCKER tags in the SRS body.
• NY4 motion reference link (.../1jN5AJKqK3Pr97jzUzr5uG01hmcZ5WslF) added to: § Fixed-Motion Exceptions (NY4 row), § NY4 Infrastructure Diagram Field (Diagram Motion row) — both apply to UC_1.7.2/UC_1.7.4/UC_1.7.5/UC_1.7.6 by the shared-template mechanism.
• Chart motion reference link (.../1b0ZpmiX27ICIV105UqMyEjMIc_ZE1g-K) added to UC_1.7.1 BR-1.7.1-05 (CME Level 2/DOM "Stop Trading Blind" comparison) and its §10 table row.
• § Trustpilot TrustScore — Live API Field given a new "Endpoint reference" table citing v7_full.txt line 2445-2451 (GET /community/trustpilot-stats), plus a note cross-checking zapier_v7_full.txt — confirmed this specific score-fetch call is a direct backend proxy, not a Zapier-triggered flow (Zapier only touches the separate trigger-review-invite endpoint, Flow 2/Flow 5).
• Every Business Rule section (Shared Architecture § Fixed-Motion Exceptions/§ NY4 Infrastructure Diagram Field, and BR-1.7.1-04/BR-1.7.1-05 for UC_1.7.1, BR-1.7.2-01/BR-1.7.4-01/BR-1.7.5-01/BR-1.7.6-01, BR-1.7.3-01/BR-1.7.3-02 for UC_1.7.3) was trimmed to contain only empty-data display rules and the motion-change-lockstep rule — mechanism/schema/section-catalog descriptions (shared template reuse, section inventories, field shapes) were moved to or left in §10 and the shared architecture sections, not duplicated as "Business Rule" content. UC_1.7.1's BR-1.7.1-01/02/03/06/07/08/09 (mechanism and new-section descriptions) were removed from § 8 Business Rule and folded into §10's existing table, which already carried the field-level detail.
• Every §9 Wireframe/UI section (UC_1.7.1 through UC_1.7.6) reduced to a single wireframe-link bullet; UC_1.7.6 now cites Trading Template Page Forex.png as its structural reference in the absence of a dedicated Swing PNG.
• Changelog table in UC_1.7.v1.md updated with a new 2026-07-27 row; A-02 and A-07 rows in this doc's Cross-cutting table marked Resolved. No content was dropped that fell inside the two permitted Business Rule categories; content outside that scope was relocated rather than deleted, consistent with the standing explicit user instruction to edit in place.