PanSphaira now, next, and later

This is a curated navigation layer, not a second backlog. GitHub issue state and labels remain authoritative, and a linked issue is not evidence that a capability is released. The capability matrix owns current maturity; regular releases own shipped scope.

Now — verify and harden the released local proof

• Reproduce the released CRM-to-ERP approval and readback path and its CM-SEC-007 evidence.
• Continue the finite inactive capability/action catalogue in issue #3. Its live labels and issue history own the work state.
• Reproduce the released Extension Assurance Profile and its eight universal fail-closed gates. Issue #45 retains delivery history, while release governance owns shipped status.
• Reproduce the released minimized agent-work event contract and its consent, retention, tombstone and disclosure-safe readback gates. Issue #43 retains delivery history, while release governance owns shipped status.
• Reproduce the released update, migration, and Doctor contract freeze and its six-axis lock, canonical digest and fail-closed preview gates. Issue #59 retains delivery history, while release governance owns shipped status.
• Reproduce the separated External Video Service Boundary and its deterministic local reference-closure checks. Issue #64 retains delivery history, while release governance owns shipped status.
• Reproduce the released ASF-INTAKE-2 closed nine-gate pre-candidate decision through CM-REL-017. Issue #56 retains delivery history, while release governance owns shipped status.
• Reproduce the released INT-PROFILE-001 integration profiles and their five local-synthetic variants plus nine fail-closed probes. Issue #60 retains delivery history, while release governance owns shipped status.
• Keep release truth, anonymous asset/hash readback, secure-default probes, public navigation, and known limitations synchronized with every bounded increment.

Next — ready contract foundations

• Freeze the governed immutable skill bundle and compatibility contracts in issue #41. “Ready” is an issue-planning label, not a release or validation claim. Each increment still needs its own implementation, tests, evidence, review, and release decision.

Later — selected planned directions

• A governed CRM/ERP business-intelligence demo: issue #9.
• A governed Power Apps-first integration: issue #32.
• One core with thin conformant harness adapters: issue #36.

These are selected orientation links, not a promise of order, date, funding, compatibility, or delivery. Browse the full issue tracker for live scope and status.

Participate safely

Ask non-sensitive questions in GitHub Q&A, or follow the contribution guide for a bounded proposal. Use the security policy for vulnerabilities; do not post sensitive reports in an issue or Discussion.