v0.9.6

Work Charter v0.9.6 keeps the user's actual outcome and the freedom to adjust methods intact across handoffs.

• Preserve the original goal, the basis of necessary constraints, existing evidence and downstream method-adjustment authority across planning, execution and review.
• Prioritize real inputs and the intended environment for prototypes. Explain necessary checks without per-test approval, invented API/page/review caps or non-blocking uncertainty gates.
• Choose optional collaborators by their ability to complete an independent outcome and by total handoff cost. Keep tightly coupled editing, running and repair together.
• Keep the public package self-contained and independent of personal defaults, named services and private routing.

Model defaults, configuration schemas and installer production behavior are unchanged. Existing agreements are not automatically migrated.

Validation: independent source review passed; the missing section-entry link found during review was corrected. SOURCE checks, Skill metadata, repository provenance and whitespace checks passed. These establish source quality and identity, not universal runtime adherence or productivity gains.

Work Charter v0.9.5

Outcome-first delivery

Work Charter v0.9.5 prioritizes making the main workflow usable and delivering the agreed outcome. Improve through actual use, while preserving explicit requirements and applicable protections.

• Choose test timing to suit the task and group related edits before checking. Broader verification follows actual change impact or explicit requirements.
• Keep non-blocking edge cases, extra tests and review suggestions as follow-ups. Recording a suggestion or assigning severity does not automatically make it a delivery requirement.
• Carry the full guidance inside the installable package, so it works independently of private host rules.

No model defaults, configuration schemas, roles, template structure or production installer behavior changed. Existing approved contracts remain in force.

Focused source checks (33/33), Skill metadata and repository provenance checks passed. Independent review and a managed local update with six-file readback passed. These establish source and installation correctness; behavioral improvement remains to be observed in ordinary use.

主要变化

优先跑通本次约定的主要流程，再通过实际使用发现和改进问题。按任务需要安排测试；预想的非阻断边缘情况和额外补测可以留作后续，不挤占主要交付进度。完整原则随 Work Charter 安装包提供，无需依赖私人全局规则。

保留明确要求和适用保护，不新增角色、审批表单或测试矩阵。

Work Charter v0.9.4

Work Charter v0.9.4

User decisions now focus on outcomes, material choices and the evidence needed to decide. Agents retain responsibility for technical verification and authorized same-scope repair; routine corrections do not add another approval gate. Changes to acceptance, trust or material risk route first to the lowest already authorized owner, while user-reserved decisions and operation-local permission remain protected.

• Clarify conditional and partial approvals, refusals, withdrawal and user cooperation without mandatory forms, ledgers or extra roles.
• Keep the portable Skill independent of private host rules. Host guidance separately provides the general-task fallback, including tasks that do not adopt Work Charter.
• Include the previously locally delivered GPT-6.1 Sol / xhigh Planner and Executor defaults. Whole-object configuration precedence, schema v2, arrangement-v1 and other role defaults are unchanged.

Existing task contracts, frozen model combinations and projects are not automatically migrated. Installation does not modify personal model configuration.

Validation: independent review passed; SOURCE static clauses 33/33, Skill metadata, repository provenance (106 mapped files) and whitespace checks passed. The managed local copy matches all six reviewed package files and preserves its previous permission records. These are static and local delivery results; fresh runtime loading and general behavior remain UNKNOWN. No efficacy study was performed.

The candidate descriptors remain immutable pre-effect snapshots. Current delivery and publication evidence is recorded in the repository's State and Verification owners.

Work Charter v0.9.2

Work Charter v0.9.2 clarifies how approved work continues across ended role turns.

• Formal asynchronous Team and Phased work normally uses independently addressable role tasks with an authorized, supported next-turn route. Delivery, activation, completion and acceptance are distinct.
• The current Codex mixed-carrier default is temporarily suspended. Its design and explicit restoration conditions remain available; restoration requires a supported route and user adoption.
• Bounded Direct review and evidence subagents remain available within an active parent turn. Preauthorized repair and re-review loops continue without per-round Planner approval, while acceptance stays with its owner.
• Task labels should be short and recognizable; exact personal title limits belong to host policy.
• arrangement-v1, model schema v2, package model defaults and installer behavior are unchanged. Existing project contracts and frozen deliveries are not automatically migrated.

