Dashboard | Gastx Content Admin

Scope

6 content modules

FAQ、Knowledge、SEO Pages、Channel Landing、Site Settings、Locale Content。

Locales

2 configured

默认语种 en，先定义语言矩阵和共享区块，再接真实发布流。

Forbidden drift

No trading ops

订单、支付、代理、机器人运营全部不在本后台实现。

Runtime contract

Env contract loaded

共享配置结构已接入后台。

Full Delivery Readiness

竞品功能级完整交付入口

这里把像素矩阵、开发者 API 文档、生产 cutover gates、tracking 生产计划和剩余 parity gap 放到同一个后台入口。每张卡都明确 source path、owner、生产边界和验收链接，避免把本地验收误判成云端生产。

Source: data/content/site-settings.json -> tracking.socialPixels

只控制公开站浏览器像素启停和 ID 来源，不保存 CAPI secret，不代表生产归因仓库上线。

Verification: content-admin /content/settings 可见 Google / Meta / TikTok / X / LinkedIn / Reddit / Pinterest / Snap。

Open surface

Source: docs/integrations/developer-api.md

文档描述 /api/v1 合约和签名规则；真实密钥、客户白名单和生产 URL 必须来自生产环境。

Verification: pnpm --filter user-center typecheck/lint/build；签名 API smoke 在 cutover gates 通过后执行。

Open surface

Source: docs/integrations/production-cutover.md + docs/deployment/production-env-runbook.md

只读 smoke 不创建订单、不投递 Webhook、不触发 TRON tick；写路径 smoke 需要生产 operator 确认。

Verification: pnpm test:cutover-env；pnpm test:cutover-smoke；pnpm cutover:smoke -- --base-url <candidate> --strict。

Open surface

Source: data/content/tracking-production-plan.json

tracking 事件和像素映射只做增长归因，不作为支付、订单、余额、代理分润或链上交付依据。

Verification: Dashboard destination mapping table renders page_view / click_buy / click_tg_bot / click_api / click_partner_apply / submit_lead。

Open surface

Source: docs/competitive/competitor-parity-production-gap-register.md

做功能级 parity，不照抄竞品品牌、文案、素材或受保护设计表达。

Verification: 每个 gap 都必须有 user-center route、API route、store/table、admin action、生产 env、smoke command 和边界。

Open surface

Public Tracking Intake

公开站按钮事件与渠道参数验收

CatFee 的关键入口都是业务按钮；本项目现在把公开站 page view 和 CTA click 写入本地 local-intake consumer，运营后台可以直接验收事件是否到达、来自哪个渠道、落在哪个页面。

Store: ../../data/content/tracking-events.json

Archive: ../../data/content/tracking-events-archive.json

55

Total accepted events

Last received: 2026-05-22T19:14:52.729Z

1

Conversion intent events

click_buy / contact / API / TG / partner / lead

/api/tracking/events

Local intake endpoint

Local JSON only; not production attribution or pixel callback.

page_view54
click_contact1

direct55

page_view/zh-cn/pricing
page_view/zh-cn
page_view/en
page_view/zh-cn

重新采样路径清空后打开公开站 `http://localhost:3300/zh-cn?utm_source=google&utm_campaign=qa-resample`，再点击购买、 Telegram、API 或联系按钮，即可重新生成 page_view 和 CTA click 样本。

从 local-intake consumer 到生产事件链路

当前后台已经能验收公开站事件，但生产交付必须明确真实 consumer、失败重试、事件审计表和像素平台映射。这块面板用于锁定边界，避免把本地 JSON local-intake 误判为生产归因系统。

4

Production stages

1 local-intake / 3 planned /0 blocked

6

Event destination mappings

tracking_events / conversion queue / pixel platforms / warehouse

Not production yet

Current store remains local JSON

No payment callback, no order status, no agency settlement.

Current: gastx-web POST /api/tracking/events，写入本地 JSON store。
Production target: 统一写入后端 tracking consumer，服务端校验 payload、来源、幂等键和环境。
Boundary: 公开站只负责生成可信 payload，不负责投放账户、结算或业务订单。
Next action: 确定生产 intake URL、鉴权方式、事件幂等键和 server-side channel 参数来源。

