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

**Status:** bounded post-merge candidate. This packet does not change package versions, merge the
World draft, tag or publish an artifact, close issue
[#38](https://github.com/augmented-cognition-engine/core/issues/38), pass SI4, apply a measured
proposal, or declare ACE 0.6.0 complete.

**Core base:** merged `main` commit `7013de62ae7320c51c3de9e9a03b049e768e4d84`.

**World target:** draft [PR #17](https://github.com/augmented-cognition-engine/domain-world-intelligence/pull/17),
executable source `cb7b6fdb2b9fe4dd3c34df8afc1368c86d026710`.

## Objective

Replace stacked-candidate inheritance with one exact default-branch artifact and cross-domain
receipt:

1. build Core, the reference Action adapter, World, and the World source adapter twice from exact
   source identities and require byte-identical wheels;
2. install those exact wheels in a fresh Python 3.12 environment outside every Core checkout;
3. rerun the public World correction journey twice and freeze one canonical result;
4. rerun the independent Market production-store journey, including fresh-process replay after a
   real database restart and atomic-interruption controls;
5. bind merged Core focused, default-branch CI, compatibility, and vulnerability results; and
6. keep every release-owner decision visible rather than inferring a release pass.

The public World path remains:

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

## Ownership boundary

- Core owns durable scope, identity, provenance, authority, Decision, Action, Outcome, append-only
  history, replay, and proposal coordinates.
- Intelligence owns the domain-neutral matched evaluation and `useful | harmful | unproven`
  classifier.
- World owns public-source fixtures, correction semantics, source policy, product criteria,
  controls, and outcome meaning.
- Market remains a separate private consumer. Only bounded result identities and verification
  totals may enter this public record; no private source, fixture, product data, or extension code
  moves into Core.

## Acceptance and non-claims

The packet may prove exact merged-source installation, reproducible wheels, checkout exclusion,
deterministic World reproduction, independent Market reproduction, restart durability, atomic
failure behavior, and green compatibility/security gates. It cannot prove causality, population
performance, live freshness, general source independence, provider quality, human/customer
benefit, general SI4 completion, or a published 0.6 artifact.

Every governance proposal remains non-effective, non-selectable, unapplied, and subject to
separate human/Core authority. This packet adds no proposal-application path.

## Issue #49 boundary

F1 and F5 implementation are merged in exact Core `main` and are re-derived here through focused,
default-branch, and external-consumer evidence. On `2026-08-11`, an authenticated release owner
reconciled the public issue #49 checklist by marking F1 and F5 complete against exact Core
`7013de62ae7320c51c3de9e9a03b049e768e4d84`.

F3 remains unimplemented, unresolved, and unwaived. The same public disposition re-dated it to
`2026-11-05` under trusted-package-only scope, `ACE_DISABLE_EXTENSIONS=1`, compatibility-matrix
verification, and operator disablement on unexpected partial registration. Issue #49 remains open,
and its future packet must stage every mutable registration surface, enforce ceilings, publish or
roll back atomically, and emit a bounded failure report.

## Owned files, rollback, and deletion criteria

This packet owns this work packet, its point-in-time evidence, one evidence-index entry, and
restrained current-state roadmap and maturity reconciliation. It owns no runtime code, schema,
package version, workflow, World or Market policy, issue checklist, tag, or release.

Rollback removes only these additive records and references. Preserve the evidence as historical
if later artifact epochs, package versions, World source, or release identities change. Supersede
it with a release-readiness receipt only after World review/merge, final artifact/version decisions,
public-index installation, and release-owner acceptance.
