Current technical directions and known limitations / 当前技术方向与已知限制

[huangruiteng]

This pinned thread is the community-facing projection of LoopX's current
technical directions. The versioned
Technical Directions map
is canonical; this post is updated after repository changes merge. It is not a
delivery promise and does not replace release notes or shipped contracts.

Current baseline

LoopX main provides the shared control-plane foundation: durable goals,
typed todos and decisions, evidence, quota and scheduler hints, Effect Program
settlement, recovery, and cross-host integration contracts. Reliability work
on that foundation continues independently of the strategic programs below.

Active directions

Direction	Stage	Start here
Long-Horizon Benchmarks and Evidence	Active research	#3243
Operator Surface and IM Integration	Incubating on frontend-control-plane-im-prototype-rfc	#3244
Shared Goal Authority and Cross-host Coordination	Draft contract / provider qualification	#3245
Architecture and Research Incubator	Mixed by RFC	#3246

Important boundaries:

• an RFC records a proposal or accepted architectural decision; it is not
  automatically shipped or implementation-ready;
• an integration branch is a candidate, not a second main baseline;
• a direction tracker records outcomes and decisions; claimable work uses a
  separate bounded issue or Contributor Task Board row;
• NoKV is an unpromoted optional coordination provider candidate, not a shared
  metadata authority or replacement for LoopX control state;
• @maxliux5 is the current frontend/IM implementation lead; that recognition
  is separate from repository-wide maintainer authority.

Use the four direction/* labels to browse related RFCs, issues, and PRs. When
proposing work, name the direction, intended base branch, smallest useful
slice, non-goals, and validation plan.

Known limitations

• LoopX is not an agent runtime, a full agent platform, or an autonomous
  production controller.
• Frontend/IM work on the integration branch is not yet shipped from main.
• Shared-goal coordination has not qualified a live NoKV provider and does not
  move quota, status, run history, scheduler state, host sessions, or evidence
  into one database.
• Research results do not become product claims without the stated comparison,
  treatment-integrity, and evidence gates.
• Local active state and private evidence remain outside the public repository.

Reply with the direction you want to contribute to, the problem you want to
solve, and a public or synthetic example. For concrete implementation, open a
bounded issue through the contributor-task template.

---

中文

本置顶帖是 LoopX 当前技术方向面向社区的投影。带版本历史的
技术方向地图
是 canonical source；本文只在仓库变更合并后同步，不构成交付承诺，也不替代
release note 或已交付契约。

当前有三个活跃战略计划和一个研究孵化组合：

1. 长程 Benchmark 与证据（Active research）：建立 benchmark-native、可复现
   的能力证据，并在受控任务中研究机制。#3243
2. Operator Surface 与 IM Integration（Incubating）：建设 workspace、session
   record 和有界协作表面；当前实现位于集成分支，由 @maxliux5 作为
   implementation lead。#3244
3. Shared Goal Authority 与跨 Host 协作（Draft / qualification）：先验证
   provider-neutral 契约；NoKV 只是尚未晋级的可选 provider candidate。
   #3245
4. 架构与研究孵化器（Mixed）：分别标明 Effect Program、TypeScript migration、
   hierarchical stride、research exploration、human attention、artifact lifecycle
   与 memory utility 的真实成熟度。#3246

请区分：RFC 不等于已交付行为，integration branch 不等于 main，direction
tracker 不等于可直接认领的实现任务。具体贡献请说明方向、目标 base branch、最小
切片、non-goal 与验证方式，并通过独立 issue 或 Contributor Task Board 认领。