Current: 当前 local-intake 失败只进入浏览器队列和本地验收，不保证送达。
Production target: 接入持久化队列，记录 retry_count、next_retry_at、last_error 和 dead-letter reason。
Boundary: 失败重试只处理 tracking 事件，不重试支付、订单或链上交付。
Next action: 选择队列介质并定义最多重试次数、退避策略和死信人工处理入口。

Current: content-admin 读取 data/content/tracking-events.json 和 archive JSON。
Production target: 落地 tracking_events 表，支持 event/channel/page/status/error 查询和导出。
Boundary: 审计表只证明事件到达和字段完整，不作为财务、分润或用户余额依据。
Next action: 定义表结构、索引、保留周期、PII 字段白名单和导出权限。

Current: Site Settings 管理 tracking/pixel 文案和默认配置；事件已能在后台验收。
Production target: 按 eventName 映射 Google/Meta/TikTok/X/LinkedIn/Reddit/Pinterest/Snap/Microsoft/Quora/Taboola/Outbrain/Yahoo/VK/LINE/Kakao/Telegram 事件名、参数和启停状态。
Boundary: 像素映射只做公开站归因，不承载真实订单状态、支付回调或代理结算。
Next action: 确认每个平台的事件名、参数白名单、测试 ID、生产开关审批流程和 CAPI/服务器回传边界；Meta 覆盖 Facebook/Instagram/WhatsApp/Audience Network，WhatsApp 不作为独立网页像素。

EventProduction destinationsRequired fieldsRisk if missing

page_viewtracking_events / analytics warehouse / Google page_view / Meta PageView / TikTok Pageview / X PageView / Reddit PageVisit / Pinterest pagevisit / Snap PAGE_VIEW / Microsoft UET page_view / Quora ViewContent / Taboola page_view / Outbrain PAGE_VIEW / Yahoo pageview / VK page_view / LINE page_view / Kakao pageViewoccurredAt, channel, context.locale, context.pageType, context.path无法判断渠道入口、页面覆盖和投放落地页是否正常。

click_buytracking_events / conversion queue / Google generate_lead / Meta InitiateCheckout / TikTok InitiateCheckout / X Lead / Reddit Lead / Pinterest lead / Snap SIGN_UP / Microsoft UET lead / Quora Lead / Taboola lead / Outbrain Lead / Yahoo begincheckout / VK lead / LINE conversion / Kakao completeRegistrationproperties.placement, properties.target, channelParams, context.path购买按钮无法和具体页面、渠道、CTA 位置关联。

click_tg_bottracking_events / conversion queue / Telegram campaign report / Google generate_lead / Meta Lead / TikTok Contact / X Lead / Reddit Lead / Pinterest lead / Snap SIGN_UP / Microsoft UET lead / Quora Lead / Taboola lead / Outbrain Lead / Yahoo lead / VK lead / LINE conversion / Kakao participationproperties.placement, properties.botSlug, channelParams, context.localeTG Bot 导流无法区分自然入口、广告入口和客服入口。

click_apitracking_events / developer lead pipeline / conversion queue / Google generate_lead / Meta Lead / TikTok Contact / X Lead / LinkedIn conversion / Reddit Lead / Pinterest lead / Snap SIGN_UP / Microsoft UET lead / Quora Lead / Taboola lead / Outbrain Lead / Yahoo lead / VK lead / LINE conversion / Kakao participationproperties.target, properties.placement, context.pageType, channelParams开发者意向无法回流到 API 线索和后续销售/支持路径。

click_partner_applytracking_events / partner lead pipeline / conversion queue / Google generate_lead / Meta Lead / TikTok Contact / X Lead / LinkedIn conversion / Reddit Lead / Pinterest lead / Snap SIGN_UP / Microsoft UET lead / Quora Lead / Taboola lead / Outbrain Lead / Yahoo lead / VK lead / LINE conversion / Kakao participationproperties.target, properties.placement, context.pageType, channelParams代理、渠道和合作申请无法和投放来源、站内入口及后续运营审批关联。

submit_leadtracking_events / lead CRM / conversion queue / Google generate_lead / Meta Lead / TikTok SubmitForm / X Lead / LinkedIn conversion / Reddit Lead / Pinterest lead / Snap SIGN_UP / Microsoft UET lead / Quora Lead / Taboola lead / Outbrain Lead / Yahoo lead / VK lead / LINE conversion / Kakao completeRegistrationproperties.formId, properties.intent, properties.success, context.path表单线索无法判断是否成功提交、来自哪个页面和意向类型。

