Releases: viettran-edgeAI/codex_workflow
Release list
codex_workflow v1.1.17 — Minor fixes, no performance impact
codex_workflow 1.1.17 — Minor fixes with no performance impact
Version 1.1.17 corrects documentation ownership and worker-facing descriptions.
These are instruction-quality fixes and do not change models, reasoning effort,
execution topology, context limits, or expected performance.
Document scope adjustment
The main agent now handles agent_docs/project_progress.md and
agent_docs/latest_session_work.md alongside project_diary.md. Archivist uses
these documents as canonical closure inputs but does not edit them during a
deployment. The generated document templates now contain only project state,
not embedded maintenance instructions.
Consistent Archivist usage in Medium
Medium-route descriptions now consistently state that Archivist is used for
every substantive deployment closure. Medium still keeps implementation,
repair, root-cause decisions, and verification with the main agent. Archivist
handles other assigned documentation, the read-only Git handoff, and the
Deployment Token Report.
Worker-perspective instructions
Archivist installation and closure instructions now explain the observable
assignment context, supplied inputs, required task, and applicable authority
from Archivist's perspective. Companion's initial assignment uses the same
worker-facing approach, avoiding designer-facing lifecycle assumptions and
hidden context.
Validation and artifact
- Artifact:
codex_workflow-1.1.17.zip. - SHA-256:
d9300d43a78058e1d2acab6c1f849f1c47e48f21d227e4243f9357a850bfdbcc. - Validation passed: 58 runtime tests, 8 Deployment Token Report tests,
package-schema validation, and independent archive verification.
codex_workflow v1.1.15
codex_workflow 1.1.15 — Experimental release notes
Overview
Version 1.1.15 tightens the Medium and Heavy orchestration contracts around
project-context intake, worker eligibility, and production ownership. The goal
is to reduce repeated main-agent context loading while preserving its authority
over architecture, root cause, integration, acceptance, and final claims.
Shared deployment intake
- The first Medium or Heavy deployment-state entry now initializes exactly one
persistent Companion before planning, mutations, or other worker dispatch. - Companion receives a substantial initial context assignment, retains useful
diary and module detail, and is reused across route changes. - The main still reads the complete
agent_docs/framework exactly once per
session. Later large syntheses, delta checks, and conflict checks belong to
Companion when they are useful. - Companion assignments should be consolidated because every rollout reloads
its retained context. Status-only calls, repeated broad summaries, and tiny
lookups already answerable from current context are discouraged.
Context routing and investigation
After intake, Medium and Heavy create a compact working-context map:
Directcovers decision-critical material the main must understand.Companioncovers supporting modules, tools, configuration, logs,
dependencies, and other bulky project context.Investigatorcovers one unfamiliar or ambiguous evidence gap that benefits
from independent project inspection, Internet research, or both.
Investigator is no longer limited to Internet-only questions. It remains
read-only and supplies evidence and implications; the main retains every
root-cause, architecture, implementation, and acceptance decision.
Heavy execution boundary
- Heavy keeps the main as the central knowledge director and prohibits it from
becoming a production Executor, deployment operator, repair worker, or
independent Tester during substantive deployments. - Executors own their bounded implementation, operational checks, and ordinary
repair. Tester owns independent verification and its assigned test assets. - Failed routine operational evidence returns to the responsible worker. The
main evaluates evidence and revises decisions or packages instead of entering
a repeated diagnostic loop. - Main-owned reads and worker dispatches are batched when independent. Polling,
status-only requests, and duplicated routine checks are explicitly avoided.
Medium preserves its separate ownership model: planning, root-cause reasoning,
implementation, repair, and verification remain with the main agent.
Documentation and validation
- Archivist guidance now requires concise canonical documents, removal of stale
or redundant detail, and recoverable deployment handoffs. - Runtime contract tests cover the shared intake lifecycle, context map,
Investigator scope, Heavy ownership boundaries, rollout guidance, and concise
documentation requirements.
Artifact
- Artifact:
dist/codex_workflow-1.1.15.zip. - SHA-256:
6ff393d8747fde32ece10d7dbe2a9fee4783b76f9b6ca6d9ae248b2c47d37431. - The archive passed package verification, the 58-test runtime suite, and the
8-test Deployment Token Report suite. - The release workflow rebuilds and validates the package from tag
v1.1.15
before publishing it as a prerelease.