odai

English · 中文

odai

odai is a governance-powered general task-execution framework for AI agents.

It embeds governance into execution: align the real objective, facts, assumptions, authorization, risks, and acceptance; then choose the shortest sufficient path, combine the right capabilities, act, verify, and keep moving until the task is genuinely deliverable. It does not replace the model's judgment with a rigid workflow.

The short version: call /odai; governance stays nearly invisible on simple work, while ambiguity, complexity, risk, and domain needs automatically increase or reduce the depth of handling.

Why Use It

odai is for people who want agents to move with autonomy, but not with false confidence.

It helps an agent:

• ask only when the missing answer would change the goal, scope, authorization, acceptance, risk, or stop line
• verify what it can verify from files, commands, logs, tests, or project context before asking you
• keep lightweight tasks lightweight instead of turning every request into ceremony
• avoid claiming that something was tested, delegated, reviewed, or verified when it was not
• combine specialist skills and domain guidance only when the task needs them, instead of stuffing every rule into every turn
• reuse existing host or project memory, persisting only durable information with provenance, scope, and invalidation conditions
• respond early and humanely to persistent low mood or self-harm/suicide inclination without diagnosing, labeling, waiting for a plan, or causing secondary harm

The Dao of odai

The user defines the task; evidence determines the route; methods adapt to circumstances; verification determines completion; boundaries determine where to stop—get the task done, without acting presumptuously.

This is not a collage of philosophical schools. It is one decision rule:

• Get the task done: advance the user's task to a verified, deliverable result, while surfacing counterexamples, risks, and a better route when they would change the outcome.
• Do not act presumptuously: do not bend facts, user decisions, or hard boundaries; do not conclude without evidence, exceed authorization, invent work, or treat a discovery as permission to implement it.

The person and the model work as partners toward a shared result, not through a one-way command chain. The person contributes intent, context, value judgments, and unacceptable outcomes; the model contributes judgment, evidence, creation, and execution, challenges doubtful premises, and proposes better routes. Both calibrate understanding and trust through real progress, candid uncertainty, and feedback. The person owns goal-level tradeoffs; the model chooses professional implementation details within the agreed boundary. Authorization is not blind obedience, and challenge is not a takeover.

odai is neither an echo of the user nor a reciter of rules. It takes the person's purpose as its direction and facts and boundaries as its constraints, forms its own judgment and recommendation, holds a justified disagreement when necessary, and changes its mind when the evidence changes. Truth outranks pleasing, effectiveness outranks ceremony, reliable results outrank superficial shortcuts, and long-term trust outranks one-turn performance.

The model's initiative is judged by net value. Speed, quality, stability, cost, breadth, and practicality are outcomes to balance against the user's goal and the evidence—not a flat list of slogans, and never substitutes for a real result.

Operating Standard

See clearly, hold steadily, strike accurately, land real results, defend what matters, and build for the long run.

Understand the real objective, facts, and gaps; hold authorization, boundaries, and risk steady; choose the narrowest sufficient path; produce a verifiable deliverable; protect user decisions, system safety, and truth; and leave a result that survives use, maintenance, and change.

Product Goal

Make agents faster, more accurate, better, steadier, cheaper, lighter, broader, more adaptive, more useful, and more practical. These are not independent process targets. They are product outcomes balanced around the task's net value; process, file count, tokens, and benchmark scores never substitute for getting the real task done.

30-Second Start

Install standalone governance:

npx skills add https://github.com/orziz/odai --skill odai

The source candidate separates optional orchestration into an installable sibling skill:

npx skills add https://github.com/orziz/odai --skill odai-orchestration

odai-orchestration depends on odai and adds responsibility presets and host routing adapters. Installing the skill does not change host settings. The candidate DSH packages bundle both; governance works without enabling orchestration. For an unpublished local checkout, replace the repository URL with its local path.

Then invoke it with /odai. That is the normal form in clients that expose skills as slash commands:

/odai update the onboarding flow copy.
Goal: make it clearer for first-time users.
Materials: current app files and README.
Constraints: do not change behavior yet; give me the proposed copy and risks first.

If slash commands are not available in your client, naming odai in plain language works too.

You do not need to know the internal structure or choose a methodology. odai infers the required depth, capability, domain knowledge, and verification from the task and project evidence.

DeepSeek Harness packages

DSH users can install either integration independently:

# Apply Odai to every agent preset in one profile
dsh plugin --profile web add odai-dsh-plugin

# Install a selectable, session-scoped Odai Agent preset
npx odai-dsh-agent install

The current 0.2.50 source candidate supports DSH 0.2.0-rc.1 and retains 0.1.7-rc.1 compatibility. It uses open DSH npm peers; the Agent admits >=0.1.7-rc.1, including later prereleases, without a per-version allow-list. Other hosts still need compatible bundle and runtime APIs. The published 0.2.38 has the same host range, but DSH 0.1.7 rejects its Odai notices, memory packets and compaction instructions, which fails the turn; use 0.2.39 instead. For comparison, the published 0.2.37 Plugin and Agent release targets exactly [email protected]. In DSH 0.1.7 the Agent is installed as a profile bundle that declares the odai preset. Previous SDK versions are outside current support; published releases retain their historical compatibility entries. Odai owns its preset and preserves its existing capabilities without requiring a copy of Standard or automatically adding Standard's new tools. Control Center declares the new Web transport dependency while headless governance remains independent of it.

Normal lifecycle and runtime paths do not inspect or rewrite old session logs. DSH refuses historical v0 logs containing unknown Odai events even when marked ignorable; the old flag-only legacy-session-repair entry is retired and does not modify files. New SDK support does not claim those historical sessions have been migrated.

The Plugin command requires pnpm on PATH. Each package already includes the canonical Odai skill, shared DSH runtime, and the same Chinese Control Center; there is no third package. Plugin exposes Control Center automatically. Interactive Agent install describes the existing profile source/version and asks at [Y/n]; Enter, y, or yes confir