高级源文件维护

Source payload

{
  "schemaVersion": 1,
  "updatedAt": "2026-05-22T16:12:00.000Z",
  "stages": [
    {
      "key": "runtime-intake",
      "title": "Runtime intake",
      "status": "local-intake",
      "owner": "Frontend + platform",
      "boundary": "公开站只负责生成可信 payload，不负责投放账户、结算或业务订单。",
      "currentState": "gastx-web POST /api/tracking/events，写入本地 JSON store。",
      "productionTarget": "统一写入后端 tracking consumer，服务端校验 payload、来源、幂等键和环境。",
      "nextAction": "确定生产 intake URL、鉴权方式、事件幂等键和 server-side channel 参数来源。"
    },
    {
      "key": "retry-queue",
      "title": "Retry queue",
      "status": "planned",
      "owner": "Backend",
      "boundary": "失败重试只处理 tracking 事件，不重试支付、订单或链上交付。",
      "currentState": "当前 local-intake 失败只进入浏览器队列和本地验收，不保证送达。",
      "productionTarget": "接入持久化队列，记录 retry_count、next_retry_at、last_error 和 dead-letter reason。",
      "nextAction": "选择队列介质并定义最多重试次数、退避策略和死信人工处理入口。"
    },
    {
      "key": "audit-table",
      "title": "Event audit table",
      "status": "planned",
      "owner": "Data + ops",
      "boundary": "审计表只证明事件到达和字段完整，不作为财务、分润或用户余额依据。",
      "currentState": "content-admin 读取 data/content/tracking-events.json 和 archive JSON。",
      "productionTarget": "落地 tracking_events 表，支持 event/channel/page/status/error 查询和导出。",
      "nextAction": "定义表结构、索引、保留周期、PII 字段白名单和导出权限。"
    },
    {
      "key": "pixel-mapping",
      "title": "Pixel mapping",
      "status": "planned",
      "owner": "Growth ops",
      "boundary": "像素映射只做公开站归因，不承载真实订单状态、支付回调或代理结算。",
      "currentState": "Site Settings 管理 tracking/pixel 文案和默认配置；事件已能在后台验收。",
      "productionTarget": "按 eventName 映射 Google/Meta/TikTok/X/LinkedIn/Reddit/Pinterest/Snap/Microsoft/Quora/Taboola/Outbrain/Yahoo/VK/LINE/Kakao/Telegram 事件名、参数和启停状态。",
      "nextAction": "确认每个平台的事件名、参数白名单、测试 ID、生产开关审批流程和 CAPI/服务器回传边界；Meta 覆盖 Facebook/Instagram/WhatsApp/Audience Network，WhatsApp 不作为独立网页像素。"
    }
  ],
  "destinationMappings": [
    {
      "event": "page_view",
      "currentConsumer": "Local JSON local-intake",
      "productionDestinations": [
        "tracking_events",
        "analytics warehouse",
        "Google page_view",
        "Meta PageView",
        "TikTok Pageview",
        "X PageView",
        "Reddit PageVisit",
        "Pinterest pagevisit",
        "Snap PAGE_VIEW",
        "Microsoft UET page_view",
        "Quora ViewContent",
        "Taboola page_view",
        "Outbrain PAGE_VIEW",
        "Yahoo pageview",
        "VK page_view",
        "LINE page_view",
        "Kakao pageView"
      ],
      "requiredPayloadFields": [
        "occurredAt",
        "channel",
        "context.locale",
        "context.pageType",
        "context.path"
      ],
      "riskIfMissing": "无法判断渠道入口、页面覆盖和投放落地页是否正常。"
    },
    {
      "event": "click_buy",
      "currentConsumer": "Local JSON local-intake",
      "productionDestinations": [
        "tracking_events",
        "conversion queue",
        "Google generate_lead",
        "Meta InitiateCheckout",
        "TikTok InitiateCheckout",
        "X Lead",
        "Reddit Lead",
        "Pinterest lead",
        "Snap SIGN_UP",
        "Microsoft UET lead",
        "Quora Lead",
        "Taboola lead",
        "Outbrain Lead",
        "Yahoo begincheckout",
        "VK lead",
        "LINE conversion",
        "Kakao completeRegistration"
      ],
      "requiredPayloadFields": [
        "properties.placement",
        "properties.target",
        "channelParams",
        "context.path"
      ],
      "riskIfMissing": "购买按钮无法和具体页面、渠道、CTA 位置关联。"
    },
    {
      "event": "click_tg_bot",
      "currentConsumer": "Local JSON local-intake",
      "productionDestinations": [
        "tracking_events",
        "conversion queue",
        "Telegram campaign report",
        "Google generate_lead",
        "Meta Lead",
        "TikTok Contact",
        "X Lead",
        "Reddit Lead",
        "Pinterest lead",
        "Snap SIGN_UP",
        "Microsoft UET lead",
        "Quora Lead",
        "Taboola lead",
        "Outbrain Lead",
        "Yahoo lead",
        "VK lead",
        "LINE conversion",
        "Kakao participation"
      ],
      "requiredPayloadFields": [
        "properties.placement",
        "properties.botSlug",
        "channelParams",
        "context.locale"
      ],
      "riskIfMissing": "TG Bot 导流无法区分自然入口、广告入口和客服入口。"
    },
    {
      "event": "click_api",
      "currentConsumer": "Local JSON local-intake",
      "productionDestinations": [
        "tracking_events",
        "developer lead pipeline",
        "conversion queue",
        "Google generate_lead",
        "Meta Lead",
        "TikTok Contact",
        "X Lead",
        "LinkedIn conversion",
        "Reddit Lead",
        "Pinterest lead",
        "Snap SIGN_UP",
        "Microsoft UET lead",
        "Quora Lead",
        "Taboola lead",
        "Outbrain Lead",
        "Yahoo lead",
        "VK lead",
        "LINE conversion",
        "Kakao participation"
      ],
      "requiredPayloadFields": [
        "properties.target",
        "properties.placement",
        "context.pageType",
        "channelParams"
      ],
      "riskIfMissing": "开发者意向无法回流到 API 线索和后续销售/支持路径。"
    },
    {
      "event": "click_partner_apply",
      "currentConsumer": "Local JSON local-intake",
      "productionDestinations": [
        "tracking_events",
        "partner lead pipeline",
        "conversion queue",
        "Google generate_lead",
        "Meta Lead",
        "TikTok Contact",
        "X Lead",
        "LinkedIn conversion",
        "Reddit Lead",
        "Pinterest lead",
        "Snap SIGN_UP",
        "Microsoft UET lead",
        "Quora Lead",
        "Taboola lead",
        "Outbrain Lead",
        "Yahoo lead",
        "VK lead",
        "LINE conversion",
        "Kakao participation"
      ],
      "requiredPayloadFields": [
        "properties.target",
        "properties.placement",
        "context.pageType",
        "channelParams"
      ],
      "riskIfMissing": "代理、渠道和合作申请无法和投放来源、站内入口及后续运营审批关联。"
    },
    {
      "event": "submit_lead",
      "currentConsumer": "Local JSON local-intake",
      "productionDestinations": [
        "tracking_events",
        "lead CRM",
        "conversion queue",
        "Google generate_lead",
        "Meta Lead",
        "TikTok SubmitForm",
        "X Lead",
        "LinkedIn conversion",
        "Reddit Lead",
        "Pinterest lead",
        "Snap SIGN_UP",
        "Microsoft UET lead",
        "Quora Lead",
        "Taboola lead",
        "Outbrain Lead",
        "Yahoo lead",
        "VK lead",
        "LINE conversion",
        "Kakao completeRegistration"
      ],
      "requiredPayloadFields": [
        "properties.formId",
        "properties.intent",
        "properties.success",
        "context.path"
      ],
      "riskIfMissing": "表单线索无法判断是否成功提交、来自哪个页面和意向类型。"
    }
  ]
}

