ACE World Intelligence

ACE World Intelligence is an inert Domain Pack and reference solution for making sense of a changing public issue. It separates admitted records, attributed claims, corroboration, disputes, ACE inference, unknowns, and conditional scenarios instead of presenting one opaque summary as truth.

This repository is a consumer of the public ACE Core + Intelligence distribution. It does not own a reasoning runtime, graph, state store, authority system, detector engine, or feedback loop.

• Distribution: ace-domain-world-intelligence 0.9.0 release candidate — JSON-only, data-only, inert
• Requires: Python 3.12 and ace-core>=0.5.0,<0.6
• Status: release candidate. The complete P2C2 journey passes against public ace-core==0.5.0 and the public reference-action adapter without a Core checkout. The World v0.9.0 tag and PyPI publication remain the final release gate. The current public release remains 0.8.0. See the 0.9.0 release packet.

What you install, and what you get

The product is split into three layers, and this repository owns only the third.

Layer	Distribution	What it is
ACE Core	ace-core (public on PyPI, 0.5.0)	The runtime: identity, graph, immutable records, temporal validation, lineage, admission, replay, and governed bounded action.
ACE Intelligence	shipped with ACE Core	The domain-neutral contracts: the pack compiler, activation binding, detection, Case, Brief synthesis, and epistemic-status validation that packs are checked against.
World Intelligence Domain Pack	ace-domain-world-intelligence (this repository)	JSON declarations only — ontology, source mapping, detection, personas, synthesis, epistemic-status vocabulary, and frozen conformance fixtures.

Installing the Domain Pack adds data, not behaviour. The wheel contains no .py, no entry points, and no install hooks; nothing in it executes on install or import. ACE Core compiles those JSON modules and does the reasoning. If you want to sense a live official source, you additionally install a separately reviewed connector — see Connector boundary.

Install

After the v0.9.0 release is published, install it on Python 3.12 with either command below. The release candidate has already been built and tested against public ace-core==0.5.0.

With uv:

uv add "ace-domain-world-intelligence==0.9.0"

With pip:

pip install "ace-domain-world-intelligence==0.9.0"

Either command also brings in ace-core>=0.5.0,<0.6, which is already public. It does not bring in the Federal Register connector; that is a deliberate boundary, not an omission.

Resolve the pack data from the installed distribution:

import json
from importlib.resources import files

manifest = json.loads(
    files("domain_packs.world_intelligence").joinpath("manifest.json").read_text(encoding="utf-8")
)
print(manifest["metadata"]["pack_id"])  # world_intelligence

Develop from a source checkout

To develop the pack, or to run the acceptance harnesses and the P2C connector packet, work from a checkout alongside an ACE Core checkout or installation:

# from the root of this checkout
export REPO="$PWD"
export ACE=/path/to/ace-core
export PYTHONPATH="$REPO:$REPO/adapters/federal_register_source/src:$ACE"
export PY="$ACE/.venv/bin/python"

PYTHONPATH above includes the connector source so that the P2C packet runs. Drop that middle entry and the P2C modules skip rather than fail.

Product loop

authorized public sources
  → attributable Observations and entity state
  → event, actor, institution, issue, policy, claim, and source graph
  → meaningful Signal or Shift
  → cited reality Brief
  → user correction or disposition
  → governed Outcome and feedback

Current milestone

P2A proved that a materially different, JSON-only World Intelligence pack compiles through the unchanged ACE pack compiler (pack_ir:683de57a71669814e507d07d65a109db, seven conformance tests).

P2B freezes the golden 72-hour public-issue scenario: the synthetic, hermetic, redistributable meridia_reservoir_release_72h packet. It pins eight timestamped source records across four provenance families (including two syndicated copies and a publisher correction), a nineteen-entity graph exercising all eleven relation types, an official status change, four material categorical shifts plus one numeric shift, one runtime-routable signal, and an exact Reality Brief whose seventeen statements carry all seven epistemic statuses. Nine negative vectors fail closed, from missing attribution through divergent replay.

The additive P2B PREPARED replay now compiles and activation-binds detection v1alpha2, admits all eight source records as PREPARED Observations, reproduces all five Shifts, emits only the intended four Signals, and resolves all four persona routes. The claim-corroboration Shift is represented through ACE's generic resource-set admission without inventing a Signal. The frozen scenario and default 0.1.0 pack identities remain unchanged.

The replay also freezes those developments into ACE's public immutable Case contract. Four routed Signals plus the non-routed corroboration Shift form one five-member Case that transitively binds the complete 28-resource scenario closure. World supplies the case type and purpose; ACE owns the identity, temporal validation, lineage resolution, admission, and replay.

