Demo mode. These companies, people, amounts and documents are fictional. Nothing here comes from a real business, and no sign-in is needed.

Why is Project Atlas behind schedule?

Northstar Systems. Asked: “Why is Project Atlas behind schedule, who owns the blockers, which previous decisions are relevant, and what evidence supports the findings?”

Findings

  • ticket:atlas-142 'Connect onboarding checkout to Billing Gateway v2' is blocked and overdue (due 2026-10-01, as of 2026-10-16); status: blocked
  • ticket:atlas-142 is blocked by ticket:int-88 'Enable v2 webhook signing in production' (status: blocked)
  • ticket:atlas-142 is currently owned by person:dev-patel (Dev Patel); owner team membership: team:platform
  • ticket:int-88 is currently owned by person:sam-okafor (Sam Okafor); owner team membership: team:integrations
  • ticket:atlas-147 'Localized onboarding email templates' is overdue (due 2026-10-10, as of 2026-10-16); status: in_progress
  • incident:inc-009 'Billing Gateway v2 webhook signature verification failures' (mitigated, sev2) affects the blocker chain of ticket:atlas-142
  • incident:inc-007 'Billing Gateway v1 timeout cascade during month-end invoicing' (resolved) occurred in the same component as ticket:atlas-142's blocker chain; resolved by person:lena-ortiz
  • project:atlas is currently owned by person:maya-chen (Maya Chen), team:platform (Platform); owner team membership: team:platform
  • decision:dec-005 'Atlas launch date is fixed at 2026-11-01 for the Q4 customer cohort' (decided 2026-08-01 by person:omar-haddad) is current guidance for project:atlas
  • decision:dec-004 'New integrations use Billing Gateway v2 only; the v1 fallback is retired' (decided 2026-07-15 by person:priya-nair) is current guidance for component:billing-gateway, project:atlas; it supersedes decision:dec-002
  • decision:dec-002 'Keep Billing Gateway v1 as a fallback for new integrations until v2 is certified' is superseded by decision:dec-004; excluded from current guidance
  • person:lena-ortiz (Lena Ortiz) has recorded experience with resolved_incident incident:inc-007, authored_incident_source source:postmortem-007
  • person:sam-okafor (Sam Okafor) has recorded experience with owns_component component:billing-gateway, authored_incident_source source:postmortem-009, member_of_owning_team team:integrations
  • person:dev-patel (Dev Patel) has recorded experience with authored_incident_source source:chat-inc-009, member_of_owning_team team:platform

Missing information

  • ticket:atlas-147 is overdue but the graph records no open blocker, incident or status explaining the delay.
  • No current owner is recorded for ticket:atlas-147.

Sources used

  • Architecture review notes, July 2026 (AR-2026-07)
  • Memo: gateway v1 fallback policy (DEC-002)
  • Postmortem: INC-009 webhook signature failures (PM-009)
  • Architecture review notes, July 2026 (AR-2026-07)
  • Atlas Q4 launch plan (PLAN-ATLAS-Q4)
  • Postmortem: INC-007 v1 timeout cascade (PM-007)
  • LedgerPay status page snapshot, 2026-09-22
  • INT-88 ticket record (INT-88)
  • #inc-009 incident channel thread (inc-009-thread)
  • Postmortem: INC-009 webhook signature failures (PM-009)
  • Atlas Q4 launch plan (PLAN-ATLAS-Q4)
  • #inc-009 incident channel thread (inc-009-thread)
  • ATLAS-142 ticket record (ATLAS-142)
  • ATLAS-142 ticket record (ATLAS-142)
  • Postmortem: INC-009 webhook signature failures (PM-009)
  • INT-88 ticket record (INT-88)

10 parameterized graph queries ran for this answer: resolve_entities, tickets_in_scope, ticket_status, ticket_incident_paths, incidents, decisions_affecting, current_decisions, experts_for_components, current_owners, sources_for.

source:vendor-status-0922 contradicts incident:inc-009; review before relying on it