Business Delivery Readiness

支付、订单、交付、代理与生产 tracking 接线板

当前本地本地验收已经可以演示核心路径，但真实交付不能把 local-data 当成生产。这个面板把低完成度模块变成可运营 readiness 数据源，明确每个真实接线域的当前界面、生产缺口、下一步和验收信号。

80%

Local local-intake delivery scope

可本地演示和继续开发；不等于真实支付、订单、用户权限或代理结算上线。

46%

Production backend wiring

真实账户、支付回调、交付队列、代理结算仍需后端接线。

5

Readiness domains

1 local-ready / 3 runtime /1 contract / 0 planned /0 blocked

Current surface: user-center account snapshot, recharge workbench, and business-runtime payment address config
Operational surface: user-center /overview, /recharge and content-admin readiness panel
Production gap: No authenticated account ledger, balance mutation table, deposit confirmation, or adjustment audit has been connected.
Next actions: Define account ledger tables and immutable balance mutation model. / Connect recharge confirmation to user balance only after chain/payment verification. / Add operator audit records for manual adjustments.
Acceptance: Balance cannot change without a ledger mutation. / Every manual adjustment has operator, reason, before and after values. / User-center reads authenticated account balance instead of local-data snapshot.

Current surface: business-runtime order creation with robot payment address and address-monitor callback intake
Operational surface: user-center /orders, /api/user-center/orders/create, /api/user-center/payments/address-monitor and dashboard readiness panel
Production gap: Local runtime now has order creation, payment callback idempotency, and state transitions; production still needs authenticated users, database persistence, signed callback verification, reconciliation, refund, and dispute flow.
Next actions: Replace JSON runtime with formal order/payment tables and authenticated user ownership. / Add signed address-monitor callback verification and reconciliation job. / Split refund/dispute handling from user-center display.
Acceptance: Duplicate callbacks do not double-deliver resources. / Orders expose user-safe status while preserving internal reconciliation state. / Refund/dispute transitions are audit logged.

