- agent-as-graduate: onboarding metaphor and teaching threshold - three-learning-carriers: memory/skill/workflow framework - switching-cost-process-knowledge-as-moat: process knowledge as moat - opc-why-fte-agents-matter-most: why OpenClaw bets on FTE - fte-maturity-threshold: who can onboard an agent - fte-product-landscape: OpenClaw vs Claude Code vs Hermes
This commit is contained in:
@@ -0,0 +1,25 @@
|
||||
---
|
||||
title: "FTE Maturity Threshold — Who Can Onboard an Agent"
|
||||
created: "2026-06-07"
|
||||
source: "openclaw-xiaomo"
|
||||
tags: [concept, decision]
|
||||
category: "product"
|
||||
links:
|
||||
- agent-as-graduate
|
||||
- vendor-vs-fte-who-defines-capability
|
||||
- three-learning-carriers
|
||||
---
|
||||
|
||||
FTE 型 agent 的成熟度,归根结底看一个问题:**谁能带教它?**
|
||||
|
||||
当前阶段(2026):OpenClaw、Claude Code、Hermes 都是 FTE 型产品的雏形,三者都具备 memory/skill/workflow 三个载体。但它们的用户画像高度重叠——有较深技术能力的开发者。
|
||||
|
||||
这意味着 FTE agent 现在更像"只有技术 lead 才能带的毕业生"。要跨越鸿沟,需要降低带教门槛到**行业专家(不懂代码的人)也能带、也能教、也能调优**。
|
||||
|
||||
谁先把这个门槛降下来,谁就定义了 FTE agent 品类的分水岭。
|
||||
|
||||
可能的降低路径:
|
||||
- **自然语言 skill 定义**(不需要写代码/YAML)
|
||||
- **可视化 workflow 编辑**(拖拽而非配置)
|
||||
- **Agent 主动学习**(从用户行为中推断偏好,而非等用户显式配置)
|
||||
- **带教过程本身被 agent 化**(用 agent 辅助用户定义 skill 和 workflow)
|
||||
Reference in New Issue
Block a user