An additive Case-bound packet now consumes ACE's public CaseBriefSynthesisService over that exact Case. It admits the routed derivations through ACE's durable PREPARED ledger without duplicating any source record, derives one compatible template and persona scope from the four exact attention receipts, freezes all 26 closure resources as Core context, and emits one governed, grounded, atomically persisted, deterministically replayable Reality Brief that carries the Case in lineage: brief:8fb3173069eca502652b1c9c004c92e6. WI-CR-005 is closed.

Per-statement epistemic status (WI-CR-002) and derivation-family independence (WI-CR-003) are now closed through public, domain-neutral ACE contracts. World declares its seven-label vocabulary; ACE validates each statement against its exact supports and proves that corroborated spans at least two admitted derivation families. The Ledger report and the independent Basin gauge satisfy that rule, while Coastal Wire and Harborview collapse into the Ledger root despite being different publishers. The durable projection discloses the exact root-to-member partition used by the proof. Supersession-impact enumeration (WI-CR-004) is now closed too, so no public-platform contract request remains open. When a record is superseded, ACE enumerates exactly what depended on it, directly and transitively, and appends that answer as an additive immutable record. Both frozen corrections are exercised: the Ledger correction reaches 11 resources and 9 Brief claims, the Order supersession reaches 7 resources and 5 claims, and each projection discloses the resources it found unaffected so the boundary is visible rather than inferred. Impact means dependency, not falsehood — the prior Brief keeps its exact identity, replays byte-identically, and is never rewritten.

P2C adds the first official-source sensing proof without mutating that frozen pack. A separate, JSON-only activation pack (pack_ir:1847032fc5301bba9b6f85d3d091400d) maps one exact Federal Register document, while a separately versioned, transport-injected adapter validates the exact source, artifact, URI, network attestations, and closed payload. ACE then admits one acquisition receipt, source snapshot, visibly LIVE Observation, LIVE Entity Snapshot, and admission receipt as one atomic transaction. Exact replay and fresh-service restart replay perform no second capture.

The conformance transport is a recorded, network-free response from the reviewed official API URI; it proves the governed LIVE contract and deterministic admission, not that the test suite performed a live network request. FederalRegister.gov is explicitly labeled as not the official legal edition, and the corresponding govinfo.gov PDF is retained as the official-format verification reference. No Signal, Shift, Brief, Decision, Outcome, feedback, delivery, publishing, persuasion, or external action is created.

P2C2 completes that sensing path across the Core + Intelligence + Domain boundaries. A new declarative monitor pack admits two exact FCC records — document 2026-15932 published August 6 and document 2026-16197 published August 7 — as successive LIVE snapshots of one stable monitor entity. Its configured categorical detector produces an official_publication_change Shift, routes an official_publication Signal, and invokes Core-governed reasoning to produce one LIVE Reality Brief with six claims and two exact citations. A named human Decision then authorizes only a create-only workspace export; a second exact human review precedes the effect, and separate verification and promotion receipts follow it. Replay performs neither a second reasoning call nor a second file effect.

This is a governed export proof, not autonomous publishing. The pack contains no executable code or action authority; the export is provided by Core's separately packaged reference adapter. The two source responses are exact official public records under recorded transport, so P2C2 proves the complete deterministic product journey but still does not claim network freshness at test time.

What the public World proof demonstrates

Generate a self-contained visual Reality Brief and its exact machine-readable backing data:

PYTHONPATH=/path/to/domain-world-intelligence:/path/to/ace-core \
  /path/to/ace-core/.venv/bin/python scripts/public_demo.py

The command writes artifacts/public-demo/index.html and demo-data.json. It runs the accepted independence and correction-impact harnesses, refuses to render if the pinned release proof drifts, and uses no external web assets.

It demonstrates four things, and only these:

1. Two publishers are not two sources. Coastal Wire and Harborview are different publishers, but both derive from the Ledger report and collapse into one derivation family. Only the Ledger + Basin pairing satisfies the Brief's two-family corroboration rule.
2. Every statement carries its own epistemic status. The seven-label World vocabulary is validated by ACE against each statement's exact supports, not asserted by the pack.
3. Corrections append rather than rewrite. Admitting the later Ledger correction produces a governed impact projection over 11 downstream resources and 9 Brief claims, and discloses the 16 resources it found unaffected. Impact means dependency, not falsehood.
4. The result is reproducible. The prior Brief keeps its exact identity and replays byte-identically, and the two artifacts are byte-identical across runs.

Exact public identities reproduced by the demo:

• Case: case:412426eee708d56f6bda931ccf9e5d8b
• Brief: brief:25d8232c9bfa27050bdcb160fb75f06c

The page is explicitly a synthetic PREPARED / FROZEN scenario, not a live news product. It does not monitor the news, and it takes no action of its own. See docs/releases/world-intelligence-public-demo-v0.7.0.md for the 0.7.0 release boundary and full identity list.

Connector boundary

This repository ships an inert Domain Pack. The Federal Register connector is a separately versioned executable artifact, ace-ext-world-federal-register-source 0.2.0, with its own review boundary:

