GGA Exchange vault

Daily tracking and queues

2 min read

Status. Proposed design only. Nothing in this vault is GGA client approval. The GGA client documents are supplied drafts: see GGA-Source-Digest. No application, service or test has been executed; every scenario is Not executed. Delivery fees and dates are open.

Daily tracking and queues

Sources: Blueprint pp. 7, 10, 16, 19 (GGA-Requirement-Register); retained 1.3 findings on mirroring authorised records.

Member dashboard

Profile status and next due date, relevant opportunities, upcoming sessions, pending consent requests and introduction progress. Contribution appears as a separate status and never as an access state.

Partner workspace

Own listings, review reasons, permitted pitches, freshness and expiry confirmations, closure.

Operations and finance console

Separate queues for profile exceptions, listings, consent delays, failed jobs and invoices. Each row shows owner, age, next action and audit history. Operations must be able to resolve a review, a failed message and an expired consent without Anand (GA11 in Acceptance-Gates-A01-A11).

Rules

  • The view mirrors the underlying authorised records and never exposes another company’s or partner’s items (T30).
  • Eligibility shown on screen is computed at request time, not read from a stored flag.
  • Time boundaries are reproducible: operational timestamps are UTC and rendered in the user’s timezone; due and overdue use the clock port (T31).
  • Pilot metrics (Blueprint p. 19): current-profile rate, active owner-confirmed opportunities, accepted introductions, discussions held, company-confirmed value, cash collected, operating cost and Anand’s total time, each with source and time window. Registrations and submitted pitches are not realised value.

No GGA feedback received (Proposed carry-forward)

The 1.3 in-app list of assigned next actions with due dates, and the rule that a nudge about an overdue item is not part of the view (DG13, DG22), stay Proposed. That exclusion covers assigned next-action items only. Profile freshness reminders at the due date and grace days 7 and 13 (Blueprint pp. 7, 16) are part of release one. Dashboards beyond the above and escalation workflows for next actions are not part of release one.

Graph View