# ACE public roadmap

**ACE, the Intelligence Builder. Build intelligence, not infrastructure.** ACE is an open,
provider-neutral Intelligence Operating System for turning authorized sources into living,
source-grounded briefings, monitors, decisions, and improving institutional knowledge. Models may
provide inference inside the loop. ACE owns the durable state, composition, lifecycle, authority,
provenance, and outcome loop around it.

This roadmap is the authoritative public view of ACE outcome state and dispatch. It describes
product capabilities rather than internal release operations, commercial plans, customer work, or
security-sensitive details. Priorities may change as maintainers learn from users and contributors.

## North star

The north-star builder journey is:

```text
install → Connect → Map a concept model → Watch what matters → Brief with citations → Activate
→ keep updating → improve relevance through feedback
```

The outcome must arrive before the architecture lesson. A builder should not need to understand
Core, Intelligence, Domain Packs, compiler mechanics, or hand-authored JSON to reach first value.
Those boundaries remain essential implementation and trust guarantees underneath a guided product
experience.

ACE is organized around four durable responsibilities:

- **Core** owns cognition and control: provider-neutral reasoning orchestration, product-scoped
  identity, immutable and temporal state, provenance, authority, decisions, execution contracts,
  and outcomes.
- **Intelligence** owns domain-neutral sensing and orientation: Observation, Entity Snapshot,
  Shift, Signal, Brief, Case, monitor, routing, synthesis, feedback, pack compilation, and
  conformance contracts.
- **Domain Packs and connectors** supply vocabulary and source access: ontology, source mappings,
  detector definitions, personas, synthesis policy, source adapters, and domain policy without
  making those nouns or rules part of Core.
- **Domain applications and product surfaces** expose the appropriate experience through an
  application, API, CLI, MCP, IDE, workflow, or Atrium without becoming the owner of durable
  intelligence.

The north-star acceptance test is:

> Can a builder connect authorized sources and receive useful, source-grounded intelligence that
> stays current and improves with feedback—without building the underlying infrastructure,
> surrendering human authority, or learning ACE's internal layers first?

One cross-cutting expression of that north star is **continuous situational intelligence**: ACE
maintains living orientation over any bounded, changing subject a user is authorized to examine.
The subject may be personal, organizational, market, geopolitical, scientific, technical, or
another pack-defined domain. Core owns authority, durable state, governed reasoning, decisions,
and outcomes. Intelligence owns the neutral resource and derivation contracts. Domain Packs own
what entities, relations, measurements, material changes, personas, and synthesis policies mean;
connectors own the reviewed translation from an authorized source into that boundary.

## Roadmap and design-document hierarchy

- **This file** owns current public outcome state, sequencing, and dispatch.
- [Architecture](docs/architecture.md) records the as-built system and dependency boundaries.
- [Governed cognition design](docs/design/capability-evolution.md) details how ACE can be taught,
  reviewed, versioned, measured, revised, and retired.
- [State Engine design and implementation record](docs/design/state-engine-roadmap.md) preserves the
  two-plane design, TP0–TP8 sequence, contracts, tests, and historical packet decisions.
- [Capability maturity](docs/capability-maturity.md) defines the current supported, experimental,
  internal, and planned product surface.
- The [evidence archive](docs/evidence/README.md) contains point-in-time acceptance and release
  receipts. Evidence records do not independently change roadmap state.

Roadmap outcome states are used strictly:

- **ready** — authorized and able to start;
- **active** — currently being executed;
- **candidate** — implementation exists, but evidence or reconciliation is incomplete;
- **not ready** — a dependency or acceptance gate remains;
- **passed** — outcome, verification evidence, limitations, and roadmap reconciliation are complete;
- **superseded** — replaced by an accepted newer outcome.

## Current release checkpoint

