# ACE 0.6.0 Measured Intelligence release-convergence work packet (v1)

**Status:** bounded convergence candidate. This packet does not merge the stacked candidates,
publish artifacts, close issue [#38](https://github.com/augmented-cognition-engine/core/issues/38),
pass SI4, or complete ACE 0.6.0.

**Frozen:** 2026-08-11 from Core observed-result candidate
`433e3d16c5458c975557dcd1552824fb959d4d12` over live `main`
`be5e76c79715bb34bcbdcae9a0471a5c317fafe7`.

## Objective

Compose the release-critical candidate evidence without widening product scope:

1. build the exact Core and separately distributed reference action-adapter artifacts;
2. run World P2C10 from the installed Core artifact outside every Core checkout and freeze one
   canonical, machine-readable result;
3. retain the independent Market reproduction as a separate domain falsification;
4. rerun focused, compatibility, security, packaging, and repository checks; and
5. make every unresolved release decision visible rather than inferring a 0.6 pass.

The public World path remains:

```text
Observation -> Shift -> Signal -> Brief -> Decision -> reviewed Action
            -> observed Outcome -> governed feedback
```

The useful classification and `promote` proposal are measured under World-owned criteria. The
proposal remains non-effective, non-selectable, unapplied, and subject to separate Core authority.

## Source and ownership boundary

- Core owns immutable state, provenance, authority, Decision, Action, Outcome, durable replay, and
  the non-effective proposal coordinate.
- Intelligence owns the domain-neutral matched evaluation and useful, harmful, or unproven
  classification machinery.
- World owns BLS nouns, recorded source policy, correction semantics, matched control, review
  score, and public convergence record.
- Market remains an independent consumer and does not become a Core release dependency.

No domain noun, source trust rule, or result interpretation moves into Core or Intelligence.

## Acceptance and non-claims

This packet may demonstrate candidate artifact installation, exact hashes, checkout exclusion,
deterministic public-source reproduction, historical replay, independent second-domain
reproduction, and green required checks. It cannot demonstrate a published 0.6 artifact, live
freshness, population performance, causality, general source independence, general SI4 completion,
or human/customer benefit. It adds no proposal-application path and performs no release action.

## Issue #49: explicit 0.6 dispositions

The accepted `next minor` deadlines in issue
[#49](https://github.com/augmented-cognition-engine/core/issues/49) now apply to 0.6.0. This packet
records the following literal dispositions:

| Item | 0.6 disposition | Effect on this packet |
|---|---|---|
| F1 — generation guard / real-DB concurrency and receipt reconciliation | **Open release gate; not waived, deferred, or resolved** | Candidate evidence may proceed; 0.6 release closeout may not call this satisfied |
| F3 — trusted-registration ceilings and partial-registration rollback/reporting | **Open release gate; not waived, deferred, or resolved** | Candidate evidence may proceed; 0.6 release closeout may not call this satisfied |
| F5 — pin the legacy optimizer query to `self_optimizer_proposal` | **Open release gate; not waived, deferred, or resolved** | Candidate evidence may proceed; 0.6 release closeout may not call this satisfied |

Before release closeout, the release owner must either accept bounded hardening packets or record a
new dated deadline with containment rationale on #49. This work packet does neither and does not
silently broaden itself to implement the items. F2/F6 retain `2026-11-05`; F4 remains tied to the
next security bundle; F7 remains due before production traffic.

## Owned files, rollback, and deletion criteria

This packet owns this work packet, its point-in-time candidate evidence, and restrained roadmap and
capability-maturity reconciliation. It does not own measured-impact implementation, World or
Market code, package versions, schemas, workflows, or issue #49 hardening.

Rollback removes only these additive records and references. Delete or supersede this candidate
evidence when the tested source identity changes, an artifact hash cannot be reproduced, an open
gate receives an explicit owner disposition, or a later release receipt binds the final merged and
published identities.