• it is not a dependency of the Domain Pack, and no extra reintroduces it;
• installing ace-domain-world-intelligence never installs it;
• it is not published by this repository's release workflow, which builds and uploads the root sdist and wheel only;
• it contains no network client — it accepts only an injected, separately reviewed transport, and validates the exact artifact identity, source type, HTTPS URI, empty redirect chain, absence of credentials, exact HTTP 200 application/json, bounded strict JSON, globally routable address attestations, DNS-rebinding protection, and monotonic operation times;
• to exercise it, put it on the path explicitly. Omit it and the P2C modules skip rather than fail.

Rebuild the connector reproducibly:

cd adapters/federal_register_source
SOURCE_DATE_EPOCH=1735689600 uv build --wheel

A production host must supply and review a real transport that enforces address validation and rebinding protection throughout use. The shipped conformance material does not do that for you.

Verification

With $REPO, $ACE, $PYTHONPATH, and $PY exported as in Develop from a source checkout:

# Complete domain suite, including every frozen packet and the P2C2 product journey: 83 passed
export PYTHONPATH="$PYTHONPATH:$ACE/adapters/reference_workspace_action/src"
$PY -m pytest -q

# Connector fail-closed unit suite: 26 passed
$PY -m pytest adapters/federal_register_source/tests -q

# Individual acceptance harnesses
$PY scripts/p2a_compile_acceptance.py
$PY scripts/p2b_scenario_acceptance.py --negative
$PY scripts/p2b_prepared_replay.py
$PY scripts/p2b_case_brief.py
$PY scripts/p2b_status_case_brief.py
$PY scripts/p2b_independent_case_brief.py
$PY scripts/p2c_federal_register_live_acceptance.py

# Complete official-record -> Shift -> Signal -> Brief -> reviewed export journey
WORKSPACE=$(mktemp -d)
$PY -m scripts.p2c2_governed_reality_brief "$WORKSPACE"

The 0.9.0 release-candidate gates are reproducible through the locked environment, as CI does. The P2C2 action test runs when the independently packaged Core reference adapter is installed:

uv sync --frozen --no-install-project
uv run --no-sync python -m pytest                         # released + candidate-compatible gates
uv run --no-sync python -m pytest tests/test_release_contract.py  # publishable-identity gate
uv run --no-sync python -m pytest adapters/federal_register_source/tests  # connector: 26 passed

Verified totals as of 2026-08-10 with public ace-core==0.5.0 from PyPI and the independently packaged reference adapter from the Core v0.5.0 GitHub release: domain suite 83 passed, connector suite 26 passed. The public demo reproduces case:412426eee708d56f6bda931ccf9e5d8b and brief:25d8232c9bfa27050bdcb160fb75f06c, and its two artifacts are byte-identical across runs.

The exact identities, negative cases, and artifact proofs are recorded in docs/audits/world-intelligence-p2a-2026-08-06.md and docs/audits/world-intelligence-p2b-2026-08-06.md, with the interpreter and Case proof in docs/audits/world-intelligence-p2b-prepared-replay-2026-08-07.md and the governed Case-bound Brief proof in docs/audits/world-intelligence-p2b-case-brief-2026-08-07.md, the per-statement status proof in docs/audits/world-intelligence-p2b-status-case-brief-2026-08-07.md, and the independent-corroboration proof in docs/audits/world-intelligence-p2b-independent-case-brief-2026-08-07.md. The governed official-source admission proof is recorded in docs/audits/world-intelligence-p2c-federal-register-live-2026-08-07.md. The complete governed product-journey evidence is recorded in docs/audits/world-intelligence-p2c2-governed-reality-brief-2026-08-10.md.

Release-level scope, artifacts, and open gates are recorded in docs/releases/world-intelligence-p2c-v0.8.0.md, and version history in CHANGELOG.md.

Guardrails

• A publisher is not assigned a hidden universal truth score.
• Repetition and syndication are not independent corroboration.
• Claims retain attribution.
• Corrections append state rather than rewriting history.
• Inference and scenario material remain explicitly labeled.
• Persona routing never changes an evidence status.
• No political persuasion, voter targeting, or autonomous publishing.
• External effects require an exact Core-governed Decision, human review, post-effect verification, and promotion; the reference proof is limited to one create-only workspace file.

World Intelligence does not watch live news feeds, decide anything on its own, or publish or deliver content autonomously. Every LIVE capture demonstrated here is one explicitly requested, governed, read-only retrieval. P2C2's only effect is an explicitly authorized and reviewed create-only local workspace export followed by separate verification and promotion.

Next: publish World Intelligence 0.9.0, verify its installed wheel with public Core 0.5.0, then add a separately reviewed opt-in network transport and exercise P2D multi-source conflict/correction with LIVE inputs. Neither step may add autonomous publishing, delivery, persuasion, or action authority to a Domain Pack.

License

Apache-2.0.