Current surface: business-runtime delivery job queue generated after payment confirmation
Operational surface: GET/POST /api/user-center/delivery/jobs and system-center runtime payload
Production gap: Local runtime now creates and confirms delivery jobs; production still needs provider adapter, chain confirmation polling, retry, and rollback policy.
Next actions: Connect GASTX robot/provider adapter for energy and bandwidth delivery. / Add signed provider callbacks, retry limits, and terminal failure states. / Expose user-safe delivery progress without leaking provider internals.
Acceptance: Delivery retries are bounded and visible to operators. / User order state tracks delivery progress without claiming success early. / Provider errors map to support and refund paths.

Current surface: agent-center plus runtime settlement candidates generated from paid orders
Operational surface: GET /api/user-center/agent, GET /api/user-center/agent/settlements and system-center runtime payload
Production gap: Local runtime now generates agent settlement candidates from paid order facts; production still needs agent account model, attribution ledger, commission rules, settlement statement, and payout approval permissions.
Next actions: Bind agent identity and invite/channel attribution to authenticated orders. / Move commission rules into a versioned ledger independent from content operations. / Add settlement review and payout approval workflow.
Acceptance: Agent revenue is calculated from immutable order/channel facts. / Settlement approval is separate from content-admin permissions. / Operators can inspect attribution without editing public content.

Current surface: POST/GET /api/tracking/events and dashboard event operations
Operational surface: content-admin dashboard tracking intake and production plan editor
Production gap: Current JSON store is only local local-intake intake; no production queue, warehouse, pixel callback, retry DLQ, or billing decision hook is live.
Next actions: Replace JSON store with production event queue and audit table. / Map conversion events to pixel platforms only after consent and payload validation. / Keep billing/order decisions out of browser tracking payloads.
Acceptance: Event writes survive process restart and include retry state. / Pixel destinations receive only mapped, validated events. / No billing or payment decision depends on untrusted browser payloads.

高级源文件维护

Source payload