Validation: the unchanged package passed 33 SOURCE checks, metadata validation and independent review. Managed installation and file identity were verified locally. Publication receives separate repository, review and remote readback checks. These checks do not claim general runtime activation or efficiency gains.

See Changelog and current publication evidence.

Work Charter v0.9.1

Work Charter v0.9.1

This release brings the local v0.9.0 contract/configuration changes and the
v0.9.1 migration and continuing-review refinements to the published package.

What's changed

• New agreements use Direct, Team, or Phased with contract_format: arrangement-v1.
  Conditional selection covers outcomes, real constraints, review, recovery,
  role carriers and authorized progression.
• Existing L0–L4 agreements remain valid. Migration can be proposed at a stable
  work checkpoint without waiting for a whole Phase to finish; approval,
  findings, failures, consumed budgets and frozen models are preserved.
• Model configuration schema v2 selects complete objects by responsibility and
  arrangement, with legacy overrides and schema-v1 compatibility. Ambiguous
  legacy Direct choices require a user decision.
• Work can continue through authorized implementation, independent review,
  original-author repair, re-review, acceptance and the next approved item.
  New phases and expanded effects still require their applicable authority.
• Adoption, reassessment and migration use the same conditional selection.
  A previous agreement supplies reusable answers without skipping material choices.
• Prefer one reliable continuing Reviewer for related O/P/E products when real
  request and return routes support it. Review remains independent and read-only;
  original authors repair and designated owners accept.

Compatibility and verification

Installation does not migrate a project or rewrite personal model configuration.
Existing frozen deliveries keep their agreed settings. The six-file package and
production installer mechanism are unchanged in shape; the v0.9.1 package contains
the updated instructions.

SOURCE contract checks, repository provenance/inventory checks, independent
semantic review and the local managed installation have bounded evidence.
These are not model-performance evaluations or guarantees of runtime adoption,
cache hits, cross-task delivery or efficiency gains.

Package identity

• Installable source: skills/work-charter/
• Version: 0.9.1
• Git package tree: 39659168b5fb20899335dd0923c87b65d5a95e36
• SOURCE file-list SHA-256: 3095abc1727ca15901185876ce012b0145c5f7deede636fa29511bdfb69dacb8
• Install-manager package SHA-256: 07a4c7579c985d8580387e1cbc48f315289975b6e62369b316c5fdf3fcfb2ec0

The two SHA-256 values use different serializations. Use the Git package-tree
identity as the explicit target trust anchor with the existing managed installer.
Historical candidate descriptors remain immutable pre-effect snapshots.

Work Charter v0.8.0

Work Charter v0.8.0

Work Charter now presents three user-facing work arrangements: Direct, Team, and Phased. Existing L0-L4 contracts remain valid. Direct preserves the separate L0, L1, and L2 internal rules; existing approved work is not migrated by this release.

• Select an arrangement from the known goal, constraints, coordination, review, and recovery needs. Ordinary small work remains lightweight.
• Review the actual Direct, Planner, Executor, or Orchestrator product against its applicable instructions and evidence. The original author repairs findings, and the same valid Reviewer rechecks them.
• Allow approved continuing subagents, separate role tasks, or mixed carriers when permissions, continuity, user intervention, and result routing are reliable.
• Update schema-v1 package defaults: Direct primary, Team Planner, and Phased Orchestrator use gpt-6-astra/high; Phased Planner and Executors use gpt-6-sol/xhigh; enabled independent Reviewers use gpt-6-astra/medium. Existing complete-object user overrides and frozen task settings retain precedence.
• Fix the Standard workflow section link reported during the v0.7.1 review.

The source contract and repository provenance checks passed for this release candidate. These checks and independent source review do not establish natural agent adherence, live model routing, or runtime Skill reload. See docs/skills/work-charter/VERIFICATION.md for the exact evidence and limits.

Work Charter v0.7.1

