Understand the workflow, then trust the evidence.

Install DynosAI, configure a provider, initialize a project, and run your first governed workflow.

The day-to-day DynosAI workflow, commands, scope changes, recovery, and greenfield/brownfield usage.

Use the guided project hub, project-scoped workflow, approvals, checks, themes and multilingual interface.

Exactly what DynosAI verifies, how validation profiles work, and what Quality 100 does—and does not—mean.

What DynosAI 1.0 freezes: MCP names, public CLI, schema v6, App Server scope, human gates and optional harness features.

Enforced vs not-enforced 1.0 controls, including the honest local-browser and loopback surface.

Authority boundaries, workflow state, Git, MCP, memory, verification, and the local-first runtime model.

Phase-aware budgets, complexity signals, failure classification, route lifecycle, and predictive shadow mode.

How DynosAI indexes existing code and builds an evidence-backed inferred baseline without inventing business truth.

Codex and Cursor integration, managed runtime behavior, and transport compatibility decisions.

MCP telemetry, tokens, context strategy, validation evidence, routing decisions, retries, and audit events.

The deterministic, migration, provider-native, real-provider, Oracle, wheel, and replay validation layers.

Public command overview for projects, work, diagnostics, setup, model control, and acceptance.

Runtime and environment configuration for DynosAI projects and providers.

Responsibility of every production Python module in the DynosAI package.

How DynosAI evolved from persistent workflow state to provider-certified governance.

Governed session continuity. Bounded multi-turn Codex trials in one provider session. Cursor remains Preview. Not production-ready 1.0.

Codex MCP observability. App Server preflight without model turns. Opaque _meta no longer aborts a 2025 session. Not production-ready 1.0.

Provider runtime portability. User-local workspaces, Codex temp-home abort, candidate identity gate. Not production-ready 1.0.

Certification integrity and protocol correctness. Release archive safety, MCP 2026 strict metadata/MRTR, MATRIX runner honesty. Not production-ready 1.0.

Standards and release evidence: MCP 2026 compatibility, unified release gate, eval corpus and distribution ADR. Not production-ready 1.0.

Freeze: threat model, contribution/certification process and loopback honesty. External PRs stay closed. Not production-ready 1.0.

Installation: Studio doctor, verified local wheel, installed-package CI and 0.19.0 upgrade preservation. Not production-ready 1.0.

Eval maturity: acceptance ZIP importer, governed-change cost aggregates and a stable authority prefix. Not production-ready 1.0.

Certification evidence: MATRIX_1.0 not_run cells and two-session lease proof. Historical 0.13 scores are not copied.

Contract freeze: frozen MCP names, optional harness switches, shared release-gate policy. Not production-ready 1.0.

Ecosystem: capability manifests for Cursor ACP and Codex app-server; uncertified clients and packs refused.

Secure Autonomous Runtime: Strict/Balanced/Autonomous profiles, runtime-only vault and policy evidence without OS network interception.

Eval Intelligence: failure attribution, local-trace mining, inbox-only improvement loop and offline regression evidence.

Governed Agent Teams: DAG waves, file-disjoint leases, claim/fan-in and no extra provider spawn.

Verified Agent Harness: context handles, ExecutionRuntime, validation integrity, eval registry v0 and execution policy.

Guided Studio UX refresh: setup, reviews, themes, project checks, help and compatibility boundaries.

Install, validate and understand compatibility and limitations of the Control Plane & Studio Alpha release.

Maintainability review, current module and LOC metrics, hotspots, and characterization-before-extract policy.

Use dynosai on PyPI, keep the dynosai_flow import, and keep MCP serverInfo as dynosai-flow.

Future plugins follow the portable Agent Plugins spec with a com.dynosai extension. No DynosAI Pack format.

Support 2026-07-28 plus 2025-11-25 and 2025-06-18 on stdio. Official HTTP conformance is not pretended.

Versioning, changelog discipline, tests, acceptance matrices, and release-candidate and promotion policy.

Security policy, responsible reporting, and project security boundaries.

Maintainer development, release gate and certified-provider process. External pull requests are not currently accepted.

The product roadmap from Local Studio through harness loops, governed agent teams, eval intelligence, secure runtime and 1.0.

Release-by-release evolution, fixes, compatibility work, validation, and release and promotion history.