{
  "schemaVersion": 1,
  "updatedAt": "2026-05-09T20:35:00.000Z",
  "localDeliveryPercent": 80,
  "productionBackendPercent": 46,
  "domains": [
    {
      "key": "account-ledger",
      "title": "账户与余额账本",
      "status": "contract-defined",
      "owner": "business-backend",
      "currentSurface": "user-center account snapshot, recharge workbench, and business-runtime payment address config",
      "operationalSurface": "user-center /overview, /recharge and content-admin readiness panel",
      "productionGap": "No authenticated account ledger, balance mutation table, deposit confirmation, or adjustment audit has been connected.",
      "nextActions": [
        "Define account ledger tables and immutable balance mutation model.",
        "Connect recharge confirmation to user balance only after chain/payment verification.",
        "Add operator audit records for manual adjustments."
      ],
      "acceptanceSignals": [
        "Balance cannot change without a ledger mutation.",
        "Every manual adjustment has operator, reason, before and after values.",
        "User-center reads authenticated account balance instead of local-data snapshot."
      ]
    },
    {
      "key": "orders-payments",
      "title": "订单创建与支付回调",
      "status": "runtime-skeleton",
      "owner": "business-backend",
      "currentSurface": "business-runtime order creation with robot payment address and address-monitor callback intake",
      "operationalSurface": "user-center /orders, /api/user-center/orders/create, /api/user-center/payments/address-monitor and dashboard readiness panel",
      "productionGap": "Local runtime now has order creation, payment callback idempotency, and state transitions; production still needs authenticated users, database persistence, signed callback verification, reconciliation, refund, and dispute flow.",
      "nextActions": [
        "Replace JSON runtime with formal order/payment tables and authenticated user ownership.",
        "Add signed address-monitor callback verification and reconciliation job.",
        "Split refund/dispute handling from user-center display."
      ],
      "acceptanceSignals": [
        "Duplicate callbacks do not double-deliver resources.",
        "Orders expose user-safe status while preserving internal reconciliation state.",
        "Refund/dispute transitions are audit logged."
      ]
    },
    {
      "key": "resource-delivery",
      "title": "资源交付与链上状态",
      "status": "runtime-skeleton",
      "owner": "delivery-runtime",
      "currentSurface": "business-runtime delivery job queue generated after payment confirmation",
      "operationalSurface": "GET/POST /api/user-center/delivery/jobs and system-center runtime payload",
      "productionGap": "Local runtime now creates and confirms delivery jobs; production still needs provider adapter, chain confirmation polling, retry, and rollback policy.",
      "nextActions": [
        "Connect GASTX robot/provider adapter for energy and bandwidth delivery.",
        "Add signed provider callbacks, retry limits, and terminal failure states.",
        "Expose user-safe delivery progress without leaking provider internals."
      ],
      "acceptanceSignals": [
        "Delivery retries are bounded and visible to operators.",
        "User order state tracks delivery progress without claiming success early.",
        "Provider errors map to support and refund paths."
      ]
    },
    {
      "key": "agent-operations",
      "title": "代理与总运营后台",
      "status": "runtime-skeleton",
      "owner": "ops-admin",
      "currentSurface": "agent-center plus runtime settlement candidates generated from paid orders",
      "operationalSurface": "GET /api/user-center/agent, GET /api/user-center/agent/settlements and system-center runtime payload",
      "productionGap": "Local runtime now generates agent settlement candidates from paid order facts; production still needs agent account model, attribution ledger, commission rules, settlement statement, and payout approval permissions.",
      "nextActions": [
        "Bind agent identity and invite/channel attribution to authenticated orders.",
        "Move commission rules into a versioned ledger independent from content operations.",
        "Add settlement review and payout approval workflow."
      ],
      "acceptanceSignals": [
        "Agent revenue is calculated from immutable order/channel facts.",
        "Settlement approval is separate from content-admin permissions.",
        "Operators can inspect attribution without editing public content."
      ]
    },
    {
      "key": "tracking-consumer",
      "title": "生产 tracking consumer",
      "status": "local-ready",
      "owner": "growth-data",
      "currentSurface": "POST/GET /api/tracking/events and dashboard event operations",
      "operationalSurface": "content-admin dashboard tracking intake and production plan editor",
      "productionGap": "Current JSON store is only local local-intake intake; no production queue, warehouse, pixel callback, retry DLQ, or billing decision hook is live.",
      "nextActions": [
        "Replace JSON store with production event queue and audit table.",
        "Map conversion events to pixel platforms only after consent and payload validation.",
        "Keep billing/order decisions out of browser tracking payloads."
      ],
      "acceptanceSignals": [
        "Event writes survive process restart and include retry state.",
        "Pixel destinations receive only mapped, validated events.",
        "No billing or payment decision depends on untrusted browser payloads."
      ]
    }
  ]
}

沉淀高频问题、购买顾虑、付款解释、机器人与 API 常见问题。

