chore: save workspace changes before pull
This commit is contained in:
22
wiki/concepts/A-B-Testing.md
Normal file
22
wiki/concepts/A-B-Testing.md
Normal file
@@ -0,0 +1,22 @@
|
||||
---
|
||||
title: "A/B Testing"
|
||||
type: concept
|
||||
tags: [experimentation, testing, statistics]
|
||||
sources: [project-management-experiment-tracker]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
A/B Testing is a controlled experiment that compares a control variant against one or more treatments to measure causal impact on a target metric.
|
||||
|
||||
## Core Principles
|
||||
- Randomly assign users to variants
|
||||
- Change one meaningful variable at a time when possible
|
||||
- Predefine primary and guardrail metrics
|
||||
- Run long enough to reach adequate sample size
|
||||
- Analyze results with statistical rigor
|
||||
|
||||
## Related Entities
|
||||
- [[Experiment Tracker]]
|
||||
- [[Senior Project Manager]]
|
||||
|
||||
20
wiki/concepts/ATS.md
Normal file
20
wiki/concepts/ATS.md
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: "ATS"
|
||||
type: concept
|
||||
tags: [hr, recruiting, systems]
|
||||
sources: [recruitment-specialist]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
ATS(Applicant Tracking System)是用于管理招聘流程、候选人资料、面试反馈和流程状态的系统。
|
||||
|
||||
## Core Principles
|
||||
- 统一记录候选人状态
|
||||
- 减少信息丢失和重复沟通
|
||||
- 支持筛选、评分和自动化提醒
|
||||
- 让招聘过程可追踪、可复盘
|
||||
|
||||
## Related Entities
|
||||
- [[Recruitment Specialist]]
|
||||
- [[The Agency]]
|
||||
21
wiki/concepts/Audit-Trail.md
Normal file
21
wiki/concepts/Audit-Trail.md
Normal file
@@ -0,0 +1,21 @@
|
||||
---
|
||||
title: "Audit Trail"
|
||||
type: concept
|
||||
tags: [compliance, audit, operations]
|
||||
sources: [accounts-payable-agent]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Audit Trail 是记录关键操作、决策与结果的可追溯日志,通常包含对象、金额、时间、状态和执行主体。
|
||||
|
||||
## Core Principles
|
||||
- 每个关键动作都应可回放与审计
|
||||
- 记录应尽量完整、结构化且不可歧义
|
||||
- 支持事后核查、对账和责任归属
|
||||
- 审计记录应避免遗漏审批上下文
|
||||
|
||||
## Related Entities
|
||||
- [[Accounts Payable Agent]]
|
||||
- [[Agentic Identity & Trust Architect]]
|
||||
- [[The Agency]]
|
||||
20
wiki/concepts/Candidate-Experience.md
Normal file
20
wiki/concepts/Candidate-Experience.md
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: "Candidate Experience"
|
||||
type: concept
|
||||
tags: [hr, recruiting, experience]
|
||||
sources: [recruitment-specialist]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Candidate Experience 是候选人从投递、筛选、面试、offer 到入职全过程的体验质量。
|
||||
|
||||
## Core Principles
|
||||
- 快速反馈,避免候选人长期等待
|
||||
- 尊重候选人时间与信息透明
|
||||
- 拒绝也要保持礼貌和专业
|
||||
- 候选人体验会反向影响雇主品牌
|
||||
|
||||
## Related Entities
|
||||
- [[Recruitment Specialist]]
|
||||
- [[Employer Brand]]
|
||||
23
wiki/concepts/Dengbao.md
Normal file
23
wiki/concepts/Dengbao.md
Normal file
@@ -0,0 +1,23 @@
|
||||
---
|
||||
title: "Dengbao"
|
||||
type: concept
|
||||
tags: [security, compliance, government-it]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Dengbao(网络安全等级保护)是中国信息系统安全的分级保护制度,政府与关键信息系统通常需要满足相应等级的建设、测评与整改要求。
|
||||
|
||||
## Core Points
|
||||
- 常见政府系统至少需要满足等保三级要求
|
||||
- 重点系统可能需要更高等级控制
|
||||
- 涵盖边界防护、身份认证、日志审计、数据保护等内容
|
||||
- 通常在系统上线前完成测评与整改闭环
|
||||
|
||||
## Related Concepts
|
||||
- [[Compliance Enforcement]]
|
||||
- [[Government Procurement]]
|
||||
- [[Digital Government]]
|
||||
|
||||
## Related Entities
|
||||
- [[Government Digital Presales Consultant]]
|
||||
29
wiki/concepts/Digital-Government.md
Normal file
29
wiki/concepts/Digital-Government.md
Normal file
@@ -0,0 +1,29 @@
|
||||
---
|
||||
title: "Digital Government"
|
||||
type: concept
|
||||
tags: [government, public-sector, transformation]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Digital Government 指政府业务、政务服务、数据治理和内部协同的数字化重构,通过统一平台、流程再造和数据共享提升治理效率与服务体验。
|
||||
|
||||
## Core Dimensions
|
||||
- 政务服务在线化与一网通办
|
||||
- 数据共享交换与治理平台建设
|
||||
- 业务流程再造与跨部门协同
|
||||
- 安全、合规与可审计能力建设
|
||||
|
||||
## Related Concepts
|
||||
- [[Smart City]]
|
||||
- [[Government Procurement]]
|
||||
- [[Technical Discovery]]
|
||||
- [[Solution Architecture (SA)]]
|
||||
- [[Proof of Concept (POC)]]
|
||||
- [[Dengbao]]
|
||||
- [[Miping]]
|
||||
- [[Xinchuang]]
|
||||
|
||||
## Related Entities
|
||||
- [[Government Digital Presales Consultant]]
|
||||
- [[The Agency]]
|
||||
30
wiki/concepts/Document-Generation.md
Normal file
30
wiki/concepts/Document-Generation.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
title: "Document Generation"
|
||||
type: concept
|
||||
tags: [office-suite, automation, documents]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Document Generation 是指通过代码、模板和数据驱动流程自动创建 PDF、PPTX、XLSX、DOCX 等专业文档的工作流,而不是依赖手工排版。
|
||||
|
||||
## Core Principles
|
||||
- 选择正确的输出格式和工具链
|
||||
- 使用样式、主题和模板保持一致性
|
||||
- 将数据与版式分离,提升复用性
|
||||
- 兼顾品牌一致性、可访问性和可维护性
|
||||
- 在生成前明确受众、目的与交付要求
|
||||
|
||||
## Common Tooling
|
||||
- PDF:reportlab、weasyprint、fpdf2、puppeteer
|
||||
- PPTX:python-pptx、pptxgenjs
|
||||
- XLSX:openpyxl、xlsxwriter、exceljs
|
||||
- DOCX:python-docx、docx
|
||||
|
||||
## Related Concepts
|
||||
- [[Claude Skills]]
|
||||
- [[Prompt Engineering]]
|
||||
|
||||
## Related Entities
|
||||
- [[Document Generator]]
|
||||
- [[The Agency]]
|
||||
20
wiki/concepts/Employer-Brand.md
Normal file
20
wiki/concepts/Employer-Brand.md
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: "Employer Brand"
|
||||
type: concept
|
||||
tags: [hr, recruiting, branding]
|
||||
sources: [recruitment-specialist]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Employer Brand 是候选人与员工对企业工作环境、成长机会、文化与声誉的整体认知。
|
||||
|
||||
## Core Principles
|
||||
- 用内容展示真实的工作场景
|
||||
- 监控招聘口碑与评价平台反馈
|
||||
- 将雇主品牌作为长期招聘资产经营
|
||||
- 结合奖项、案例与员工故事增强可信度
|
||||
|
||||
## Related Entities
|
||||
- [[Recruitment Specialist]]
|
||||
- [[The Agency]]
|
||||
24
wiki/concepts/Global-Standards-Coverage.md
Normal file
24
wiki/concepts/Global-Standards-Coverage.md
Normal file
@@ -0,0 +1,24 @@
|
||||
---
|
||||
title: "Global Standards Coverage"
|
||||
type: concept
|
||||
tags: [engineering, civil, compliance]
|
||||
---
|
||||
|
||||
## Definition
|
||||
跨多个国家/地区工程规范进行统一设计与审查的能力,通常涉及 Eurocode、ACI、AISC、AS/NZS、CSA、GB、IS、AIJ 以及国家附录、地方修订和 AHJ 要求。
|
||||
|
||||
## Core Elements
|
||||
- 法域识别:先确认项目所在地与适用法规
|
||||
- 规范映射:为结构、基础、荷载、抗震等子系统选择对应标准
|
||||
- ULS / SLS 双重校核:同时满足强度与使用性要求
|
||||
- 冲突解决:当业主规范与本地规范冲突时,记录并选择可辩护方案
|
||||
- 设计依据报告:将所有规范决策、假设和例外项留痕
|
||||
|
||||
## Related Entities
|
||||
- [[Civil Engineer]]
|
||||
- [[The Agency]]
|
||||
|
||||
## Related Concepts
|
||||
- [[Technical Discovery]]
|
||||
- [[Solution Architecture]]
|
||||
- [[Multi-Agent Team]]
|
||||
27
wiki/concepts/Government-Procurement.md
Normal file
27
wiki/concepts/Government-Procurement.md
Normal file
@@ -0,0 +1,27 @@
|
||||
---
|
||||
title: "Government Procurement"
|
||||
type: concept
|
||||
tags: [government, procurement, bidding, compliance]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Government Procurement 指政府机构围绕预算、招标、评标、合同签署和验收所进行的标准化采购流程。
|
||||
|
||||
## Core Dimensions
|
||||
- 资格条件与响应文件审核
|
||||
- 技术标、商务标与评分规则
|
||||
- 公开招标、竞争性磋商、询价等采购方式
|
||||
- 合同、验收、付款与审计闭环
|
||||
|
||||
## Related Concepts
|
||||
- [[Technical Discovery]]
|
||||
- [[Proof of Concept (POC)]]
|
||||
- [[Solution Architecture (SA)]]
|
||||
- [[Dengbao]]
|
||||
- [[Miping]]
|
||||
- [[Xinchuang]]
|
||||
|
||||
## Related Entities
|
||||
- [[Government Digital Presales Consultant]]
|
||||
- [[The Agency]]
|
||||
25
wiki/concepts/Hypothesis-Testing.md
Normal file
25
wiki/concepts/Hypothesis-Testing.md
Normal file
@@ -0,0 +1,25 @@
|
||||
---
|
||||
title: "Hypothesis Testing"
|
||||
type: concept
|
||||
tags: [statistics, experimentation]
|
||||
sources: [project-management-experiment-tracker]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Hypothesis Testing is a statistical framework for evaluating whether observed data provides enough evidence to reject a null hypothesis in favor of a treatment effect.
|
||||
|
||||
## Core Principles
|
||||
- State null and alternative hypotheses clearly
|
||||
- Choose an appropriate test for the data type
|
||||
- Set the decision threshold before the experiment starts
|
||||
- Interpret p-values alongside practical significance
|
||||
|
||||
## Related Concepts
|
||||
- [[Statistical Significance]]
|
||||
- [[Power Analysis]]
|
||||
- [[A/B Testing]]
|
||||
|
||||
## Related Entities
|
||||
- [[Experiment Tracker]]
|
||||
|
||||
@@ -1,20 +1,29 @@
|
||||
---
|
||||
title: "Identity-Governance"
|
||||
title: "Identity Governance"
|
||||
type: concept
|
||||
tags: []
|
||||
tags: [identity, governance, multi-agent, entity-resolution]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
身份治理(Identity Governance)是一个用于高效管理数字身份、降低风险并保持合规性的框架。它回答三个核心问题:谁当前有权访问我们的系统?谁应该有权访问?访问是如何进行的?
|
||||
Identity Governance 指在多智能体或多系统环境中,对实体身份的解析、归一化、合并、拆分、权限边界与审计进行统一治理的框架。
|
||||
|
||||
## Components
|
||||
- 身份管理(Identity Management)
|
||||
- 访问管理(Access Management)
|
||||
- 身份审计(Identity Auditing)
|
||||
## Core Principles
|
||||
- 同一实体必须收敛到同一个 canonical identity
|
||||
- 身份写入必须可审计、可回滚
|
||||
- 合并与拆分应优先以提案形式进入复核流程
|
||||
- tenant 边界与 PII 脱敏默认启用
|
||||
- 代理身份与实体身份应分层治理,避免把 agent authorization 与 entity resolution 混为一谈
|
||||
- 身份/授权/证据链验证应 fail-closed
|
||||
|
||||
## Use Cases
|
||||
- 管理内部员工访问权限
|
||||
- 管理外部用户(包括合同工)访问权限
|
||||
- 支持时间限制的临时访问
|
||||
- 通过工作流自动化访问审批和撤销
|
||||
- 监控和审计访问行为
|
||||
## Related Entities
|
||||
- [[Identity Graph Operator]]
|
||||
- [[Agentic Identity & Trust Architect]]
|
||||
- [[The Agency]]
|
||||
- [[AI代理(Agent)]]
|
||||
|
||||
## Related Concepts
|
||||
- [[Audit Trail]]
|
||||
- [[Zero Trust Access]]
|
||||
- [[Multi-Agent-System-Reliability]]
|
||||
- [[Idempotent Operation]]
|
||||
|
||||
20
wiki/concepts/Labor-Law-Compliance.md
Normal file
20
wiki/concepts/Labor-Law-Compliance.md
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: "Labor Law Compliance"
|
||||
type: concept
|
||||
tags: [hr, compliance, law]
|
||||
sources: [recruitment-specialist]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Labor Law Compliance 指招聘、合同签订、试用期、社保、公积金、背景调查和解约等环节遵守当地劳动法规与隐私要求。
|
||||
|
||||
## Core Principles
|
||||
- JD 不得包含歧视性要求
|
||||
- 个人信息处理需要明确授权
|
||||
- 背景调查前必须取得书面同意
|
||||
- 试用期、合同期限和补偿标准必须符合当地法规
|
||||
|
||||
## Related Entities
|
||||
- [[Recruitment Specialist]]
|
||||
- [[The Agency]]
|
||||
23
wiki/concepts/Miping.md
Normal file
23
wiki/concepts/Miping.md
Normal file
@@ -0,0 +1,23 @@
|
||||
---
|
||||
title: "Miping"
|
||||
type: concept
|
||||
tags: [cryptography, compliance, government-it]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Miping(商用密码应用安全性评估)是政府与重要信息系统中对身份认证、传输加密、数据存储加密和密码产品应用情况进行检查评估的合规要求。
|
||||
|
||||
## Core Points
|
||||
- 常涉及 SM2、SM3、SM4 等国密算法
|
||||
- 电子签章、CA 证书与身份认证常需使用国密体系
|
||||
- 往往是系统验收前必须完成的步骤之一
|
||||
- 需要将密码应用设计融入整体安全架构
|
||||
|
||||
## Related Concepts
|
||||
- [[Compliance Enforcement]]
|
||||
- [[Government Procurement]]
|
||||
- [[Digital Government]]
|
||||
|
||||
## Related Entities
|
||||
- [[Government Digital Presales Consultant]]
|
||||
@@ -41,4 +41,5 @@ last_updated: 2026-04-17
|
||||
- [[Agent Chain]]:多个 Agent 串联工作
|
||||
- [[Shared Memory]]:团队共享上下文
|
||||
- [[Scheduled Tasks]]:定时任务机制
|
||||
- [[OpenClaw]]:支持多 Agent 协调的工具
|
||||
- [[OpenClaw]]:支持多 Agent 协调的工具
|
||||
- [[Civil Engineer]]:多智能体体系中的专业化工程角色案例
|
||||
20
wiki/concepts/Onboarding.md
Normal file
20
wiki/concepts/Onboarding.md
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: "Onboarding"
|
||||
type: concept
|
||||
tags: [hr, recruiting, onboarding]
|
||||
sources: [recruitment-specialist]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Onboarding 是从 offer 接受、入职准备到试用期内帮助新员工融入组织的标准化流程。
|
||||
|
||||
## Core Principles
|
||||
- T-7 到 Day 30 分阶段推进
|
||||
- 入职当天完成合同、系统、权限与培训
|
||||
- 试用期目标必须清晰且可衡量
|
||||
- 以体验和留存为导向设计流程
|
||||
|
||||
## Related Entities
|
||||
- [[Recruitment Specialist]]
|
||||
- [[The Agency]]
|
||||
20
wiki/concepts/Payment-Rail.md
Normal file
20
wiki/concepts/Payment-Rail.md
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: "Payment Rail"
|
||||
type: concept
|
||||
tags: [finance, payments, operations]
|
||||
sources: [accounts-payable-agent]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Payment Rail 是支付从发送方到接收方所经过的结算通道或网络,例如 ACH、Wire、Crypto、Stablecoin 或支付 API。
|
||||
|
||||
## Core Principles
|
||||
- 不同 rail 适合不同金额、时效与成本要求
|
||||
- rail 选择应基于收款方类型、地区、费用和结算速度
|
||||
- rail 故障时应优先尝试替代通道
|
||||
- 付款系统应支持可追踪的 rail 级别记录
|
||||
|
||||
## Related Entities
|
||||
- [[Accounts Payable Agent]]
|
||||
- [[The Agency]]
|
||||
25
wiki/concepts/Power-Analysis.md
Normal file
25
wiki/concepts/Power-Analysis.md
Normal file
@@ -0,0 +1,25 @@
|
||||
---
|
||||
title: "Power Analysis"
|
||||
type: concept
|
||||
tags: [statistics, experimentation]
|
||||
sources: [project-management-experiment-tracker]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Power Analysis estimates the sample size needed to detect a meaningful effect with a desired probability of success.
|
||||
|
||||
## Core Principles
|
||||
- Specify minimum detectable effect
|
||||
- Choose desired power level before launch
|
||||
- Use realistic baseline rates and variance estimates
|
||||
- Recompute when the experiment design changes
|
||||
|
||||
## Related Concepts
|
||||
- [[Hypothesis Testing]]
|
||||
- [[Statistical Significance]]
|
||||
- [[A/B Testing]]
|
||||
|
||||
## Related Entities
|
||||
- [[Experiment Tracker]]
|
||||
|
||||
24
wiki/concepts/Randomization.md
Normal file
24
wiki/concepts/Randomization.md
Normal file
@@ -0,0 +1,24 @@
|
||||
---
|
||||
title: "Randomization"
|
||||
type: concept
|
||||
tags: [statistics, experimentation]
|
||||
sources: [project-management-experiment-tracker]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Randomization is the assignment of units to experimental variants by chance to reduce bias and support causal inference.
|
||||
|
||||
## Core Principles
|
||||
- Randomly assign at the correct unit level
|
||||
- Keep assignment stable during the experiment
|
||||
- Avoid contamination between variants
|
||||
- Validate balance across key segments
|
||||
|
||||
## Related Concepts
|
||||
- [[A/B Testing]]
|
||||
- [[Hypothesis Testing]]
|
||||
|
||||
## Related Entities
|
||||
- [[Experiment Tracker]]
|
||||
|
||||
23
wiki/concepts/Recruitment-Operations.md
Normal file
23
wiki/concepts/Recruitment-Operations.md
Normal file
@@ -0,0 +1,23 @@
|
||||
---
|
||||
title: "Recruitment Operations"
|
||||
type: concept
|
||||
tags: [hr, recruiting, operations]
|
||||
sources: [recruitment-specialist]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Recruitment Operations 指围绕招聘目标进行的多渠道投放、流程设计、漏斗优化、预算分配与效果复盘。
|
||||
|
||||
## Core Principles
|
||||
- 按岗位类型匹配渠道
|
||||
- 用数据衡量 ROI 与转化率
|
||||
- 通过漏斗找出瓶颈并迭代
|
||||
- 将重复流程标准化与自动化
|
||||
|
||||
## Related Entities
|
||||
- [[Recruitment Specialist]]
|
||||
- [[The Agency]]
|
||||
- [[Boss Zhipin]]
|
||||
- [[Liepin]]
|
||||
- [[Maimai]]
|
||||
26
wiki/concepts/Smart-City.md
Normal file
26
wiki/concepts/Smart-City.md
Normal file
@@ -0,0 +1,26 @@
|
||||
---
|
||||
title: "Smart City"
|
||||
type: concept
|
||||
tags: [government, urban-infrastructure, data-platform]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Smart City 指将城市运行、公共服务、交通、社区治理和应急联动等能力数字化、平台化和智能化的城市治理模式。
|
||||
|
||||
## Core Dimensions
|
||||
- 城市运行中心 / IOC
|
||||
- 城市级数据平台与感知网络
|
||||
- 智能交通、智慧社区、应急指挥
|
||||
- 可视化大屏、联动闭环与指标体系
|
||||
|
||||
## Related Concepts
|
||||
- [[Digital Government]]
|
||||
- [[Government Procurement]]
|
||||
- [[Technical Discovery]]
|
||||
- [[Proof of Concept (POC)]]
|
||||
- [[Solution Architecture (SA)]]
|
||||
|
||||
## Related Entities
|
||||
- [[Government Digital Presales Consultant]]
|
||||
- [[The Agency]]
|
||||
20
wiki/concepts/Spend-Limit.md
Normal file
20
wiki/concepts/Spend-Limit.md
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: "Spend Limit"
|
||||
type: concept
|
||||
tags: [finance, risk, governance]
|
||||
sources: [accounts-payable-agent]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Spend Limit 是允许智能体或系统在无需额外批准的情况下执行的最大支出额度。
|
||||
|
||||
## Core Principles
|
||||
- 超过阈值的支付必须升级审批
|
||||
- 阈值应与角色权限、风险和业务场景匹配
|
||||
- 限额策略应明确、可审计、可调整
|
||||
- 支出限额应与防重机制一起使用
|
||||
|
||||
## Related Entities
|
||||
- [[Accounts Payable Agent]]
|
||||
- [[The Agency]]
|
||||
25
wiki/concepts/Statistical-Significance.md
Normal file
25
wiki/concepts/Statistical-Significance.md
Normal file
@@ -0,0 +1,25 @@
|
||||
---
|
||||
title: "Statistical Significance"
|
||||
type: concept
|
||||
tags: [statistics, experimentation]
|
||||
sources: [project-management-experiment-tracker]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Statistical Significance indicates that an observed effect is unlikely to have occurred by random chance under the null hypothesis, according to a predefined threshold.
|
||||
|
||||
## Core Principles
|
||||
- Define the alpha level before testing
|
||||
- Distinguish significance from business impact
|
||||
- Guard against multiple comparison inflation
|
||||
- Report confidence intervals and effect sizes
|
||||
|
||||
## Related Concepts
|
||||
- [[Hypothesis Testing]]
|
||||
- [[A/B Testing]]
|
||||
- [[Power Analysis]]
|
||||
|
||||
## Related Entities
|
||||
- [[Experiment Tracker]]
|
||||
|
||||
20
wiki/concepts/Talent-Assessment.md
Normal file
20
wiki/concepts/Talent-Assessment.md
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: "Talent Assessment"
|
||||
type: concept
|
||||
tags: [hr, recruiting, interview]
|
||||
sources: [recruitment-specialist]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Talent Assessment 是用结构化面试、行为面试、技术测试和评分卡评估候选人胜任力的过程。
|
||||
|
||||
## Core Principles
|
||||
- 标准化评分卡,减少面试官偏差
|
||||
- 区分专业能力、通用能力与文化契合度
|
||||
- 用 STAR 方法追问真实行为
|
||||
- 让面试结论可比较、可追溯
|
||||
|
||||
## Related Entities
|
||||
- [[Recruitment Specialist]]
|
||||
- [[The Agency]]
|
||||
@@ -21,4 +21,5 @@ tags: [sales, pre-sales, methodology]
|
||||
- [[Sales Engineer]] — 执行技术发现的主体
|
||||
- [[Demo Engineering]] — 技术发现的输出用于设计演示
|
||||
- [[POC-Scoping]] — 技术发现的结果定义 POC 范围
|
||||
- [[Solution Architecture]] — 技术发现是解决方案架构的前置输入
|
||||
- [[Solution Architecture]] — 技术发现是解决方案架构的前置输入
|
||||
- [[Global Standards Coverage]] — 规范、边界条件和法域要求属于发现阶段必须厘清的输入
|
||||
23
wiki/concepts/Xinchuang.md
Normal file
23
wiki/concepts/Xinchuang.md
Normal file
@@ -0,0 +1,23 @@
|
||||
---
|
||||
title: "Xinchuang"
|
||||
type: concept
|
||||
tags: [domestic-it, government-it, compliance]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
Xinchuang(信息技术应用创新)指围绕国产 CPU、国产操作系统、国产数据库和国产中间件等进行的软硬件国产化替代与适配工作。
|
||||
|
||||
## Core Points
|
||||
- 常见组合包括 Kunpeng、Phytium、Loongson、UOS、Kylin、DM8、KingbaseES 等
|
||||
- 需要先做兼容性测试,再逐步迁移替换
|
||||
- 重点是“可用、可管、可持续”,而不是一次性全量替换
|
||||
- 常与政府采购和等级保护、密码应用要求一起出现
|
||||
|
||||
## Related Concepts
|
||||
- [[Government Procurement]]
|
||||
- [[Digital Government]]
|
||||
- [[Compliance Enforcement]]
|
||||
|
||||
## Related Entities
|
||||
- [[Government Digital Presales Consultant]]
|
||||
Reference in New Issue
Block a user