huangruiteng · huangruiteng · Aug 16, 2026 · Aug 16, 2026
@@ -1,6 +1,8 @@
 # Repository governance files remain owned by the lead maintainer.
 /.github/CODEOWNERS @huangruiteng
 /.github/GOVERNANCE.md @huangruiteng
+/CONTRIBUTOR_TASKS.md @huangruiteng
+/docs/project/technical-directions*.md @huangruiteng
 
 # Lark integration review routing.
 /loopx/extensions/lark/** @huangruiteng @steven-kid

@@ -150,6 +150,35 @@ releases, and boundary decisions.
 - When consensus is not reached, the lead maintainer records the decision and
   rationale in the relevant issue or pull request.
 
+## Technical Direction Governance
+
+The versioned
+[Current Technical Directions](../docs/project/technical-directions.md) page is
+the canonical map of active strategic programs, maturity, contribution routes,
+and promotion gates. The pinned
+[GitHub Discussion](https://github.com/huangruiteng/loopx/discussions/2851) is
+its community-facing projection; an issue, Discussion, RFC, or integration
+branch does not override merged runtime and stable reference contracts.
+
+Each strategic direction has one long-lived tracking issue. Trackers record
+outcomes, boundaries, implementation leads, material decisions, and links to
+bounded work. They are not themselves blanket implementation authorization.
+A claimable change should have a separate issue or public task-board row with
+an explicit smallest slice, base branch, non-goals, and validation plan.
+
+A material change to a direction's stage, scope, implementation lead,
+integration branch, or promotion gate requires a pull request updating the
+canonical map. The RFC index and contributor task board should change in the
+same pull request when their routing changes. Maintainers update the pinned
+Discussion after merge and should not maintain an independent roadmap body
+there.
+
+The `direction/*` labels route discovery and review. They do not grant
+authority, promise delivery, or imply that a Draft or Research item is ready
+for implementation. Recognition as an implementation lead records current
+public work; it is separate from repository write access, subsystem maintainer
+appointment, and repository-wide maintainer authority.
+
 ## Becoming A Maintainer
 
 Maintainers are selected from contributors who have shown sustained technical

diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
@@ -12,3 +12,6 @@ contact_links:
   - name: Contributor task board
     url: https://github.com/huangruiteng/loopx/blob/main/CONTRIBUTOR_TASKS.md
     about: Start here for public, claimable work.
+  - name: Current technical directions
+    url: https://github.com/huangruiteng/loopx/blob/main/docs/project/technical-directions.md
+    about: Understand active programs, maturity, ownership boundaries, and promotion gates.
diff --git a/.github/ISSUE_TEMPLATE/contributor-task.yml b/.github/ISSUE_TEMPLATE/contributor-task.yml
@@ -13,6 +13,20 @@ body:
       label: Task ID or area
       description: Use the board ID if one exists, such as GH-C01, or a short area name.
       placeholder: "GH-C01 or area: docs"
+  - type: dropdown
+    id: direction
+    attributes:
+      label: Technical direction
+      description: Choose the closest current program. This routes discussion; it does not make a draft implementation-ready.
+      options:
+        - Core control-plane hardening
+        - Long-horizon benchmark evidence
+        - Operator surface and IM integration
+        - Shared Goal Authority and cross-host coordination
+        - Architecture and research incubator
+        - Unsure; maintainer triage needed
+    validations:
+      required: true
   - type: dropdown
     id: intent
     attributes:
@@ -44,6 +58,14 @@ body:
         - ...
     validations:
       required: true
+  - type: input
+    id: target_base
+    attributes:
+      label: Intended base branch
+      description: Usually main. Name an integration branch when the direction tracker requires one.
+      placeholder: "main or frontend-control-plane-im-prototype-rfc"
+    validations:
+      required: true
   - type: textarea
     id: files
     attributes:

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -35,6 +35,19 @@
 - [ ] Build, packaging, installer, or CI
 - [ ] Host or runtime integration
 
+## Technical Direction
+
+<!-- Select one. Direction labels route review; they do not imply maturity or merge authority. -->
+
+- [ ] Core control-plane hardening
+- [ ] Long-horizon benchmark evidence
+- [ ] Operator surface and IM integration
+- [ ] Shared Goal Authority and cross-host coordination
+- [ ] Architecture and research incubator
+
+- Target base branch:
+- Direction tracker or promotion unit:
+
 ## Boundary Checklist
 
 - [ ] I did not commit `.loopx/`, `.codex/goals/`, live `ACTIVE_GOAL_STATE.md`, credentials, private benchmark traces, verifier output, raw agent sessions, internal document links, or local machine paths.

diff --git a/.github/SUPPORT.md b/.github/SUPPORT.md
@@ -17,7 +17,10 @@ channels.
 
 Public contributor work belongs on the
 [Contributor Task Board](../CONTRIBUTOR_TASKS.md) or in the contributor-task
-issue form. Pull requests should follow
+issue form. The
+[Technical Directions map](../docs/project/technical-directions.md) explains
+which programs are active and what maturity or promotion gate applies. Pull
+requests should follow
 [`CONTRIBUTING.md`](../CONTRIBUTING.md).
 
 ## Official Publication Sources
@@ -26,7 +29,9 @@ issue form. Pull requests should follow
   authoritative source for published versions and release notes.
 - [GitHub Discussions: Announcements](https://github.com/huangruiteng/loopx/discussions/categories/announcements)
   is the authoritative source for project announcements that are not tied to
-  one release.
+  one release. The pinned
+  [Current technical directions and known limitations](https://github.com/huangruiteng/loopx/discussions/2851)
+  post is the community-facing projection of the versioned repository map.
 - [GitHub Security Advisories](https://github.com/huangruiteng/loopx/security/advisories)
   is the authoritative source for coordinated vulnerability disclosures.
 

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -5,8 +5,10 @@ contributions are small, reviewable, and tied to a public task or clear bug.
 
 ## Find Work
 
-Start with [CONTRIBUTOR_TASKS.md](CONTRIBUTOR_TASKS.md). It lists public work
-that is useful, claimable, and safe to discuss in the repository.
+Start with the [current technical directions](docs/project/technical-directions.md)
+to understand the active programs and their maturity, then use
+[CONTRIBUTOR_TASKS.md](CONTRIBUTOR_TASKS.md) to find public work that is useful,
+claimable, and safe to discuss in the repository.
 
 If you do not see a matching task:
 

diff --git a/CONTRIBUTOR_TASKS.md b/CONTRIBUTOR_TASKS.md
@@ -37,54 +37,37 @@ into a mirror of maintainer scratch state.
 5. If a task is `Maintainer-owned`, do not duplicate the work. Ask whether
    there is a public helper slice instead.
 
-## Project Development Direction
-
-LoopX is becoming a management surface for long-running agent work: the control
-plane owns verified state transitions, typed settlement, and public evidence,
-while operators and contributors interact through compact read models and
-bounded commands. Pick work that advances one of the directions below; avoid
-parallel abstractions or a second source of truth.
-
-1. **From control-plane library to management surface.** Make kernel objects
-   (work items, owners, decisions, evidence, budgets, risk, next actions)
-   legible through dashboards, global manager commands, and showcase
-   walkthroughs. Prefer synthetic, provider-neutral surfaces; public first
-   viewports stay maintainer-preview work.
-2. **Effect Program runtime maturity.** A shared typed Effect Program now
-   drives quota, Turn, task-lease, and todo-completion settlement, and the
-   turn driver is the second consumer of the settlement algebra. M7 parity
-   fixtures, a read-only journal lens, and a shared typed settlement
-   receipt-chain driver are shipped. The next milestone is negative coverage
-   on the shared driver (receipt-chain drift, replay identity) and a second
-   adapter consuming the same plan/receipt algebra. Only then may a shared
-   executor be extracted, and only if two adapters share execution ownership.
-3. **Verified state transitions.** "done" must mean verified, not claimed:
-   wire caller-approved `validation_command` into self-reported completion
-   (#3082), keep typed receipts for writeback and spend, and make replay
-   safe under lease fencing (#3074).
-4. **Operator observability.** Give operators per-goal token/cost/duration and
-   legible governance (who can act, who must approve, what was spent) from
-   existing compact projections (#3085); do not create a second ledger.
-5. **Contributor and operator experience.** Make first-run onboarding durable
-   (#3092), complete the canonical read-only global command set, keep CLI
-   output budget-aware and readable (#2881), and close the release docs
-   timeline gap.
-6. **Maintainability.** Keep hot modules bounded, ratchet debt low, and smokes
-   deterministic (no wall-clock oracles). Extract cohesive rule groups into
-   bounded modules; never into generic helper layers.
+## Current Technical Directions
 
-## Priority Queue
+The canonical [Technical Directions map](docs/project/technical-directions.md)
+explains outcomes, maturity, ownership boundaries, and promotion gates. This
+board lists bounded work; it does not redefine those directions.
 
-| Priority | Slice | Issue / PR | Status |
+| Direction | Current stage | Contributor entry | Boundary |
 | --- | --- | --- | --- |
-| P0 | Wire caller-approved `validation_command` into the remaining self-report entry points | #3082 | Available |
-| P0 | Typed settlement receipt-chain negatives on the shared driver; Turn fencing review still open | #3074, #3199 | Available |
-| P1 | Security-boundary mutation coverage beyond the shipped negative fixtures | #3137-#3140 | Available |
-| P1 | Codex CLI timeout recovery cannot resume the session observed by the failed Turn | #3228 | Available |
-| P1 | Per-goal token/cost/duration dashboard projection | #3085 | Needs design |
-| P1 | One budget-aware CLI output ergonomics slice | #2881 | Needs design |
-| P2 | Release docs timeline v0.2.6 -> v0.4.7 | GH-C04 | Available |
-| P2 | CLI ownership and hot-module extraction | GH-C06 | Available |
+| Long-Horizon Benchmarks and Evidence | Active research | [#3243](https://github.com/huangruiteng/loopx/issues/3243) | Work on public-safe fixtures, treatment integrity, reducers, and docs; live cases and scoring remain maintainer-owned. |
+| Operator Surface and IM Integration | Incubating on `frontend-control-plane-im-prototype-rfc` | [#3244](https://github.com/huangruiteng/loopx/issues/3244) | State the target base branch; UI remains a projection and promotion to `main` is staged. |
+| Shared Goal Authority and Cross-host Coordination | Draft contract / provider qualification | [#3245](https://github.com/huangruiteng/loopx/issues/3245) | Start provider-neutral and file-backed; NoKV is an unpromoted candidate, not authority. |
+| Architecture and Research Incubator | Mixed by RFC | [#3246](https://github.com/huangruiteng/loopx/issues/3246) | Read the per-exploration stage; an RFC alone does not make implementation claimable. |
+
+Core control-plane reliability remains the shared shipped foundation. Effect
+Program hardening, verified transitions, recovery, observability,
+maintainability, and contributor experience continue through the focused rows
+below and the existing `control-plane` label.
+
+## Priority Queue
+
+| Priority | Direction | Slice | Issue / PR | Status |
+| --- | --- | --- | --- | --- |
+| P0 | Core hardening | Wire caller-approved `validation_command` into the remaining self-report entry points | #3082 | Available |
+| P0 | Core hardening | Complete exact-head review of remote execution and terminal writeback fencing | #3074 | Claimed |
+| P1 | Core hardening | Recover the session observed by a failed Codex CLI Turn without weakening drift checks | #3228 | Available |
+| P1 | Benchmark evidence | Split one deterministic adapter-fidelity or treatment-integrity fixture | #3243 | Needs design |
+| P1 | Operator surface / IM | Split one projection or session-contract characterization unit from the incubation branch | #3244 | Needs design |
+| P1 | Shared coordination | Define the first provider-neutral, file-backed `claim_work` parity slice | #3245 | Needs design |
+| P1 | Core hardening | One budget-aware CLI output ergonomics slice | #2881 | Needs design |
+| P2 | Project docs | Release docs timeline v0.2.6 -> v0.4.7 | GH-C04 | Available |
+| P2 | Maintainability | CLI ownership and hot-module extraction | GH-C06 | Available |
 
 ## Product Manager Cut
 

diff --git a/README.md b/README.md
@@ -482,6 +482,36 @@ loopx check \
   --scan-path examples/
 ```
 
+## Current Technical Directions
+
+LoopX has three active strategic programs plus an architecture and research
+incubator. These are direction signals, not delivery promises; `main`, released
+artifacts, and stable reference contracts remain the source of shipped truth.
+
+- **Long-Horizon Benchmarks and Evidence:** reproducible capability evidence
+  and controlled mechanism research across complementary benchmark
+  environments. [Direction tracker](https://github.com/huangruiteng/loopx/issues/3243)
+- **Operator Surface and IM Integration:** an operator workspace, session
+  records, and bounded collaboration surfaces, currently incubating on a
+  dedicated integration branch with `@maxliux5` as implementation lead.
+  [Direction tracker](https://github.com/huangruiteng/loopx/issues/3244)
+- **Shared Goal Authority and Cross-host Coordination:** provider-neutral
+  coordination for explicitly shared goals, with NoKV as an unpromoted
+  provider candidate rather than a new control-plane authority.
+  [Direction tracker](https://github.com/huangruiteng/loopx/issues/3245)
+- **Architecture and Research Incubator:** Effect Program hardening,
+  TypeScript parity migration, hierarchical stride, research exploration,
+  human attention, artifact lifecycle, and memory utility work at explicitly
+  different maturity levels.
+  [Direction tracker](https://github.com/huangruiteng/loopx/issues/3246)
+
+Read the canonical
+[Technical Directions map](docs/project/technical-directions.md) for stages,
+promotion gates, contributor-safe cuts, and ownership boundaries. Use the
+pinned [GitHub Discussion](https://github.com/huangruiteng/loopx/discussions/2851)
+for community discussion. Core control-plane reliability continues as the
+shared foundation beneath these programs.
+
 ## Advanced Documentation
 
 Start with the path that matches your current task. Use the hosted
@@ -551,6 +581,7 @@ deeper documents and versioned protocols.
 
 ### Project and Community
 
+- [Current Technical Directions](docs/project/technical-directions.md)
 - [Project Governance](.github/GOVERNANCE.md)
 - [Contributing](CONTRIBUTING.md) and [Contributor Tasks](CONTRIBUTOR_TASKS.md)
 - [Authors and Contributors](AUTHORS.md)
@@ -627,10 +658,10 @@ or experimental. LoopX does not grant credentials, approve destructive or
 production actions, publish on a user's behalf without authorization, or turn
 an unverified run into evidence of success.
 
-The next milestones are simpler installation and host packaging, broader typed
-runtime adapters, stronger terminal acceptance across repeated public loops,
-independent adoption and outcome evidence, and a more polished management
-surface.
+Current investment is organized through the
+[Technical Directions map](docs/project/technical-directions.md): long-horizon
+benchmark evidence, operator surface and IM integration, shared-goal cross-host
+coordination, and an explicitly staged architecture and research incubator.
 
 ## Star History
 

diff --git a/README.zh-CN.md b/README.zh-CN.md
@@ -433,6 +433,33 @@ loopx check \
   --scan-path examples/
 ```
 
+## 当前技术方向
+
+LoopX 当前有三个活跃战略计划和一个架构与研究孵化器。这些内容用于表达方向，
+不是交付承诺；`main`、已发布 artifact 和 stable reference contract 仍然定义真实
+已交付行为。
+
+- **长程 Benchmark 与证据：**在互补 benchmark 环境中建立可复现的能力证据，
+  并开展受控的机制研究。
+  [方向 Tracker](https://github.com/huangruiteng/loopx/issues/3243)
+- **Operator Surface 与 IM Integration：**建设 operator workspace、session
+  record 与有界协作表面；当前在专用 integration branch 孵化，由 `@maxliux5`
+  作为 implementation lead。
+  [方向 Tracker](https://github.com/huangruiteng/loopx/issues/3244)
+- **Shared Goal Authority 与跨 Host 协作：**为显式共享 goal 提供
+  provider-neutral 协调；NoKV 是尚未晋级的 provider candidate，而不是新的控制面
+  权威。
+  [方向 Tracker](https://github.com/huangruiteng/loopx/issues/3245)
+- **架构与研究孵化器：**以明确不同的成熟度推进 Effect Program hardening、
+  TypeScript parity migration、hierarchical stride、research exploration、human
+  attention、artifact lifecycle 与 memory utility。
+  [方向 Tracker](https://github.com/huangruiteng/loopx/issues/3246)
+
+完整阶段、promotion gate、贡献者安全切片和 ownership 边界见
+[当前技术方向地图](docs/project/technical-directions.zh-CN.md)；社区讨论使用置顶的
+[GitHub Discussion](https://github.com/huangruiteng/loopx/discussions/2851)。核心控制面
+可靠性继续作为这些计划共同的底座。
+
 ## 进阶文档
 
 按当前任务选择入口；[线上文档](https://huangruiteng.github.io/loopx/docs/)
@@ -494,6 +521,7 @@ loopx check \
 
 ### 项目与社区
 
+- [当前技术方向](docs/project/technical-directions.zh-CN.md)
 - [Project Governance](.github/GOVERNANCE.md)
 - [Contributing](CONTRIBUTING.md)与[Contributor Tasks](CONTRIBUTOR_TASKS.md)
 - [Authors and Contributors](AUTHORS.md)
@@ -563,8 +591,9 @@ integration 和进阶路径仍是 optional、default-off 或 experimental。Loop
 获得 credential，不会替用户批准 destructive / production action，不会在未授权时
 公开发布，也不会把未经验证的 run 当成成功证据。
 
-下一阶段会继续改善安装与 host packaging、扩展 typed runtime adapter、加强重复公开
-Loop 的 terminal acceptance、补足独立采用与 outcome evidence，并打磨管理面。
+当前投入按[技术方向地图](docs/project/technical-directions.zh-CN.md)组织：长程
+benchmark 证据、operator surface 与 IM integration、shared-goal 跨 host 协作，以及
+明确分阶段的架构与研究孵化器。
 
 ## Star 趋势
 

diff --git a/docs/README.md b/docs/README.md
@@ -15,6 +15,7 @@ material available without putting all of it on one page.
 | Run or recover a long-lived goal | [Operations](operations/README.md) | [Integration guide](integration.md) |
 | Understand the control plane | [Architecture](architecture.md) | [Concepts](concepts/README.md) |
 | Connect an agent runtime or provider | [Integrations](integrations/README.md) | [Extensions and capabilities](reference/extensions.md) |
+| See what contributors are building now | [Current technical directions](project/technical-directions.md) | [Contributor tasks](../CONTRIBUTOR_TASKS.md) |
 | Build or review LoopX | [Developer guide](development/README.md) | [Testing and quality](development/testing-and-quality.md) |
 | Inspect real outcomes | [Showcases](showcases/README.md) | [Research and evidence](research/README.md) |
 
@@ -66,6 +67,7 @@ a longer onboarding path.
 
 ## Project And Community
 
+- [Current technical directions](project/technical-directions.md)
 - [Contributing](../CONTRIBUTING.md)
 - [Contributor tasks](../CONTRIBUTOR_TASKS.md)
 - [Governance](../.github/GOVERNANCE.md)