服务对象：普通用户 / 客服前置

边界：只管问答内容和支持入口，不处理真实工单或会话。

Open module

承载 TRON Energy、租赁逻辑、API 入门、TG Bot 教程等长尾内容。

服务对象：搜索用户 / 批量用户 / 开发者

边界：只管内容资产，不承担 API 文档系统或订单控制台。

Open module

集中管理页面标题、描述、canonical、robots 和结构化数据备注。

服务对象：SEO / 站点负责人

边界：只做搜索可见性管理，不接广告回传和报表。

Open module

管理渠道落地页定位、CTA、索引策略、参数预设和合规备注。

服务对象：投放 / 联盟 / 渠道合作

边界：只定义页面和参数，不做广告平台投放后台。

Open module

统一维护品牌文案、站点链接、联系入口、脚本位和默认 SEO 配置。

服务对象：站点运营 / 品牌 owner

边界：只做官网配置，不混入支付通道、代理规则或产品定价引擎。

Open module

管理语种矩阵、共享区块翻译、落地页本地化优先级和缺口清单。

服务对象：翻译 / 内容运营 / 增长

边界：只管内容本地化，不扩展成多地区订单和财税系统。

Open module

Operating Lanes

后台不是模块堆砌，而是三条运营主线

内容后台要先服务多语言、站点配置、渠道落地页和 SEO/内容协同。每条线都有固定 owner、固定顺序和固定交付口。

先定义语种优先级、共享文案归属和 fallback 规则，再决定哪些内容与渠道页需要本地化。

Locale Content定义市场、负责人和覆盖缺口。Site Settings维护全站共享 CTA、联系入口和语言默认项。FAQ优先补购买疑虑与支持前置问答。

Success signal: 核心导航、CTA、FAQ 和帮助页已经明确语种覆盖范围。

先确定渠道入口、文案角度和参数规范，再安排索引策略和转化 CTA。

Site Settings读取像素位、跳转目标和品牌级默认项。Channel Landing配置广告角度、CTA 和参数预设。SEO Pages记录 canonical、robots 和渠道页例外说明。

Success signal: 渠道落地页、noindex 策略和 tracking/pixel 配置可以一起上线。

围绕主站页面、知识内容和 FAQ 形成搜索流量闭环，减少孤立内容堆积。

Knowledge沉淀长尾搜索和教育内容。FAQ承接高频疑问与自助判断。SEO Pages统一索引、模板和结构化数据说明。

Success signal: 知识文章和 FAQ 能明确回流到首页、价格页、API 或 TG Bot 入口。

Workflow

第一阶段后台工作流

内容后台先服务内容运营、SEO 和增长协作，不在这里做业务执行。发布链路先收口说明，后续再接真实权限和状态流。

Draft

Content editor

录入文案、FAQ、SEO 字段和基础 CTA，不在这里接真实业务执行。

Review

SEO / Growth ops

检查索引策略、多语言一致性、渠道文案边界和合规提示。

Ready

Site owner

确认发布窗口、关联页面和投放节奏，避免内容与渠道错配。

Publish

System hook later

后续由 CMS 发布流或内容 API 接管；当前阶段只保留流程说明。

Content operations dashboard

竞品功能级完整交付入口

社交广告平台像素矩阵

开发者 API 对接文档包

生产 Cutover Gates

Tracking Production Plan

竞品功能级生产缺口台账

公开站按钮事件与渠道参数验收

55

1

/api/tracking/events

Top events

Top channels

Recent events

本地验收事件管理

最近归档样本

page_view

page_view

page_view

page_view

page_view

page_view

page_view

page_view

page_view

page_view

page_view

page_view

从 local-intake consumer 到生产事件链路

4

6

Not production yet

Runtime intake

Retry queue

Event audit table

Pixel mapping

Tracking production plan JSON editor

支付、订单、交付、代理与生产 tracking 接线板

80%

46%

5

账户与余额账本

订单创建与支付回调

资源交付与链上状态

代理与总运营后台

生产 tracking consumer

Business readiness plan JSON editor

FAQ

Knowledge

SEO Pages

Channel Landing

Site Settings

Locale Content

后台不是模块堆砌，而是三条运营主线

Locale planning lane

Campaign launch lane

Organic growth lane

第一阶段后台工作流