docs: launch ACE 0.8 Intelligence OS realignment

[eamirian]

Outcome

Launches the bounded 0.8A control packet for ACE 0.8.0 Intelligence OS Realignment.

This reconciles the public roadmap from Intelligence Workspace / Later to Intelligence OS Realignment / Next and freezes the A–F delivery sequence before runtime or UI changes begin.

What is frozen

• canonical lifecycle: evidence → observation → entity state → signal/shift → case/brief → decision/action → outcome → governed feedback
• ownership across Core, Intelligence, declarative Domain Packs, executable adapters/strategy plugins, and applications
• compatibility treatment for reasoning/orchestration, MAKE/SHIP arms, the Living Product Graph name, broad MCP, Atrium, and extensions
• the 0.8A–0.8F landing and rollback order
• World AI Command Center as the public signature journey
• Market Intelligence as the materially different commercial falsifier
• exact stop conditions preventing domain leakage, duplicate infrastructure, authority widening, and incidental MCP expansion

Product boundary and compatibility

0.7 remains the released Intelligence Builder foundation. This packet does not rebuild the shipped onboarding agents, AC7 composition, or AM3 authorized memory. AM4 and AM6 remain independent candidate inputs and are not silently made 0.8 dependencies.

0.8 does not claim multi-tenant collaboration, marketplace, managed operation, hostile-code isolation, omniscience, or general real-world causal accuracy.

Evidence

• focused roadmap and evidence-index gate: 18 passed
• Ruff check: passed
• Ruff format check: passed
• git diff --check: passed

Risk and rollback

Documentation, release control, and compatibility policy only. No runtime, schema, API, authority, or public package behavior changes. Revert this commit to restore the prior roadmap framing; later 0.8 packets must not land until this ownership and compatibility boundary is accepted.

Checklist

• I used no private data, credentials, proprietary fixtures, or private-extension code.
• I updated documentation for changed public behavior and did not overstate maturity.
• I ran focused checks, relevant conformance checks, Ruff for changed Python, and git diff --check.
• If roadmap-related, I linked or updated the public issue/Project item.
• Security-sensitive details were reported privately under SECURITY.md (not applicable).

Part of #40. This PR does not close the 0.8 milestone.