Jira and Confluence

Jira can project work items, ownership, dependencies, and status. Confluence can project accepted discovery, specifications, decisions, and review summaries.

These projections improve team access, but neither becomes the executable source of truth. The repository Execution Package keeps the signed requirements, evidence identities, and checkpoints.

Connector effects use stable idempotency keys and remote claims. Replaying a handoff adopts matching issues or pages instead of creating duplicates. Conflicting remote state blocks for reconciliation.

Credentials and tenant details are local bindings; stable project and space identifiers may be committed when policy allows.