The latest published release is [`ace-core` 0.8.3](https://github.com/augmented-cognition-engine/core/releases/tag/v0.8.3)
on PyPI and GitHub. It provides the compatibility baseline used by the independently released
World and Market Intelligence products.

The current 1.0.0 release candidate completes the bounded 0.9 single-user journey and freezes it as
the stable Personal Intelligence Operating System for one local owner and one documented
single-node deployment. Publication and clean public-artifact reproduction remain the final
release gates; the candidate does not claim collaboration, managed hosting, or distributed
operation.

The 0.8 release makes the existing Builder, composition, memory, authority, action, and outcome
capabilities coherent as one **Intelligence Operating System**. One governed point-in-time resource
plane exposes the complete evidence → orientation → decision/action → outcome → feedback loop to
machines and to Atrium. Independent public World and Market repositories reproduce the same
contract with materially different ontologies and dispositions. Schema head remains v177 and the
thin MCP surface remains exactly eleven tools. The exact pre-publication source, cross-domain
proof, verification, and limitations are bound by the
[Intelligence OS release closeout](docs/evidence/intelligence-os-v0.8.0-release-closeout-v1.md).

The [0.8.3 GitHub Release](https://github.com/augmented-cognition-engine/core/releases/tag/v0.8.3)
and public [`ace-core==0.8.3`](https://pypi.org/project/ace-core/0.8.3/) package close the 0.8
compatibility line. The 0.8.1 foundation binds live onboarding state into Atrium, defines
Opportunities as evidence-backed decision openings, establishes the ACE design system, and adds a
reproducible World AI resource replay. Atrium remains a repository-delivered optional workspace
rather than a second state or authority path.

### Passed hardening — Atrium live onboarding and product experience

The 0.8.1 patch closes one experience gap without creating a new product layer. Core now
projects one inert onboarding profile plus the exact append-only Intelligence Builder session
history through the same authenticated resource plane Atrium already consumes. Atrium renders
proposal, working, blocked, retrying, and complete states from those durable records and opens the
first Brief only after `first_briefing_ready`. World AI supplies the paired domain profile and a
four-agent `Connect -> Map -> Watch -> Brief` acceptance journey over admitted official-source
evidence. Core PR #145 and World PR #24 landed after repository, installed-artifact, browser,
naked-kernel, and package checks passed. Follow-on work adds a local-only replay of an immutable
domain resource page, replaces internal persistence language with user-facing setup status,
defines the Opportunity experience, introduces the ACE-owned design system, and applies a truthful
visual What / Why / How / When grammar across Briefs and decision-facing intelligence. It does not
by itself complete the 0.9 Single-user Intelligence Builder promise.

The passed 0.8.2 patch adds the Atrium Intelligence Catalog as an experience entry
slice: the generic resource consumer enumerates all admitted onboarding profiles in product scope,
deduplicates them by profile identity, and always offers the Core-owned Custom Intelligence path.
World and Marketing contribute their own declarative profiles from their independent repositories;
Core names neither domain and grants no installation, connection, monitor, or activation authority.
This makes first use outcome-led across domains while leaving live selection/session binding and
activation on the existing governed Builder boundaries. It is preparatory product work, not a
claim that the complete 0.9 single-user journey has passed.

The prior [0.7.0 GitHub Release](https://github.com/augmented-cognition-engine/core/releases/tag/v0.7.0)
and [`ace-core==0.7.0`](https://pypi.org/project/ace-core/0.7.0/) package remain the passed
Intelligence Builder Foundation boundary, recorded by the
[0.7 release evidence](docs/evidence/intelligence-builder-foundation-v0.7.0-release-closeout-v1.md).

The [0.6.0 GitHub Release](https://github.com/augmented-cognition-engine/core/releases/tag/v0.6.0),
public [`ace-core==0.6.0`](https://pypi.org/project/ace-core/0.6.0/) package, separately released
`ace-reference-workspace-action==0.2.0` adapter, and public World Intelligence 0.10.0 proving
journey are bound by the
[Measured Intelligence release evidence](docs/evidence/measured-intelligence-v0.6.0-release-closeout-v1.md).
A checkout-free environment installed the public artifacts and reproduced seven World-owned
matched evaluations, historical replay, and an explicit governed rejection that applied nothing
and changed no effective state.

The [0.5.0 GitHub Release](https://github.com/augmented-cognition-engine/core/releases/tag/v0.5.0),
public [`ace-core==0.5.0`](https://pypi.org/project/ace-core/0.5.0/) package, and independent World
P2C2 journey remain the passed Reasoning into Action boundary for its documented single-host
topology with explicitly trusted constructor-supplied adapters. They remain bound by the
[Reasoning into Action release evidence](docs/evidence/reasoning-into-action-v0.5.0-release-readiness.md).

The 0.4.x line remains the passed Governed Cognition milestone. Patch releases 0.4.3 and 0.4.4
hardened canonical cognition persistence and task-source timestamp compatibility, and the public
0.4.4 artifact remains the exact GC1 external-consumer receipt below.

The [0.4.4 GitHub Release](https://github.com/augmented-cognition-engine/core/releases/tag/v0.4.4)
and public `ace-core==0.4.4` package expose proposal teaching, semantic-diff inspection, authorized
human review, materially attributed fresh use, exact receipt inspection, lifecycle governance, and
the canonical persistence fixes required by a real external consumer. The
[GC1 public external-consumer evidence](docs/evidence/gc1-public-external-consumer-v1.md) binds the
tag, trusted publication, artifact hashes, clean public-index runtime, independent Market journey,
restart durability, failure controls, and released conformance coverage. The earlier
[builder-surface evidence](docs/evidence/gc1-public-builder-surface-v1.md) remains the exact
point-in-time receipt for 0.4.2. GI1 remains the packaging, contract, and publication outcome first
passed by 0.4.0.

The [0.4.1 GitHub Release](https://github.com/augmented-cognition-engine/core/releases/tag/v0.4.1)
and public `ace-core==0.4.1` package remain the exact Core identity used by the completed GI2
cross-domain falsification below; that historical receipt is not rewritten to substitute the newer
release.

Domain neutrality remains a falsification result rather than a packaging property: a single-domain
abstraction always looks neutral from inside that domain. **GI2 is now passed** through the public
Core 0.4.1, World Intelligence 0.8.0, and Market Intelligence 0.6.0 artifacts. The tagged World
journey reproduces its frozen Case and Brief identities, while a clean public-index environment
compiles and activates both inert packs through unchanged platform APIs, retires Market, and proves
the World binding remains active and byte-identical. The exact receipts and limitations are in the
[GI2 public cross-domain evidence](docs/evidence/gi2-public-cross-domain-falsification-v1.md).

The broader governed-cognition builder-experience gate is now passed. An independent Market
Intelligence consumer reproduced proposal, human disposition, exact revision use, restart
persistence, retirement failure, and attribution against a running public-package deployment.
Released Core conformance tests cover rejection, revision, rollback, expiry, unavailable
dependencies, effectiveness classification, and non-selectable revision/retirement proposals.
**GC1** is therefore passed in 0.4.x.

The release remains bounded to the documented single-node topology and trusted in-process Python
extensions. It does not establish hostile-code isolation, distributed operation, general
real-world causal accuracy, autonomous learning, a general model of reality, or general beneficial
impact.

ACE provides graph-grounded, calibrated foresight. It projects conditional consequences of
decisions, exposes the mechanisms and uncertainty behind them, observes what actually happens,
and uses resolved forecasts to improve later reasoning. F1 freezes the bounded contract; the
agent-only L1 v7 study establishes beneficial impact against every required control within its
frozen executable-workload scope, without claiming general real-world benefit.

## Public release plan

The [ACE Public Roadmap](https://github.com/orgs/augmented-cognition-engine/projects/1) is the live
operational view of this plan. Each release has one public milestone issue that owns its product
promise, included scope, acceptance gate, dependencies, and explicit boundaries. The Project shows
whether that issue is **Now**, **Next**, or **Later**; this file remains the canonical narrative and
maps each release to the granular outcome ledger below.

Release targets describe sequence, not calendar commitments. ACE follows three release rules:

1. one minor release makes one major product promise;
2. that promise requires a reproducible public acceptance journey, declared limitations, and
   reconciled evidence before it is complete;
3. patch releases harden a published promise without introducing a backward-incompatible public
   contract or silently widening authority.

| Target | Public milestone | Lane | Granular outcome map | Public issue |
|---|---|---|---|---|
| 0.2.x | State Engine stabilization | **Maintenance** | Inherits the passed R0, R1, R2, R3, R4, R5, R6, R7, G1, IA-R1, I1, I2, I3, F1, L1, K1, K2, and K3 foundation; patch work is limited to compatibility, migration, recovery, observability, reliability, security, and documentation hardening | [#1](https://github.com/augmented-cognition-engine/core/issues/1) |
| 0.3.x | Productized State | **Maintenance** | PS1 passed in 0.3.1 through the K1–K3 spine, R1/R4 onboarding pattern, G1 and IA-R1 inspection, I1–I3 receipts, and E1 extension/governance boundary; later patches are compatible hardening only | [#2](https://github.com/augmented-cognition-engine/core/issues/2) |
| 0.4.x | Governed Cognition | **Passed** | GI1 passed in 0.4.0; GC1 passed against public 0.4.4 through the supported teach, inspect, approve, use, measure, revise, rollback, and retire lifecycle, an independent Market consumer, restart durability, attribution, and failure controls | [#3](https://github.com/augmented-cognition-engine/core/issues/3) |
| 0.5.0 | Reasoning into Action | **Passed** | T1 and B1 pass for bounded attributable action under the explicit single-host, trusted-adapter topology; I1 authority receipts govern the execution-adapter slice | [#37](https://github.com/augmented-cognition-engine/core/issues/37) |
| 0.6.0 | Measured Intelligence | **Passed** | Public Core 0.6.0 and World 0.10.0 artifacts reproduce exact useful/harmful/unproven classification, matched leakage-bounded controls, durable replay, and proposal-only governance under product-owned criteria; SI4 remains a broader future outcome | [#38](https://github.com/augmented-cognition-engine/core/issues/38) |
| 0.7.0 | Intelligence Builder Foundation | **Passed** | Public Core 0.7.0 composes 0.7A–0.7E, AC1–AC7, and AM0–AM3; all release checks, trusted publication, public clean-install reproduction, and independent World/Market consumer gates passed | [#39](https://github.com/augmented-cognition-engine/core/issues/39) |
| 0.8.0 | Intelligence OS Realignment | **Passed** | Public Core 0.8.0 unifies the governed resource plane and Atrium experience over the released Builder, composition, memory, action, and outcome foundations; independent World/Market proofs reproduce the same contract without domain branches | [#40](https://github.com/augmented-cognition-engine/core/issues/40) |
| 0.9.0 | Single-user Intelligence Builder | **Passed** | The personal install → choose → connect → map → watch → first cited Brief → continuous update journey is implemented through Atrium, with local ownership, recovery, and World/Market proof | [#41](https://github.com/augmented-cognition-engine/core/issues/41) |
| 1.0.0 | Personal Intelligence Operating System | **Candidate** | Freezes and hardens the complete supported single-user loop, public contracts, packaging, upgrades, security, recovery, and reproducible domain experiences without requiring collaboration or managed infrastructure; publication and clean public-artifact reproduction remain | [#42](https://github.com/augmented-cognition-engine/core/issues/42) |

### Parallel domain validation

The release spine above belongs to `ace-core`. Domain applications version independently in sibling
repositories and consume the same public Core + Intelligence contracts. Their product releases do
not change the ACE Core version, and their domain nouns, connectors, and policies do not move into
this repository.

World Intelligence and Market Intelligence are the current validation targets. Together they must
exercise materially different entities, sources, detectors, personas, epistemic policies, and
decision cadences. A failure found by either domain returns to Core only as a domain-neutral
contract, compiler, conformance, governance, or runtime requirement. A domain-specific workaround
does not become platform code.

This work proceeds in parallel with Core releases. A domain demonstration does not promote
an ACE capability by itself; promotion still requires reproducible public evidence, declared
limitations, and reconciliation in this roadmap. The Market GC1 journey contributes to the passed
Core outcome only because it is composed with the public builder surface and released Core
conformance evidence.

### 0.2.x — State Engine stabilization

Public promise: keep the first major State Engine release dependable while the next product
milestone is built.

- Preserve the bounded single-node R7, F1, and K1–K3 contract across fresh invocations and runtime
  restarts.
- Harden compatibility, migrations, recovery, diagnostics, documentation, reliability, and
  security without changing the product promise.
- Keep failures and degraded states visible and preserve the published thin-tool boundary.

Release gate: required quality, security, compatibility, and publication checks pass, and no patch
introduces a backward-incompatible public contract. New promises or authority move to a later minor
release.

### 0.3.x — Productized State

Public promise: a builder can install ACE, add an extension, provide real product context, inspect
composed state, make and correct a decision, and observe the correction materially influence later
reasoning after a restart.

- Turn the passed K1–K3 bounded capability into the obvious supported product journey rather than
  requiring a builder to understand ACE internals.
- Integrate G1 and IA-R1 inspection with I1 decisions and corrections, I2 deliberation attribution,
  and I3 material-use receipts.
- Use the passed E1 packaging, compatibility, isolation, security, restart, and conformance
  boundary without placing domain logic in Core.
- Publish a clean-environment example, failure behavior, supported limits, and reproducible
  acceptance evidence.

Release gate: **passed in ace-core 0.3.1.** The public extension-first journey proves
classification, composition, evidence, provenance, decision capture, correction, persistence, and
later material use through supported interfaces. The tagged artifacts passed the release matrix,
trusted publication, exact registry-hash comparison, and a clean public-index installation. See the
[Productized State release evidence](docs/evidence/productized-state-v0.3.1-release-readiness.md).

### 0.4.x — Governed Cognition

Public promise: builders can run governed Intelligence and teach and revise a reasoning system
through a supported lifecycle: propose, inspect, approve, version, use, measure, revise, roll back,
or retire.

**Delivered in 0.4.0 — GI1:**

- Put Core + Intelligence in one install behind enforced public dependency boundaries.
- Compile independently versioned, inert JSON Domain Packs with fail-closed diagnostics and
  packaged conformance seams.
- Admit an exact authorized LIVE source through bounded connector composition, then derive Shift,
  Signal, attention disposition, and governed Brief resources with provenance and exact replay.
- Preserve the eleven-tool MCP surface, naked-kernel startup, schema v175, and single-node limits.

**Passed in 0.4.x — GC1:**

- Make the canonical E1 teaching lifecycle obvious through supported public interfaces.
- Create inspectable proposals from authorized tasks, corrections, conversations, and documents.
- Use immutable revisions, durable approval receipts, provenance, explicit authority, bounded
  discovery, and exact use attribution.
- Support rejection, rollback, supersession, conflict, expiry, disablement, and retirement without
  erasing history or enabling silent self-modification.

The public `ace-core==0.4.2` release added a thin `ace cognition` builder workflow over the existing
authenticated HTTP boundary. Releases 0.4.3 and 0.4.4 hardened canonical persistence and
task-source timestamp compatibility discovered by the external-consumer journey. Public 0.4.4 now
passes the complete supported gate: an independent consumer taught a reusable capability through
public interfaces, a human inspected and governed the change, fresh invocations materially used
the exact approved revision with complete attribution before and after restart, and retirement
failed a distinct later required use closed. Released conformance tests cover the remaining
rejection, revision, rollback, expiry, unavailable-dependency, and effectiveness branches.

Release gate: **passed.** GI1 and GC1 are passed and the 0.4.x milestone is complete. The subsequent
0.5.0 T1/B1 gate also passed under its separately recorded boundary.

### 0.5.0 — Reasoning into Action

Public promise: ACE can reason under explicit authority and carry an approved decision into
bounded, attributable action.

- Complete the T1 guarantees needed for writable work: cancellation, replay identity, restart
  recovery, portability, resource reporting, and explicit topology boundaries.
- Advance B1 through declared capabilities, permissions, preconditions, approvals, results,
  failures, recovery, review, repair, and promotion.
- Keep product tools and domain actions in domain applications, connectors, or explicitly trusted
  extensions while Core enforces neutral authority and execution contracts.
- Require MAKE artifacts to pass independent SHIP security, testing, observability, operations,
  and scale gates before promotion.

Release gate: **passed.** The public-artifact journey proceeds from admitted evidence to governed
reasoning, an authorized Decision, exact human review, bounded action, honest terminal receipt,
separate verification, and separate promotion. Released conformance covers denial, timeout,
cancellation, duplicate request, partial effect, restart uncertainty, linked repair, and exact
replay. ACE makes no unrestricted-autonomy claim.

The first bounded packet was
[T1A durable cancellation](docs/design/t1a-durable-cancellation-work-packet-v1.md). It hardens the
existing negotiated extension-invocation seam around immutable duplicate handling and restart
receipt reconciliation. T1A's historical candidate record is composed into the passed public
0.5.0 closeout; it did not independently authorize external effects.

The second bounded packet was
[T1B execution limits and timeout receipts](docs/design/t1b-execution-limits-work-packet-v1.md).
It adds a neutral declared wall-clock limit, process-local deadline enforcement, and explicit
terminal resource reporting to direct and trusted-extension tasks. Its historical candidate record
is composed into the passed public 0.5.0 closeout. It does not claim CPU or memory enforcement,
distributed deadlines, or remote execution.

The third bounded packet was
[T1C durable task attempt and replay](docs/design/t1c-durable-task-replay-work-packet-v1.md). It
predeclares a domain-neutral attempt identity on every new task receipt and lets failed or
restart-degraded direct tasks create one deterministic linked successor from their persisted
request. T1C's historical candidate evidence is composed into the public 0.5.0 closeout. Its
[candidate evidence](docs/evidence/t1c-durable-task-replay-candidate-v1.md) binds public review,
final-head CI, exact merge identity, real restart, full regression, and an isolated wheel probe.
T1C does not claim
distributed exactly-once execution, remote-worker recovery, provider-stream continuation,
remote execution, or external-effect compensation.

The fourth bounded packet was
[B1A governed action execution](docs/design/b1a-governed-action-execution-work-packet-v1.md). It
introduces a domain-neutral public candidate service that binds an authorized Decision to one
effect-free adapter plan, persists admission before execution, and records success, failure,
partial effect, timeout, cancellation, or restart uncertainty without allowing a Domain Pack to
execute code. B1C supplies the independently released adapter proof, and B1A's historical candidate
record is composed into the public 0.5.0 closeout. Its
[candidate evidence](docs/evidence/b1a-governed-action-execution-candidate-v1.md) binds public review,
final-head CI, exact merge identity, the focused contract suite, full regression, naked-kernel
boundary, an isolated local-wheel probe, and the merged B1B fresh-process restart proof. It does not
claim cross-process or distributed
exactly-once effects, compensation, container equivalence, remote execution, or complete SHIP
promotion beyond the documented bounded lifecycle.

The fifth bounded packet was
[B1B durable action restart and host composition](docs/design/b1b-durable-action-restart-work-packet-v1.md).
It adds exact constructor-only host registration, the supported SurrealDB composition path, strict
database-JSON replay, and a fresh-process proof that an admitted action with no terminal receipt is
never implicitly executed again. B1B's historical candidate record is composed into the public
0.5.0 closeout.
Its [candidate evidence](docs/evidence/b1b-durable-action-restart-candidate-v1.md) binds the exact
reviewed head and merge, all six final-head CI gates, full regression, real SurrealDB fresh-process
replay, and isolated installed-wheel host composition. It does not claim
distributed exactly-once effects, compensation, an independently packaged adapter, action
review/repair/promotion by itself.

The sixth bounded packet was
[B1C independent action adapter](docs/design/b1c-independent-action-adapter-work-packet-v1.md). It
adds a separately buildable trusted reference distribution over the public action-adapter contract
and one real create-only workspace export. The adapter is excluded from the Core wheel, imports no
host internals, performs no discovery, and must be constructed and registered explicitly by exact
artifact identity. Its
[candidate evidence](docs/evidence/b1c-independent-action-adapter-candidate-v1.md) binds the focused
conformance and host-registration checks, independently built and installed wheels, public review,
all six final-head CI gates, and the exact merge identity. Public 0.5.0 supplies the released-
artifact closeout. B1C
does not provide arbitrary
filesystem access, safe untrusted code, distributed exactly-once effects, compensation, action
review/repair/promotion by itself.

The seventh bounded packet was
[B1D action review, repair, and promotion](docs/design/b1d-action-review-repair-promotion-work-packet-v1.md).
It adds an additive reviewed lifecycle around the unchanged B1A admission and terminal contracts:
an authenticated human judgment binds the exact effect-free plan and Core authorization before
execution; post-effect verification stays separate from promotion; and repair is a new linked
successor rather than a silent retry. Unknown effects are ineligible for repair, and success never
promotes itself. B1D's historical candidate record is composed into the public 0.5.0 closeout. Its
[candidate evidence](docs/evidence/b1d-action-review-repair-promotion-candidate-v1.md) binds the
exact reviewed head and merge, all six final-head CI gates, full regression, real SurrealDB
review-to-promotion restart, and independently built wheels. It does not provide compensation, distributed
exactly-once effects, remote execution, or untrusted code.

The bounded release closeout is frozen in the
[0.5.0 Reasoning into Action release work packet](docs/design/reasoning-into-action-v0.5.0-release-work-packet-v1.md).
The supported topology is one ACE host, one durable store, and explicitly trusted in-process
adapters; portability means an independently packaged adapter consumes only the public contract,
not distributed execution. World Intelligence P2C2 supplies the external Decision-to-reviewed-
action journey. The exact tag, PyPI Core package, separate adapter release assets, checkout-free
World reproduction, hashes, and boundaries are recorded in the
[0.5.0 release evidence](docs/evidence/reasoning-into-action-v0.5.0-release-readiness.md). T1, B1,
and 0.5.0 are therefore **passed** for the explicit single-host topology.

### 0.6.0 — Measured Intelligence

Public promise: reasoning revisions are promoted, rejected, rolled back, or retired because of
measured outcomes rather than intuition alone.

- Link outcome identity and provenance to decisions, actions, cognition revisions, forecasts, and
  observed results.
- Compare unchanged and revised behavior under matched conditions and report quality, latency,
  cost, failures, degraded states, and important limitations.
- Carry the passed bounded L1 method into product-owned outcome journeys without broadening its claim
  or substituting material influence for beneficial impact.
- Advance F2 only when demonstrated evidence or user need justifies broadening the F1 consequence
  contract.
- Add matched, leakage-bounded evaluation for situational orientations and attention signals,
  including citation correctness, contradiction recall, source and time coverage, calibration,
  detection delay, false-alert rate, revision stability, and useful, harmful, or unproven impact.

Release gate: a public evaluation journey traces a governed change from proposal through measured
result and explicit promotion, rejection, rollback, or retirement. ACE does not self-certify
improvement or optimize outside product-defined outcomes and authority.

The first bounded
[Measured Intelligence kickoff packet](docs/design/measured-intelligence-v0.6.0-kickoff-work-packet-v1.md)
is a **candidate**, not a release closeout. It freezes domain-neutral criterion, conditions,
attribution, Decision, reviewed Action, Outcome, evaluation, and non-effective proposal identities;
the [candidate evidence](docs/evidence/measured-intelligence-v0.6.0-kickoff-candidate-v1.md) records
useful, harmful, and unproven fixture coverage plus exact real-store restart replay. The stacked
[proposal disposition packet](docs/design/measured-impact-proposal-disposition-work-packet-v1.md)
adds an exact authorized accept/reject Core Decision that always remains `no_action`. World
P2C3/P2C4 compose the source-checkout candidate over recorded official public data: the frozen
structural criterion remains `useful` and proposes `promote`, while a separate authorized reviewer
rejects broader promotion without rewriting history or changing effective state. The stacked
[observed-result provenance packet](docs/design/measured-impact-observed-result-provenance-work-packet-v1.md)
lets a product criterion require an exact immutable result behind each Outcome score. World
P2C5-P2C10 now exercise citation correctness, contradiction attention, detection delay, revision
stability, forecast scoring, and a materially different BLS correction family while keeping every
proposal non-effective. An independent Market candidate reproduces the unchanged neutral contract.
The bounded
[release-convergence packet](docs/design/measured-intelligence-v0.6.0-release-convergence-work-packet-v1.md)
owns installed-artifact and combined-gate evidence.
The follow-on
[merge-candidate audit](docs/design/measured-intelligence-v0.6.0-merge-candidate-audit-work-packet-v1.md)
binds a World direct-to-live-main integration candidate and presents bounded F1/F3/F5 owner choices.
The subsequent
[#49 hardening packet](docs/design/measured-intelligence-v0.6.0-issue49-hardening-work-packet-v1.md)
implements bounded F1 and F5, now merged in exact Core `main`. The subsequent
[merged-source convergence packet](docs/design/measured-intelligence-v0.6.0-merged-source-convergence-work-packet-v1.md)
rebuilds the exact Core and World wheels, reproduces the public World `useful` and independent
Market `unproven` results, and retains proposal-only authority. Issue #49 now records F1 and F5 as
complete against merged Core and explicitly re-dates unresolved, unwaived F3 to `2026-11-05` under
documented containment. The public Core 0.6.0 and World 0.10.0 artifacts, trusted publication,
cache-free installation, seven World-owned matched evaluations, governed rejection/no-action
disposition, historical replay, required checks, and exact boundaries are composed in the
[public release closeout](docs/evidence/measured-intelligence-v0.6.0-release-closeout-v1.md).
The 0.6.0 milestone is therefore **passed**. This advances only the bounded SI4 evaluation slice;
SI4's broader two-domain situational-orientation gate remains not ready.

### 0.7.0 — Intelligence Builder Foundation

Public promise: a builder can connect authorized sources and reach a useful first briefing and
monitoring loop without building intelligence infrastructure or understanding ACE's internal
layers. Third parties can still build, test, distribute, and operate the portable Domain Packs,
connectors, and trusted extensions underneath that experience.

- **0.7A — stable contract/compiler/conformance:** the PR #100 candidate freezes machine-readable
  generated Domain Pack schemas, compatibility, deterministic conformance, activation refusal, and
  lifecycle policy.
- **0.7B — Connect:** the Connection Agent proposes supported source options, exact permission and
  scope, provider-free fixture profiles, and resumable blocked/retry state without owning transport
  or credentials. Its bounded implementation and evidence gates are frozen in the
  [0.7B Connect work packet](docs/design/intelligence-builder-connect-v0.7.0-work-packet-v1.md).
- **0.7C — Map:** the Ontology Agent proposes an editable, cited concept model—entities, aliases,
  relations, attributes, terminology, and exclusions—with explicit confidence and no silent
  mutation. Its bounded implementation and evidence gates are frozen in the
  [0.7C Map work packet](docs/design/intelligence-builder-map-v0.7.0-work-packet-v1.md).
- **0.7D — Watch + Brief:** the Intelligence Agent proposes monitors, materiality, audiences,
  routing, and cadence; the Briefing Agent produces the cited first briefing with uncertainty,
  disagreement, omissions, and why each item matters. Its bounded candidate contract and evidence
  gates are frozen in the
  [0.7D Watch + Brief work packet](docs/design/intelligence-builder-watch-brief-v0.7.0-work-packet-v1.md).
- **0.7E — Activate + prove:** the Activation Agent compiles approved proposals through 0.7A,
  shows exact permission/effect scope, obtains approval, activates with exact receipts, proves
  restart/update/feedback behavior, and reproduces unchanged public APIs across independent World
  and Market consumers.

The exact cumulative Core source and published artifact reproduce the five-stage journey together
with AC7 policy admission and AM3 authorized Context Manifest consumption. World PR #21 provides
merged public external activation conformance; a separately maintained private B2B Market
deployment reproduces the same neutral activation and restart boundary without moving its nouns,
data, or policy into Core. See the historical
[cumulative integration candidate](docs/evidence/cumulative-core-v0.7-integration-acceptance-v1.md)
and the public
[0.7.0 release closeout](docs/evidence/intelligence-builder-foundation-v0.7.0-release-closeout-v1.md).

The cumulative contracts, state machine, authority boundary, and demo gate are frozen in the
[Intelligence Builder onboarding sequence](docs/design/guided-intelligence-bootstrap-v0.7.0-work-packet-v1.md).

The parallel Agent Composition candidate closes its finite governance sequence with AC7:
[composition-policy admission](docs/design/composition-policy-admission-ac7-work-packet-v1.md)
consumes exact inert AC6 evaluation/proposal evidence, requires independent review and current Core
authority, and uses the existing governed-state owner for an exact compare-and-swap policy head.
Composition implementation freezes after AC7 pending the same cumulative integrated 0.7 acceptance;
this candidate does not by itself complete 0.7 or open an AC8+ implementation sequence.

The 0.7 milestone does not absorb connector SDK breadth, extension sandboxing, telemetry,
heterogeneous-evidence breadth, workspace UI, collaboration, marketplace, managed service, or
release-ecosystem closeout. Those remain separately dispatched follow-ons at the appropriate
milestone after the cumulative A–E journey is accepted.

Release gate: one clean builder journey reaches a source-grounded first Brief without hand-authored
pack material or required knowledge of ACE internals; independent packs, connectors, and trusted
extensions pass their applicable public compatibility and conformance checks; requested source
scope and authority are visible before activation; and failures remain isolated and diagnosable.

### 0.8.0 — Intelligence OS Realignment

Public promise: ACE presents one coherent Intelligence Operating System. Governed data enters,
evidence-grounded intelligence is derived, people and machines consume it downstream, and
attributable outcomes return through governed feedback. Reasoning is a governed component of that
lifecycle rather than the product category. Atrium is its permission-aware intelligence dashboard
and human control plane.

The bounded delivery sequence is:

- **0.8A — architecture and compatibility:** freeze the canonical lifecycle, ownership map,
  compatibility seams, work packets, and golden acceptance journey.
- **0.8B — runtime realignment:** enforce Core, Intelligence, Domain Pack, adapter/plugin, and
  application ownership in code while preserving supported contracts through declared migration.
- **0.8C — unified intelligence resources:** expose one public resource plane for sources, entity
  state, Observations, Signals, Shifts, Cases, Briefs, monitors, subscriptions, decisions, actions,
  outcomes, feedback, provenance, uncertainty, revisions, Context Manifests, and memory lineage.
- **0.8D — Atrium experience:** rebuild the optional dashboard and control plane around attention,
  intelligence review, investigation, semantic diffs, governed controls, and Ask ACE over the same
  durable resources. The first briefing-first implementation is tracked in the
  [Atrium Intelligence experience work packet](docs/design/atrium-intelligence-experience-v0.8.0-work-packet-v1.md).
- **0.8E — cross-domain proof:** run a public World AI Command Center and the parallel Market
  Intelligence command center through unchanged Core + Intelligence APIs.
- **0.8F — release acceptance:** pass compatibility, migration, restart, installed-artifact,
  accessibility, entitlement, degraded-state, and two-domain publication gates.

Canonical current architecture and product surfaces replace the octopus, arm-growth, MAKE/SHIP,
partner-team, committee-first, product-manager-toolbox, and Living Product Graph system-category
narratives. Historical evidence and supported compatibility identities are not rewritten.

The complete packet, compatibility map, landing order, stop conditions, and signature demonstration
are frozen in the
[Intelligence OS Realignment work packet](docs/design/intelligence-os-realignment-v0.8.0-work-packet-v1.md).

Release gate: World and Market complete the same governed evidence-to-outcome lifecycle without a
domain branch in Core or Intelligence; Atrium and a machine interface consume the same public
durable intelligence; supported compatibility and migrations are tested; and accessibility,
authority, entitlement, restart, failure, and degraded behavior pass. Atrium remains optional and
does not become a second source of truth.

### 0.9.0 — Single-user Intelligence Builder

Outcome state: **passed in the cumulative 1.0 candidate.** The product journey below is complete;
its public-artifact reproduction is performed as part of the 1.0 release gate rather than as a
separate 0.9 publication.

Public promise: one person can install ACE, choose World, Market, or Custom Intelligence, connect a
few authorized sources, describe what they need to understand, and receive a useful cited first
Brief that keeps updating—without learning ACE architecture or hand-authoring a Domain Pack.

- Make Atrium the coherent local command center for choosing intelligence, connecting sources,
  approving the proposed concept model and watches, reviewing the first Brief, asking grounded
  follow-up questions, and correcting relevance.
- Compose the released Connect, Map, Watch, Brief, Activate, Agent Composition, and Agent Memory
  foundations into one resumable product journey with honest progress, blocked, retry, partial, and
  degraded states.
- Keep source permissions and credential scope visible before use. Store secrets outside Domain
  Packs and never let onboarding silently grant source, delivery, or effect authority.
- Turn admitted evidence into decision-readable intelligence: what changed, why it matters, how the
  conclusion was derived, when it happened, what remains unknown, and which citations support each
  material claim.
- Keep the personal intelligence system useful after the first Brief through Signals, Shifts,
  Opportunities, Briefs, monitors, Ask ACE, and governed feedback that can improve relevance without
  silently changing authority.
- Prove local ownership through restart continuity plus documented export, deletion, backup, and
  restore for the supported single-node deployment.
- Reproduce the same public journey through the World AI Command Center and Market Intelligence,
  while Custom Intelligence remains a generic onboarding path rather than a hidden third ontology.

Release gate: from clean public artifacts, one documented local launch reaches a cited first Brief
through the guided Atrium flow, resumes safely across restart, admits a later source change as an
append-only update, answers a grounded follow-up through the same resources, and preserves exact
source, permission, lineage, uncertainty, and feedback receipts. World and Market pass without a
domain branch in Core or Intelligence. Failure, recovery, export, deletion, accessibility, package,
schema, security, and upgrade checks pass for the documented single-user topology.

The bounded contract and acceptance matrix are frozen in the
[0.9 work packet](docs/design/single-user-intelligence-builder-v0.9.0-work-packet-v1.md).

### 1.0.0 — Personal Intelligence Operating System

Outcome state: **candidate.** Implementation and bounded source/evaluation evidence are complete;
trusted publication plus a clean, public-artifact-only acceptance receipt remain before `passed`.

Public promise: ACE is a stable, open, provider-neutral Intelligence Operating System that lets one
person build living, source-grounded, inspectable, governable, and adaptive intelligence without
rebuilding the infrastructure underneath it.

- Stabilize the public contracts required by the single-user lifecycle: source connections,
  identity and time, observations, entity state, Signals, Shifts, Opportunities, Cases, Briefs,
  monitors, Ask ACE context, feedback, memory, decisions, optional reviewed actions, outcomes,
  Domain Packs, connector boundaries, authority, provenance, and receipts.
- Preserve domain-neutral Core and Intelligence layers, separately versioned product-owned Domain
  Packs and connectors, optional Atrium and machine surfaces, portable durable intelligence, and
  explicit human authority.
- Publish and reproduce clean installation, supported upgrade, compatibility, migration, backup,
  restore, export, deletion, security, governance, deprecation, degraded-state, and
  breaking-change policies for the documented local deployment.
- Demonstrate the complete continuously updating loop through public World and Market products,
  plus the generic Custom Intelligence onboarding path, using released artifacts rather than source
  checkouts or prepared UI-only data.
- Freeze a reproducible install-to-first-Brief demonstration and an operator-readable limitations
  statement suitable for independent users and downstream builders.

Release gate: every contract needed by the supported single-user journey is reproducible from
public artifacts; a clean user can install ACE and a Domain Pack, launch Atrium, reach and reopen a
cited first Brief, observe a later update, inspect why it changed, ask a grounded question, correct
relevance, and recover owned state. The release has no hidden mutation, implicit execution
authority, provider lock-in, domain ontology in Core, or organizational ownership requirement.

Multi-user collaboration, organizations and teams, tenant isolation, shared workspaces, delegated
administration, multiplayer approvals, managed hosting, marketplace operation, hostile-extension
sandboxing, and distributed execution are explicit
[post-1.0 work](https://github.com/augmented-cognition-engine/core/issues/152). They do not gate the
first stable personal Intelligence OS.

## Continuous situational intelligence sequence

**Product promise:** ACE can maintain living, source-grounded orientation over any bounded subject
a user is authorized to examine. The same neutral loop can support personal, organizational,
market, geopolitical, scientific, technical-system, or other pack-defined intelligence:

```text
observe → detect material change → update bounded state → compare claims, commitments, and behavior
→ identify reactions and consequences → orient → watch what could change the conclusion
```

This is a cross-cutting product outcome, not a new domain in Core or Intelligence and not an
additional promise silently added to an earlier minor release. It uses the passed GI1, K1–K3, and
I1–I3 foundations and is delivered incrementally through governed cognition, measured
intelligence, the Intelligence Builder Foundation, the Intelligence OS experience, and the
single-user Intelligence Builder. The public SI1–SI4 outcome and acceptance work are tracked in
[issue #47](https://github.com/augmented-cognition-engine/core/issues/47).

### SI1. Reproducible situational orientation

- Accept a bounded subject, as-of question, optional entities and time window, and explicit
  evidence, context, latency, and cost budgets.
- Produce an immutable, versioned orientation with a concise bottom line; supporting,
  contradicting, superseding, missing, and unavailable evidence; alternative explanations;
  uncertainty and causal limits; falsifiers and watch conditions; source-level citations and deep
  links; and an exact diff from the prior orientation.
- Preserve the answer that was justified at each historical cutoff. Later evidence creates a new
  revision and never leaks backward into an as-of answer or rewrites the prior receipt.
- Keep statement, observation, belief, hypothesis, simulation, action, reaction, and outcome
  identities distinct and prove which items materially affected the orientation.

### SI2. Standing investigations and accountable change

- Make a question a durable case rather than a one-off prompt: subject, owner, scope, current
  orientation, open unknowns, competing hypotheses, falsifiers, watch conditions, cadence,
  authority, and revision history remain inspectable across restarts.
- Represent statements and commitments with actor and role, modality, target, magnitude, timeframe,
  preconditions, exceptions, and a declared observable test. Represent legal, administrative,
  financial, enforcement, operational, and other domain-defined actions separately.
- Assess commitment against observed behavior as `aligned`, `partially_aligned`, `contradicted`,
  `too_early`, `unverifiable`, or `insufficient_evidence`, with the exact interpretation and
  evidence frozen in the assessment receipt.
- Build reaction dossiers that distinguish attributed verbal response, policy or legal response,
  market repricing, physical or operational behavior, and mere temporal co-movement. A reaction or
  sequence edge alone never establishes causation.

### SI3. Heterogeneous evidence and source governance

- Let connectors map source-specific records into Intelligence's Observation contract while Core
  preserves temporal identity, durable state, provenance, authority, and receipts. Domain Packs
  declare how structured measurements, time series, locations, tracks, events, market-contract
  states, data vintages, revisions, units, precision, coverage, gaps, and degraded conditions are
  interpreted.
- Track epistemic role, proximity, domain expertise, primary versus commentary status, ownership,
  syndication or common origin, and historical performance without collapsing source trust into one
  universal scalar. Repeated reporting from one origin must not masquerade as independent
  corroboration or dominate bounded retrieval.
- Preserve source spans and access-controlled deep links while enforcing consent, entitlement,
  quotation, redaction, retention, deletion, export, and audit policy. Licensed or sensitive content
  may ground an answer without being reproduced to an unauthorized reader.
- Keep source translation in bounded connectors and domain ontologies, aliases, detector
  configuration, materiality rules, and specialized trust policy in Domain Packs. Intelligence
  owns domain-neutral resolution, delta, scoring, routing, synthesis, and feedback mechanisms; Core
  owns scope, identity, time, durable state, provenance, reasoning, receipts, authority, and failure
  semantics.

### SI4. Attention and measured orientation quality

- Maintain explicit, correctable attention policy over subjects, entities, geography, horizons,
  novelty, magnitude, confidence, source diversity, time sensitivity, acceptable interruption, and
  delivery channels. Personalization must remain attributable and must not silently broaden access.
- Trigger work from material state change or a standing watch condition rather than raw ingestion
  volume. Rank signals using user relevance and expected consequence while penalizing duplication,
  weak coverage, stale evidence, and unresolved conflict; silence must remain a valid result.
- Record why an orientation or alert was generated, suppressed, grouped, delayed, delivered,
  dismissed, corrected, or used, including the evidence and policy revisions involved.
- Evaluate historical questions only with frozen as-of cutoffs and test citation correctness,
  primary-source and contradiction coverage, calibration, detection delay, false-alert rate,
  revision stability, analyst action, and beneficial, harmful, or unproven effect against declared
  controls.

Acceptance gate: external Domain Packs from at least two materially different scopes reproduce the
same Core + Intelligence lifecycle without embedding their domain ontology in either layer. Given
a bounded as-of question, each journey ingests mixed evidence, produces a source-linked
orientation, distinguishes claims from observed behavior and reactions, exposes contradictions and
unknowns, establishes a standing watch, emits or suppresses a material-change signal under explicit
policy, survives a runtime restart, and updates by append-only revision when later evidence arrives.
Evaluation must include future-information leakage controls, duplicated-origin and entitlement
negative controls, causal-overclaim checks, alert-quality measures, and declared limits; it does
not claim omniscience, general real-world causal accuracy, or universal benefit.

## Intelligence Operating System architecture sequence

```mermaid
flowchart LR
    PACK["Domain Packs<br/>ontology · detectors · personas · policy"] --> INTEL
    CONN["Connectors<br/>authorized sources · bounded translation"] --> APP
    SURF["Domain applications<br/>API · CLI · MCP · Atrium"] --> APP
    HUMAN["Human authority<br/>approve · reject · correct · promote"] --> CORE
    APP["Application services<br/>LIVE ingress · bridge · Brief · feedback"] --> INTEL
    APP --> CORE
    INTEL["Intelligence<br/>observe · detect · route · synthesize"] --> CORE
    CORE["Reasoning kernel<br/>classify · compose · deliberate · synthesize"] <--> STATE
    STATE["Durable intelligence<br/>Living Product Graph · State Engine"] --> ORIENT
    ORIENT["Situational orientation<br/>investigate · compare · explain"] --> DECIDE
    HUMAN --> ORIENT
    ORIENT --> WATCH["Standing investigations<br/>watch · suppress · alert"]
    WATCH --> CORE
    DECIDE["Inspectable decision"] --> MAKE
    HUMAN --> MAKE
    MAKE["MAKE<br/>bounded implementation"] --> SHIP
    SHIP["SHIP<br/>security · tests · operations · scale"] --> OUTCOME
    OUTCOME["Observed outcome"] --> LEARN
    LEARN["Measure · calibrate · propose revision"] --> STATE
```

## Product phases

| Phase | Product question | Current position | Outcomes | Release target |
|---|---|---|---|---|
| 1. Reasoning foundation | Can ACE reliably reason, remember, and explain what happened? | **Passed** | R0–R7, G1, IA-R1, I1–I3, and F1 passed | through 0.2.x |
| 2. Product state | Can a product maintain grounded state and reason about change and consequences? | **Passed** | K1–K3, E1, and PS1 passed; Productized State is published in 0.3.1 | 0.3.x |
| 3. Governed cognition and intelligence | Can a builder run domain-neutral Intelligence and teach the product how to reason without silent self-modification? | **Passed** | GI1 passed in 0.4.0; GC1 passed against public 0.4.4 and an independent Market consumer | 0.4.x |
| 4. Reasoning into action | Can an approved decision safely produce attributable work? | **Passed** | T1 and B1 passed in 0.5.0 for the bounded single-host, trusted-adapter topology | 0.5.0 |
| 5. Measured intelligence | Can ACE prove when retained intelligence or a capability helped, hurt, or remains unproven? | **Passed for the public 0.6.0 boundary** | Product-owned matched evaluation, exact attribution, durable replay, and proposal-only governance are public; F2 and general benefit remain not ready | 0.6.0 |
| 6. Intelligence Builder foundation | Can any product connect sources, specialize, operate, and retain ownership of ACE intelligence? | **Passed for the bounded public 0.7.0 contract** | 0.7A–0.7E, AC1–AC7, and AM0–AM3 compose in the public artifact; 0.9 completes the coherent single-user product journey | 0.7.0 and 0.9.0 |
| 7. Intelligence OS experience | Can people and machines consume and govern one coherent intelligence loop without learning ACE internals? | **Passed for the bounded public 0.8.0 contract** | One authorized resource plane and Atrium consume the Builder, AC7, AM4, action, outcome, and feedback foundations; World and Market reproduce the same domain-neutral contract | 0.8.0 |
| 8. Continuous situational intelligence | Can ACE maintain a trustworthy, changing orientation over any bounded subject without making its domain ontology part of Core or Intelligence? | **GI1 substrate passed; product outcome not ready** | SI1–SI4 require GI1, independent Domain Packs, K1–K3, I1–I3, E2, L1, F2 where justified, and the single-user workspace, recovery, and ownership slices required by the 1.0 gate | cross-cuts 0.4.x–0.9.0; complete by 1.0.0 |

## Immediate dispatch

### Completed milestone: 0.6.0 Measured Intelligence

The public Core 0.6.0 and World Intelligence 0.10.0 artifacts close the bounded release gate. Exact
product-owned criteria can classify matched attributed evidence as useful, harmful, or unproven;
missing attribution, mismatched conditions, unavailable or post-cutoff outcomes, duplicate
evidence, divergent replay, interrupted append, and denied authority fail closed. World reproduces
the complete recorded public-data journey through a non-effective proposal and a separately
authorized rejection/no-action Decision. The
[release closeout](docs/evidence/measured-intelligence-v0.6.0-release-closeout-v1.md) binds the
tags, artifacts, hashes, workflows, public installation, replay, limitations, and issue #49
disposition.

Exit condition: **passed.** This milestone remains the public evidence foundation consumed by
0.7.0; it is not reopened or silently widened by the later Builder release.

### Completed milestone: 0.7.0 Intelligence Builder Foundation

The public Core 0.7.0 artifact composes the stable Domain Pack contract with the bounded Connect,
Map, Watch, Brief, and Activate agents; AC1–AC7 composition governance; and AM0–AM3 authorized
memory. World and private B2B Market consumers passed the unchanged activation boundary. Trusted
publication and a checkout-free public install reproduced the package's Intelligence Operating
System identity and exact eleven-tool MCP surface. The
[release closeout](docs/evidence/intelligence-builder-foundation-v0.7.0-release-closeout-v1.md)
binds the tag, artifacts, hashes, workflow, consumer gates, installation, limitations, and rollback
boundary.

Exit condition: **passed.** Its successor, 0.8.0 Intelligence OS Realignment, is now passed below.
The bounded A–F sequence is recorded in the
[0.8 work packet](docs/design/intelligence-os-realignment-v0.8.0-work-packet-v1.md). 0.7 did not
silently claim the complete 0.9 single-user experience or the stable 1.0 contract.

### Completed milestone: 0.8.0 Intelligence OS Realignment

Public Core 0.8.0 presents one coherent Intelligence Operating System over the existing governed
foundation. The public resource plane exposes authorized, point-in-time Sources, Connections,
Observations, Entity state, Signals, Shifts, Cases, Briefs, Monitors, Subscriptions, Agents,
Decisions, Actions, Outcomes, Feedback, memory, and provenance with explicit partial and degraded
states. Atrium consumes those same resources as a briefing-first workspace and remains optional and
non-authoritative. World and Market independently reproduce the evidence-to-outcome loop through
unchanged Core + Intelligence APIs.

Exit condition: **passed.** The release preserves schema head v177, exactly eleven MCP tools,
inert Domain Packs, proposal-only feedback, explicit read/effect authority, and the bounded
single-node trusted-adapter topology. The 0.9 single-user journey is complete in the cumulative
1.0 candidate; trusted publication and clean public-artifact reproduction are the remaining release
gates.

### Completed technical prerequisite: bounded Product State outcomes

K1, K2, and K3 are `passed` for the bounded single-node contract. The independent Fjord Operations
extension and frozen acceptance receipt complete the required product-builder journey:

1. install ACE and a product extension without modifying Core;
2. ingest and replay product-scoped temporal evidence;
3. inspect supported, contested, provisional, superseded, and unknown belief state;
4. review transition hypotheses and compare action, no-action, and alternative rollouts;
5. use the bounded result in a durable ACE decision;
6. capture a later outcome and reconcile the original rollout without rewriting it;
7. preserve identity, provenance, authority, isolation, degraded behavior, and restart continuity;
8. publish the supported surface, limitations, clean-user journey, and acceptance receipt.

Exit condition: **passed.** A builder can give a product a bounded State Engine through the extension
boundary, and the
[K1-K3 product-journey evidence](docs/evidence/state-engine-k1-k3-product-journey-v1.md) records the
clean install, exact receipts, restarts, failure semantics, limitations, and unchanged eleven-tool
surface. E1 passed separately through the exact ace-core 0.3.0 release evidence; this journey does
not promote T1, distributed guarantees, or real-world causal accuracy.

### Completed milestone: 0.3.x Productized State

The Fjord Operations K1–K3 receipt proves the bounded capability and independent extension journey.
E1 separately passed with ace-core 0.3.0. The new Productized State receipt now proves the integrated
implementation through authenticated ingestion, supported CLI orchestration, read-only receipt
inspection, v171 schema zero, a v168→v171 upgrade, real restarts, correction, and later material use.

The completed 0.3.x implementation sequence was:

1. freeze one obvious extension-first golden path that begins with product value and progressively
   reveals deeper ACE surfaces;
2. bind the passed E1 packaging, compatibility, isolation, security, restart, and conformance
   evidence to that journey;
3. connect G1 and IA-R1 inspection to I1 decisions and corrections, I2 deliberation attribution,
   and I3 material-use receipts without adding domain logic to Core;
4. publish clean-environment installation, configuration, recovery, degraded-state, and limitation
   guidance for a product builder;
5. run the required compatibility, security, release, and public-artifact acceptance matrix; and
6. reconcile the evidence, milestone issue, Project lane, capability maturity, and this roadmap
   before publication.

Items 1–6 passed. The integrated journey is recorded in
[Productized State evidence](docs/evidence/productized-state-journey-v1.md), and the exact release,
artifact, trusted-publication, registry, and clean-install receipts are recorded in the
[0.3.1 release evidence](docs/evidence/productized-state-v0.3.1-release-readiness.md). The acceptance
runner finding that real SurrealDB product-scope binding returned empty inspection families was
corrected with typed record IDs and retained as a regression.

Exit condition: **passed.** The [0.3.x milestone](https://github.com/augmented-cognition-engine/core/issues/2)
passes its public acceptance gate, and the versioned public release is reproducible from published
artifacts. K1–K3 and E1 remain bounded passed inputs; PS1 is the passed productized outcome.

### Completed release: 0.4.0 governed Intelligence foundation

GI1 is `passed`. ACE 0.4.0 packages Core + Intelligence together, enforces their dependency
boundary, compiles inert Domain Packs, admits bounded LIVE sources, derives exact replayable
Intelligence resources, synthesizes governed Briefs, preserves the naked kernel, and publishes the
same eleven MCP tools. The release, trusted PyPI workflow, and clean public-index installation are
linked from the current release checkpoint above.

This does not close GC1, SI1–SI4, or any domain product. It establishes the shared substrate those
outcomes consume.

### Governed Intelligence platform substrate — P1 and P2 evidence (0.4.1 public closeout)

GI1 passed with the packaged `ace-core` 0.4.0 distribution described above. `ace-core` 0.4.1 then
published the P1/P2 platform evidence records that extend the same substrate. The individual
records below remain immutable point-in-time documents and retain their original
candidate/local wording; the later
[GI2 public cross-domain evidence](docs/evidence/gi2-public-cross-domain-falsification-v1.md)
binds them to the public release line rather than rewriting their historical status.

The independent `augmented-cognition-engine/domain-world-intelligence` repository is now tagged,
released, and published as `ace-domain-world-intelligence==0.8.0`. The separate Market repository
is likewise public as `ace-domain-market-intelligence==0.6.0`. Their tagged and installed-artifact
journeys close the publication dependency that kept GI2 open.

The 0.4.1 substrate was delivered in two ordered packet sequences:

**P1 — the first governed LIVE spine**, from one authorized live source through a routed Brief and
a closed feedback loop:

- [P1C1 declarative source-mapping](docs/evidence/platform-p1c1-declarative-source-mapping-v1.md) —
  the closed source-mapping declaration module and PREPARED interpreter that turns one compiled
  Pack IR, mapping ID, and host snapshot into one content-addressed Observation and Entity Snapshot.
- [P1C2 governed LIVE source ingress](docs/evidence/platform-p1c2-governed-live-source-ingress-v1.md)
  — atomic admission of one authenticated LIVE capture into a source-acquisition receipt, snapshot,
  Observation, and Entity Snapshot.
- [P1D1 shift-triggered PREPARED Brief](docs/evidence/platform-p1d1-governed-routed-brief-v1.md) —
  one routed Signal turned into one canonical PREPARED Brief over its Shift and Entity Snapshots.
- [P1E governed PREPARED feedback](docs/evidence/platform-p1e-governed-feedback-v1.md) — a Decision
  and later Outcome closing the loop back into an append-only Intelligence policy-state commit.
- [P1F governed LIVE intelligence bridge](docs/evidence/platform-p1f-governed-live-intelligence-bridge-v1.md)
  — the first bounded operational spine end-to-end: LIVE Observation → Entity Snapshot → Shift →
  Signal → route → governed LIVE Brief.

**P2A — the separate JSON-only World Domain Pack**, compiling through unchanged `ace-core`:
seven conformance tests, five fail-closed mutations, and co-installation alongside the Market
Domain Pack. P2A is consumer-repository conformance evidence recorded in the
Domain-World-Intelligence repository, not in `ace-core`, so no separate Core evidence record was
ported into this archive for it. Its public `v0.8.0` tag and package now make that consumer proof
independently reproducible.

**P2 — Case-bound governance and domain-neutral falsification packets**, run against the second,
independent World Intelligence domain:

- [P2B categorical detection](docs/evidence/platform-p2b-categorical-detection-v1.md),
  [P2B immutable Case closure](docs/evidence/platform-p2b-immutable-case-closure-v1.md), and
  [P2B independent resource admission](docs/evidence/platform-p2b-independent-resource-admission-v1.md)
  — domain-neutral categorical transition detection, immutable Case closure, and independently
  admitted PREPARED resources.
- [P2C Case-bound governed Brief](docs/evidence/platform-p2c-case-bound-governed-brief-v1.md) —
  Brief synthesis bound to an open Case, closing packet `WI-CR-005`.
- [P2D per-statement epistemic status](docs/evidence/platform-p2d-per-statement-epistemic-status-v1.md)
  — packet `WI-CR-002`, domain-neutral per-statement epistemic status.
- [P2E derivation-family independence](docs/evidence/platform-p2e-derivation-family-independence-v1.md)
  — packet `WI-CR-003`, domain-neutral derivation-family independence.
- [P2F supersession-impact projection](docs/evidence/platform-p2f-supersession-impact-projection-v1.md)
  — packet `WI-CR-004`, domain-neutral supersession-impact projection.
- [P2G owner-governed monitoring](docs/evidence/platform-p2g-owner-governed-monitoring-v1.md)
  — local candidate closing the implementation side of packets `WI-CR-007` and `WI-CR-008` with
  append-only owner lifecycle and explicitly requested sensing-window receipts. Public artifact
  publication and independent consumer replay remain open, so SI1–SI4 do not advance here.

Two earlier local checkpoints record intermediate 0.3.x/0.4.x-era work and are preserved for history
rather than as current status: the
[context manifest and code-context checkpoint](docs/evidence/context-manifest-code-context-v1.md)
and the
[Productized State golden-journey checkpoint](docs/evidence/productized-state-golden-journey-v1.md).
Both predate the P1/P2 sequence above and are superseded by it.

These point-in-time records did not move an outcome by themselves. Their former publication gate
has now passed: Core 0.4.1, World 0.8.0, and Market 0.6.0 are public, the tagged World conformance
suite passes, and the clean public-index two-domain activation and retirement-isolation journey
passes. GI2 is therefore reconciled to `passed`; GI1 and GC1 are passed, while SI1–SI4 remain
bounded future outcomes.

### 1. Completed governed-cognition builder journey

E1 passed for ace-core 0.3.0 and establishes one canonical cognition model. GI1 passed in 0.4.0 and
establishes the governed Intelligence substrate. GC1 makes the cognition lifecycle an obvious
supported public experience:

```text
teach → propose → inspect → approve → use → measure → revise or retire
```

The accepted dependency sequence was:

1. preserve the converged recipe and legacy `Skill`/`Job`/`Phase` migration behavior;
2. create inspectable learning proposals from tasks, corrections, conversations, and documents;
3. approve immutable recipe, instrument, or framework revisions with durable human receipts;
4. support rejection, rollback, supersession, conflict, expiry, and retirement without deleting
   history;
5. discover and load only relevant approved cognition within explicit context and cost budgets;
6. record the exact cognition revisions considered, selected, used, omitted, or unavailable.

Exit condition: **passed.** The public 0.4.4 builder and independent Market consumer journeys prove
that an extension can teach ACE a reusable reasoning capability, a human can govern the change,
and fresh invocations can materially use the exact approved revision across restart without
widening the thin MCP contract. The exact receipts and composed negative-path coverage are in the
[GC1 public external-consumer evidence](docs/evidence/gc1-public-external-consumer-v1.md).

### 2. Preserve the passed bounded action runtime

T1 and B1 passed in 0.5.0 for one ACE host, one durable store, and explicitly trusted in-process
adapters. Cancellation, replay identity, restart recovery, resource reporting, explicit review,
and attributable terminal effects are now inputs to later outcome work rather than prerequisites
still awaiting dispatch. Future runtime packets may harden isolated or remote adapters, but must
keep distributed guarantees, untrusted execution, and implicit model authority outside the passed
boundary until independently demonstrated.

Exit condition: **passed for the documented 0.5.0 topology and preserved as a release input.**
Approved reasoning produces attributable reviewed work without giving a model implicit or
unbounded execution authority.

### 3. Productize bounded learning-impact evidence

L1 is `passed` for the bounded executable-workload claim. Its first leakage-bounded retrospective
probe and the agent-only v5 result remain negative; v6 remains formally invalid because one ACE case
failed the frozen I3 field-level lineage check. The independently seeded v7 correction replicate
froze that already-required check before collection, completed 192 decisions across 48 eligible
clusters on one matched live route, and passed last-observation persistence, naïve/base-rate, and
matched model-only with all three cluster-adjusted 95% lower bounds above zero. The claim does not
extend to humans, customers, providers, external products, or general real-world benefit. I3
material influence alone still does not establish benefit. F2 remains gated until demonstrated
evidence or user need justifies a broader consequence contract.

Exit condition: ACE can state, with reproducible evidence, when a capability helped, hurt, or
remains unproven and can propose—not silently apply—a revision or retirement.

### 4. Grow the domain, connector, extension, and product-surface ecosystem

GI1 establishes the inert Domain Pack compiler, external conformance seams, and bounded connector
composition. E1 establishes N-1 compatibility, isolation and security review, recovery/effect
semantics, operability, and conformance evidence for the exact ace-core 0.3.0 trusted in-process
Python-extension boundary. E2 can now add pack distribution, connector lifecycle, product-owned
telemetry, scheduled work, IDEs, messaging, webhooks, and remote execution adapters. H1 later adds
tenancy, shared authority, portability, recovery, and managed operation without transferring
ownership of a user's durable intelligence.

Atrium evolves alongside these phases as a read-first view of state, reasoning, approvals, actions,
outcomes, and proposed cognition changes. It gains no new write or execution authority merely by
rendering them.

### 5. Validate continuous situational intelligence through external domains

SI1–SI4 now begin from the passed GI1 substrate rather than asking each vertical to rebuild its own
entity, Shift, Signal, Brief, Case, provenance, and feedback machinery. The validation sequence is:

1. freeze domain-neutral contracts for standing investigations, orientation revisions, reaction
   dossiers, attention policies, subscriptions, and attention receipts; the P2G local candidate
   now covers owner lifecycle and bounded sensing-window receipts without claiming scheduled work;
2. keep structured measurements, time series, geospatial tracks, market state, source-origin
   clustering, entitlement, privacy, and source-specific materiality in Domain Packs or connectors;
3. run World Intelligence through the public compiler and application seams using public-issue,
   event, claim, correction, and source-independence semantics;
4. run Market Intelligence through the same seams using competitor, product, customer, narrative,
   campaign, and go-to-market semantics;
5. accept platform changes only when both can express the need as a domain-neutral contract,
   compiler, conformance, governance, or runtime requirement;
6. connect governed domain policy to evaluation before exposing standing watches, alerts, case
   files, timelines, maps, or revision controls through supported surfaces; and
7. reconcile SI1–SI4 evidence into the 0.4.x–0.9 milestone gates without changing a domain release
   into an ACE Core capability claim.

Exit condition: the SI1–SI4 acceptance gate is reproducible from public artifacts across at least
two materially different external domain packages, with privacy, entitlement, future-leakage,
duplicated-origin, causal-overclaim, restart, degraded-state, and attention-quality evidence. Until
then, continuous situational intelligence is a planned cross-cutting outcome, not a supported
general-intelligence claim.

## Outcome ledger

| ID | State | Public outcome | Dependency / acceptance evidence |
|---|---|---|---|
| R0 | passed | Publish `ace-core` 0.1.0 through a credential-free release path | GitHub Release, PyPI release, successful OIDC workflow, and public-index install verified |
| R1 | passed | Make first use effortless and outcome-led for product builders | [Clean-trial evidence](docs/evidence/r1-onboarding-evidence.md) covers isolated macOS and Linux journeys, recovery, and `ace doctor` |
| R2 | passed | Ship the focused 0.1.1 onboarding, packaging, and documentation release | [Release evidence](docs/evidence/r2-release-evidence.md) covers installs, artifacts, CI, tag, trusted publication, GitHub Release, and public-index verification |
| R3 | passed | Validate provider setup, authentication, diagnostics, and degraded behavior | [Provider evidence](docs/evidence/r3-provider-validation.md) covers the supported matrix, live subscription routes, degraded behavior, and current-main CI |
| R4 | passed | Publish a reproducible product-builder golden-path demonstration | [Golden-path evidence](docs/product-builder-golden-path.md) proves a decision, human correction, restart, later material use, and provenance through supported surfaces |
| R5 | passed | Ship ace-core 0.1.2 inspectability and foresight | [R5 release evidence](docs/evidence/r5-release-readiness.md) records artifacts, regressions, migration/restart health, publication, provenance, and public installation |
| R6 | passed | Ship ace-core 0.1.3 attributable deliberation and experimental extension invocation | [R6 release evidence](docs/evidence/r6-release-readiness.md) records boundaries, regressions, publication, provenance, and public installation |
| R7 | passed | Ship ace-core 0.2.0 State Engine | [R7 release evidence](docs/evidence/r7-release-readiness.md) records architecture, migrations, regressions, scale, merge/tag identity, GitHub Release, trusted PyPI publication, provenance, and public installation |
| G1 | passed | Promote the read-only Living Product Graph into a supported inspectable journey | [G1 evidence](docs/evidence/g1-living-product-graph-evidence.md) proves the bounded, deterministic, assertion-backed read contract and strict no-write boundary |
| IA-R1 | passed | Define the read-only information architecture for inspecting ACE state | [IA-R1 evidence](docs/evidence/ia-r1-product-map.md) establishes the operator hierarchy, provenance, uncertainty, failures, identity, and no-write/no-execution authority |
| I1 | passed | Make decisions, evidence, corrections, approvals, and outcomes inspectable | [Decision and correction receipts](docs/decision-correction-receipts.md) prove stable identity, disposition, provenance, isolation, redaction, and restart continuity |
| I2 | passed | Make deliberation and synthesis attributable without exposing hidden chain-of-thought | [I2 evidence](docs/evidence/i2-attributable-deliberation-evidence.md) proves selection, bounded contributor artifacts, disagreement, synthesis lineage, failure behavior, and restart continuity |
| I3 | passed | Make retained-intelligence use and its decision effect inspectable | [I3 evidence](docs/evidence/i3-intelligence-use-evidence.md) proves retrieval/use distinctions, exact decision deltas, controls, failure cases, and restart continuity |
| F1 | passed | Freeze the honest contract for graph-grounded calibrated foresight | [F1 evidence](docs/evidence/f1-foresight-evidence.md) proves the bounded forecast, observation, resolution, scoring, comparator, and non-causal contract |
| K1 | passed | Maintain grounded temporal state over large product-scoped knowledge bases | [K1-K3 product evidence](docs/evidence/state-engine-k1-k3-product-journey-v1.md) adds clean extension install, temporal ingestion/replay, exact counts/lineage/isolation, five belief meanings, supported v168 migrations, restarts, and a supported guide to the prior scale/readiness evidence |
| K2 | passed | Model inspectable world dynamics and state-transition hypotheses | [K1-K3 product evidence](docs/evidence/state-engine-k1-k3-product-journey-v1.md) proves an extension-owned product hypothesis with mechanism, preconditions, horizon, uncertainty, evidence/counterevidence challenge, review, stale behavior, and explicit causal limits |
| K3 | passed | Simulate, compare, and reconcile consequences of possible actions | [K1-K3 product evidence](docs/evidence/state-engine-k1-k3-product-journey-v1.md) proves action/no-action/alternative comparisons, durable decision/I3/promotion receipts, immutable outcome reconciliation, correction supersession, real restart/interruption recovery, later material use, and honest failure bounds |
| PS1 | passed | Make the passed State Engine an obvious supported extension-first product journey | [Productized State evidence](docs/evidence/productized-state-journey-v1.md) passes authenticated adapter discovery/ingestion, `ace state` orchestration, integrated G1/IA-R1 and I1–I3 receipt inspection, v171 schema-zero, v168→v171 upgrade, restarts, correction, and later material use; the [0.3.1 release evidence](docs/evidence/productized-state-v0.3.1-release-readiness.md) binds the exact tag, official CI, trusted PyPI publication, matching registry hashes, and clean public-index installation |
| GI1 | passed | Ship the governed Intelligence foundation as one installable distribution with inert Domain Pack compilation and governed LIVE seams | [ace-core 0.4.0](https://github.com/augmented-cognition-engine/core/releases/tag/v0.4.0) packages Core + Intelligence, the inert Domain Pack compiler, LIVE source ingress, the LIVE bridge, Brief synthesis, exact replay, external conformance seams, schema v175, unchanged eleven-tool MCP, trusted PyPI publication, and clean public-index installation. This is a packaging, contract, and publication outcome; the domain-neutrality claim it previously carried moved to GI2 |
| GI2 | passed | Prove the Intelligence foundation is domain-neutral through an independent, publicly reproducible second-domain falsification | [GI2 public cross-domain evidence](docs/evidence/gi2-public-cross-domain-falsification-v1.md) binds public Core 0.4.1, World 0.8.0, and Market 0.6.0 artifacts. The tagged World suite passes 81 tests and reproduces `case:412426eee708d56f6bda931ccf9e5d8b` and `brief:25d8232c9bfa27050bdcb160fb75f06c`; a clean public-index install compiles and activates both packs through unchanged APIs, then retires Market without changing the active World binding. This is domain-neutral substrate evidence, not SI1–SI4 completion or a claim of general real-world accuracy |
| GC1 | passed | Make governed cognition an obvious supported teach, inspect, approve, use, measure, revise, and retire journey | [GC1 public external-consumer evidence](docs/evidence/gc1-public-external-consumer-v1.md) composes the public 0.4.4 artifact identity, independent Market prepare/restart/resume/retire journey, exact material-use attribution, fail-closed post-retirement request, and released Core coverage for rejection, revision, rollback, expiry, unavailable dependencies, and effectiveness |
| T1 | passed | Strengthen task recovery, replay, portability, cancellation, and resource reporting | [ACE 0.5.0 release evidence](docs/evidence/reasoning-into-action-v0.5.0-release-readiness.md) composes TP1 and T1A–T1C with exact public artifacts, a separately installable public-contract adapter, checkout-free external reproduction, negotiated cancellation, declared deadlines, terminal resource receipts, attempt identity, and restart-safe linked replay. The pass is bounded to one host and one durable store; remote workers, distributed recovery, cross-process ordering, and broader CPU/memory enforcement remain outside the supported topology |
| E1 | passed | Stabilize the extension and governed-cognition boundary | [E1 release evidence](docs/evidence/e1-governed-cognition-release-v1.md) binds the canonical E1-A–G lifecycle to ace-core 0.3.0, exact current/N-1 and mixed-package evidence, public artifacts and fresh install, deployment inventory, independent AI security acceptance, and release-owner countersignature; the pass is limited to trusted in-process extensions and is not a human penetration test or certification |
| L1 | passed | Use resolved conditional forecasts to improve later reasoning and decision quality | [L1 evidence](docs/evidence/l1-foresight-impact-evidence.md) preserves the negative retrospective probe and v5/v6 failures, then records the preregistered v7 correction replicate: all 192 cases and 48 clusters were eligible, and ACE passed persistence, naïve/base-rate, and matched model-only under the frozen all-controls interval rule; the claim is limited to the executable benchmark |
| B1 | passed | Carry approved decisions through attributable implementation, review, repair, and promotion | [ACE 0.5.0 release evidence](docs/evidence/reasoning-into-action-v0.5.0-release-readiness.md) binds I1 authority to an effect-free plan, exact human review, durable admission, bounded trusted-adapter execution, honest terminal states, separate verification, linked repair, separate promotion, exact replay, and an independent World consumer. It does not claim unrestricted autonomy, compensation, distributed exactly-once effects, remote execution, or untrusted-code isolation |
| F2 | not ready | Broaden consequence types where product evidence justifies the complexity | Bounded L1 evidence now exists; F2 still requires demonstrated product need and its own consequence-contract evidence without reopening F1 |
| H1 | not ready | Support secure collaboration and managed operation without transferring ownership of durable intelligence | Requires tenancy, portability, authority, and recovery guarantees |
| E2 | not ready | Grow the provider-neutral Domain Pack, connector, extension, telemetry, and execution-adapter ecosystem | Requires GI1 and E1 conformance plus stable distribution, compatibility, permission, and lifecycle policy |
| SI1 | not ready | Produce reproducible, source-linked situational orientation over any bounded authorized subject | GI1 is passed; remaining work requires a versioned orientation contract, historical as-of isolation, explicit uncertainty and causal limits, deep-link and omission receipts, restart evidence, and materially different external Domain Pack journeys |
| SI2 | not ready | Maintain standing investigations and inspectable claim, commitment, action, reaction, and revision history | Requires SI1, governed pack-owned assessment policy, durable investigation/watch identity, exact assessment tests and dispositions, reaction-type separation, correction and supersession, and no causal promotion from sequence alone |
| SI3 | not ready | Govern heterogeneous evidence, source independence, privacy, entitlement, and structured deep links | Requires GI1/E2 source and telemetry contracts plus pack- or connector-owned measurement/time-series/geospatial/market semantics, origin and syndication lineage, access and retention policy, bounded retrieval controls, and H1 guarantees for shared or sensitive operation |
| SI4 | not ready | Deliver material-change attention and measure orientation and alert quality | Requires SI1–SI3, explicit correctable interest/watch policy, attributable generation and suppression receipts, delivery controls, leakage-bounded historical evaluation, alert-quality measures, and product-owned outcome evidence under L1/F2 limits |

## Product and architecture guardrails

- ACE remains provider-neutral; an LLM is an inference resource, not the owner of the loop.
- Core and Intelligence remain domain-neutral; product-specific vocabulary and policy live in
  Domain Packs, while source translation and actions live in bounded connectors or explicitly
  trusted extensions.
- Models may propose; deterministic code and explicit human authority own identity, activation,
  consequential execution, and promotion.
- Evidence, belief, hypothesis, simulation, decision, action, and observation remain distinct.
- Statement, commitment, observed action, attributed reaction, and outcome remain distinct; a
  narrative source establishes what it reported, not that its account is true.
- As-of reasoning may use only evidence available under the frozen historical cutoff; later data or
  revisions cannot leak backward into an earlier orientation.
- Source volume is not source independence. Syndicated, commonly owned, or derivative reports do
  not become corroboration merely because they appear in multiple artifacts.
- Retrieval is not use, material influence is not benefit, and correlation is not causation.
- Hidden chain-of-thought, private prompts, credentials, and unrestricted transcripts remain outside
  public receipts.
- The supported thin MCP boundary remains exactly eleven tools until a separate compatibility
  decision explicitly changes it.
- Durable intelligence remains product-scoped, portable, inspectable, and owned by its user.
- Attention policy cannot widen evidence access, and sensitive or licensed evidence cannot be
  reproduced outside its consent, entitlement, retention, and redaction policy.
- New capability claims require reproducible evidence, declared limits, and roadmap reconciliation.

## Follow and contribute

Follow the live [ACE Public Roadmap](https://github.com/orgs/augmented-cognition-engine/projects/1)
for operational status. Repository issues should state the user outcome, scope, acceptance
evidence, dependencies, and maturity impact without including credentials, vulnerability details,
customer information, private agreements, or unpublished business and release plans.

The roadmap is a projection of ACE's product state, not a substitute for evidence. Implemented code,
a demonstration, or a design note advances no outcome by itself.
