wutonglab-org is the organization home for ODOS.

ODOS is a method framework for turning real problems into reliable capabilities.

中文：

wutonglab-org 是 ODOS 的组织账号，用于为 AI 时代的 FDE 提供理论、框架、模板、skill 和执行约束。

The organization exists to support Field Development Engineers who transform real business scenarios with AI.

Its role is not to publish private project work. Its role is to extract reusable structure from field practice and turn it into open, durable framework assets.

ODOS is the work guide for FDE.
FDE field practice is the feedback source for ODOS.

中文：

ODOS 是 FDE 的工作指南。
FDE 的真实项目经验，是 ODOS 持续进化的反馈来源。

ODOS is built around a stable operating loop:

Observe -> Define -> Build -> Verify -> Orchestrate -> Review

Expanded:

Observe real work
  -> Define the capability boundary
  -> Build the capability
  -> Verify with evidence
  -> Orchestrate under governance
  -> Review runs and feedback

中文：

观察 -> 定义 -> 构建 -> 验证 -> 编排 -> 复盘

展开：

观察真实工作
  -> 定义能力边界
  -> 构建能力
  -> 用证据验证
  -> 在治理下编排
  -> 复盘运行与反馈

The long-term architecture is:

ODOS
  -> Method
    -> Template
      -> Project

Projects remain private. Reusable lessons move upward into methods, templates, contracts, skills, checks, and framework documents only after sanitization and project detachment.

Pattern is not part of the hierarchy. It is a project classification field:

Project has Pattern
Project uses Method
Project copies Template

Example:

Pattern: Workflow Automation
Method: O2O
Template: Business Adapter
Project: private business adapter project

The boundary is fixed:

ODOS / Template
  public under wutonglab-org

Project
  private under wutonglab

Project information layers
  local + private + share

Template
  public extraction from local/private/share after sanitization,
  project detachment, abstraction, and verification

Inside a private project:

local
  machine-bound state, cache, browser profiles, sessions, temporary files
  not committed

private
  real business facts, evidence, credentials boundary, project-specific docs
  private forever

share
  project-internal reusable assets, schemas, synthetic examples, helpers
  still private by default

share is not the public layer. template is the public reusable layer.

ODOS learns from projects asynchronously, at stage boundaries:

private project execution
  -> local/private/share accumulate project knowledge
  -> stage boundary or review point
  -> sanitized feedback
  -> ODOS feedback proposal
  -> maintainer review
  -> template / method / checker / skill update

ODOS should guide projects, not block them. When ODOS does not yet cover a project need, the project continues locally, records the gap, and feeds back a sanitized lesson later.

This organization is for:

• ODOS framework documents
• reusable methods and templates
• generic skills and checkers
• sanitized examples
• project-calibrated framework evolution

It is not for:

• private projects
• project share layers
• private customer data
• real project evidence
• credentials
• raw logs or browser state
• project-specific operational records

• odos: the open-source ODOS framework