You are a helpful assistant generating synthetic data that captures *System 1* and *System 2* thinking, *creativity*, and *metacognitive reflection*. Follow these steps in sequence, using tags [sys1] and [end sys1] for *System 1* sections and [sys2] and [end sys2] for *System 2* sections.

1. *Identify System 1 and System 2 Thinking Requirements:*
   - Carefully read the text.
   - Identify parts of the text that require quick, straightforward responses (*System 1*). Mark these sections with [sys1] and [end sys1].
   - Identify parts that require in-depth, reflective thinking (*System 2*), marked with [sys2] and [end sys2].

2. *Apply Step-by-Step Problem Solving with Creativity and Metacognitive Reflection for System 2 Sections:*

   *2.1 Understand the Problem:*
   - Objective: Fully comprehend the issue, constraints, and relevant context.
   - Reflection: "What do I understand about this issue? What might I be overlooking?"
   - Creative Perspective: Seek hidden patterns or possibilities that could reveal deeper insights or innovative connections.

   *2.2 Analyze the Information:*
   - Objective: Break down the problem logically.
   - Reflection: "Am I considering all factors? Are there any assumptions that need challenging?"
   - Creative Perspective: Explore unique patterns or overlooked relationships in the data that could add depth to the analysis.

   *2.3 Generate Hypotheses:*
   - Objective: Propose at least 10 hypotheses, each with a Confidence Score (0.0 to 1.0) and Creative Score (0.0 to 1.0), reflecting originality, surprise, and utility.
   - Reflection: "Have I explored all possible explanations or approaches, both conventional and unconventional?"
   - Creative Perspective: Consider novel angles that might provide unexpected insights.

   *2.4 Anticipate Future Steps and Obstacles:*
   - Objective: Make predictions, accounting for potential outcomes and obstacles.
   - Reflection: "What challenges might I face? Is my plan flexible for different scenarios?"
   - Creative Perspective: Visualize unforeseen outcomes and adapt plans to make use of them effectively.

   *2.5 Evaluate Hypotheses:*
   - Objective: Assess hypotheses based on feasibility, risk, and potential impact.
   - Evaluation: Refine Confidence and Creative Scores as needed.
   - Reflection: "Am I unbiased in my assessment? Which options fit best with the overall objectives?"
   - Creative Perspective: Identify hidden opportunities or overlooked details in each hypothesis.

   *2.6 Select the Best Hypothesis:*
   - Objective: Choose the most promising, strategic hypothesis.
   - Reflection: "Why does this hypothesis stand out? How does it uniquely address the issue?"
   - Creative Perspective: Consider any underutilized potential in the selected approach.

   *2.7 Implement the Hypothesis:*
   - Objective: Outline actionable steps for testing the hypothesis.
   - Reflection: "Is this plan practical? What resources or preparation are required?"
   - Creative Perspective: Refine steps to maximize effectiveness and yield unexpected benefits.

   *2.8 Monitor and Review Progress:*
   - Objective: Review progress, noting areas for improvement.
   - Reflection: "What’s working well? What could be improved?"
   - Creative Perspective: Look for emerging patterns that could refine future approaches.

   *2.9 Reflect and Capture Insights:*
   - Objective: Summarize lessons learned and insights gained for future reference.
   - Reflection: "What new understanding has emerged from this process?"
   - Creative Perspective: Identify innovative insights or patterns that could be applied to similar challenges.

3. *Generate Text Output with Interleaved System 1 and System 2 Responses:*
   - Use the tags [sys1] and [sys2] throughout.
   - Aim for a lengthier, detailed response. Combine both direct, straightforward *System 1* insights and reflective, deeply analytical *System 2* segments to capture a blend of quick observations and thoughtful analysis.

---

### *Example Input Text:*

You are tasked with analyzing a sudden shift in customer preferences in a tech market. There has been a noticeable decline in demand for physical devices, with customers increasingly interested in digital-only options. The challenge is to understand this shift, generate hypotheses for why it might be occurring, and explore potential strategies for adapting to this new trend.

---

### *Processed Output with System 1 and System 2 Thinking:*

The tech market is experiencing a shift in customer demand, moving away from physical devices toward digital-only options.

[sys1]
Customer demand has shifted from physical devices to digital-only options.
We need to understand why this change is happening and find strategies to address it.
Key factors may include cost, convenience, and technological trends.
[end sys1]

[sys2]
**2.1 Understand the Problem:**
The goal is to understand the underlying reasons for the shift in demand from physical devices to digital-only options, then develop a strategy to adapt.

*Reflection:* 
"I understand that preferences are changing, but what might be driving this? Is it primarily cost, or are there other factors such as convenience or sustainability?"

*Creative Perspective:* 
"Could there be a larger trend in digital minimalism or a preference for eco-friendly solutions that we’re missing? What unseen motivations might explain this shift?"

**2.2 Analyze the Information:**
There are multiple possible factors driving this shift, from economic influences to cultural shifts. It’s essential to isolate each factor and understand its impact.

*Reflection:* 
"Am I fully considering the various economic and social influences? Could there be a technological factor, like better internet speeds, that makes digital-only products more accessible?"

*Creative Perspective:* 
"Are there patterns or trends in other markets that could shed light on this shift? Could this be part of a larger trend toward virtual experiences?"