Work Charter v0.7.1 is the first public release since v0.6.5. It includes the
accepted v0.6.6–v0.7.1 changes; those intermediate candidates were not released
separately.

What's changed

• Delivery and recovery: Keep authorized work moving through implementation,
  independent review and acceptance without per-message receipt loops. Preserve
  formed decisions, evidence, failed attempts and consumed limits across task
  or context changes.
• Evidence scope: Separate material acquired from material actually examined.
  Carry inspection gaps, source identity and data boundaries through delegated
  evidence collection and recovery.
• Roles and model defaults: Clarify approved Planner delegation, the
  preauthorized Reviewer → original Executor → same Reviewer repair path, and
  Planner acceptance. The package defaults use Sol/xhigh for L0–L2 primary and
  Reviewer and L3–L4 Executor; Astra/high for L3–L4 Planner and L4 Orchestrator;
  Astra/medium for L3–L4 Reviewer. Existing tasks and user configuration are
  not changed by these package defaults.
• Authorization by result: Describe approval by outcome, functional domain,
  environment, effects and real cost. Ordinary file lists, tools, check order
  and same-scope repairs stay replaceable within that authority. Explicit
  permission, production, managed-path, frozen-evidence, compatibility,
  one-shot, independent-review and acceptance boundaries remain binding.

The installable Skill remains a six-file package. This release does not
automatically activate Work Charter, change existing tasks or prove runtime
loading, natural adherence or performance gains. See CHANGELOG.md and
docs/skills/work-charter/VERIFICATION.md for version history and check scope.

Work Charter v0.6.5

This release brings the changes since the previous public release, v0.3.0, into one current version.

• Clarifies independent Reviewer responsibility, evidence limits, one complete result per checkpoint, and continuity of approvals, findings and recovery state.
• Adds package-owned model defaults, complete-object configuration resolution and level-specific role overrides. Current Astra defaults use medium for L0–L2 work and review, high for L3/L4 Planner, xhigh for L4 Orchestrator, and medium for L3/L4 Executor and Reviewer. General compatibility fallbacks remain separate.
• Keeps ordinary L0 checks lightweight, reuses an applicable approved Charter, and loads detailed guidance for the actual level, responsibility and decision. Material scope, authority, acceptance or recovery changes call for reassessment; the user owns level decisions.
• Asks Agents to justify additional safeguards and compare the remaining cost of auxiliary work with simpler routes to the same protected outcome.
• Includes the intervening managed-installation permission-context and postflight corrections, with earlier failed attempts retained in the verification history.

The installable six-file package tree is d0df02a81471c2b9e157c9f6faebc65948cb4b54. This published identity can be retained independently of a future candidate checkout for the managed lifecycle tool's package-tree trust input; follow the tagged README for the full update and rollback contract.

The repository records deterministic checks, independent source review and bounded local installation evidence separately. This release does not establish fresh-task loading, natural adherence, comparative model performance, cross-Harness behavior or broad efficacy. Skill instructions are advisory and do not provide programmatic enforcement. Earlier tags, candidates and failure evidence are preserved.

README and lifecycle guidance · Verification

Work Charter v0.3.0

First independent release of Work Charter, a Codex Skill for bounding
consequential work by outcome, authority, evidence, recovery, and proportional
coordination.

Highlights

• Publishes the independently versioned junwei529/work-charter repository.
• Preserves the installable 5-file Work Charter package byte for byte from the
  recorded migration source.
• Includes deterministic SOURCE qualification for selection and activation,
  authority non-expansion, coordination and recovery, and Standard O/P/E.
• Includes an explicit-destination lifecycle tool with dry-run defaults and
  disposable install, update, rollback, uninstall, and recovery checks.

Evidence boundaries

• Local release readiness is verified for the accepted immutable candidate.
• The release does not by itself prove stable installed-copy behavior,
  cross-Harness behavior, untested selection or loading contexts, persistent
  lifecycle effects, or broad product efficacy.
• Lifecycle receipts provide integrity and routing evidence, not cryptographic
  ownership against a same-privilege local actor able to forge a complete
  receipt.