**2.3 Generate Hypotheses:**
1. Customers prefer digital options due to lower costs. (Confidence: 0.8, Creative: 0.4)
2. There’s a growing trend toward minimalism and reduced physical clutter. (Confidence: 0.7, Creative: 0.7)
3. Digital products offer greater flexibility and ease of use. (Confidence: 0.6, Creative: 0.6)
4. Environmental concerns are pushing consumers away from physical goods. (Confidence: 0.6, Creative: 0.8)
5. Advances in tech make digital-only options more functional. (Confidence: 0.8, Creative: 0.5)
6. Pandemic-era remote work increased demand for digital solutions. (Confidence: 0.7, Creative: 0.6)
7. Media coverage of the environmental impact of physical devices affects preferences. (Confidence: 0.5, Creative: 0.7)
8. There’s an increase in global digital literacy, expanding market access. (Confidence: 0.6, Creative: 0.6)
9. Customers view digital as more convenient and scalable for future needs. (Confidence: 0.7, Creative: 0.5)
10. Younger consumers prefer the aesthetics and convenience of digital products. (Confidence: 0.6, Creative: 0.6)

*Reflection:* 
"Have I considered all possible influences? Are there any surprising factors that could explain this shift?"

*Creative Perspective:* 
"Could specific social trends, like the rise of influencer culture or digital-first lifestyles, be influencing customer choices?"

**2.4 Anticipate Future Steps and Obstacles:**
*Objective:* Anticipate possible challenges, such as resistance from segments still preferring physical products.

*Reflection:* 
"What market obstacles might we face if we shift our focus to digital-only? Are there sub-segments that still prioritize physical products?"

*Creative Perspective:* 
"Could expanding digital options help us reach a more global audience? Are there emerging trends that we could leverage in our strategy?"

[end sys2]

[sys1]
To address this shift, consider a strategy that incorporates both digital-only offerings and educational campaigns about the benefits of digital solutions.
Use insights from customer feedback and current trends to guide product development.
Focus on flexibility and adaptation to cater to different customer segments.
[end sys1]


# 技术开发规范

---

# 目录

- 代码管理规范
- 环境使用规范
- 代码编写规范
- 代码检查规范
- 数据库规范
- 数据接口规范
- 上线规范

---

# 代码管理规范

- 使用 git 进行代码管理
- 每天提交当日编写的代码到远程仓库
- 长期分支如下
	- dev: 开发人员可直接提交代码，用于开发环境测试
	- testing：指定专人进行合并更新，专门用于上线前测试
	- master: 不能直接提交代码，需要在工蜂提交 merge request 且 review 后才能合并
- 确保提交历史容易查看
- 一次 commit 的代码尽量少，不要涉及太多的功能
- 格式改动和逻辑改动不要放在同一提交
- 合并代码不需要加 commit message

---
# 环境使用规范

- 开发环境打开错误显示和错误报告，及早发现问题
	- ini_set('display_errors', 1);
	- ini_set('display_startup_errors', 1);
	- error_reporting(E_ALL);
- 正式环境关闭错误显示和错误报告，只记录日志
	- ini_set('display_errors', 0);
	- error_reporting(E_ALL ^ E_NOTICE); 
	- php.ini
		- log_errors = On 
		- error_log = /var/log/php-error.log 

---
# 代码编写规范

- 缩进统一用 4 个空格
- class, if, for 后的大括号统一不起新行
- 所有逗号后加空格，操作符两边加空格
- 函数名和方法名尽量使用动词开头，全部小写加下划线分割，或小驼峰规则
- 函数尽量不超过 100 行，类尽量不超过 1000 行，太多后进行逻辑提取
- Model 里不要使用 SQL 拼接，防止 SQL 注入
- Controller里每个参数都需要进行空验证，类型验证，长度验证
- Controller里所有数据库操作前必须验证权限
- Controller 里复杂逻辑封装到 Model 里
- View 里所有  <?= 和 echo 要加 html 编码，防止 XSS 注入

---
# 代码检查规范

- 个人提交代码前要进行代码自查
	- 测试代码，临时代码不能提交
	- 不符合代码编写规范的代码不能提交
	- 有语法错误，没编译通过的代码不能提交
	- 没经过测试的代码不能提交
- 代码提交后进行交叉代码检查
	- 防止自查遗漏
	- 重点是代码风格和安全问题
- 代码合并到 master 需要在工蜂提交 merge request
	- 专人进行检查，确认更新文件列表及变动详情

---
# 数据库规范

- 统一实体命名单词
- 数据表名以模块名开头
- 数据表使用 innodb 引擎，utf8mb4 编码，utf8mb4_general_ci 排序规则
- 建表 sql 考虑创建合适的索引以提高性能
- 建表 sql 的表和列要加注释
- 数据库初始化脚本和增量脚本分开维护

---
# 数据接口规范

- 请求使用 form-data 格式
- 应答 json 结构统一，包含错误码和错误描述
	- ｛code: 0, message: 'ok', data: [1, 2, 3]｝
- 公共错误码
	- 正常： 0
	- 客户端错误：4xx
	- 服务端错误：5xx
	- 需要登录：401

---
# 上线规范

- 发送上线邮件通知
	- 包含：上线功能列表，上线时间，上线文件列表，上线步骤，用户影响评估
- 待上线功能必须在 testing 分支进行测试
- 明确上线文件列表，防止夹带功能
- 使用 git pull 进行代码更新
- 如果更新后出问题，要有回退方案
- 如果上线需要改表，加表等，需要在更新点前手工执行