Admin Operations

Check for new bounty postings, NTE threshold warnings (70%/90%/100%), auto-promote triggers, and expiring deadlines. The admin dashboard shows all activity in a unified feed.

Review developer approach, NTE estimate vs budget ceiling, team composition (for team claims), and developer completion rates at the same difficulty level.

The Delivery Hub board in Nimba org shows cross-org work status via the sync engine. Internal employee work and external contractor work visible in unified view.

Track estimated completion dates, dependency chains, and cascading delay impacts. Proactively alert when downstream work items are at risk due to upstream delays.

Create NetworkEntity records for vendors (with billing rates, insurance verification) or internal teams (with SLA expectations and auto-promote thresholds).

Set conditions for automatic promotion of internal bounties to the external marketplace: SLA warning thresholds, no-progress triggers, NTE breach responses.

Compare completion rates, NTE accuracy (estimated vs actual), code quality scores, and response times across vendors and internal teams.

Verify that all external vendors and contractors maintain current professional liability insurance. Internal employees are covered by the organization. Block uninsured vendor work.

GitHub Actions runs Apex tests, PMD scan, and scratch org build on every PR. Results are visible inline on the PR and reported to the platform.

Review the manual checklist: data migration verified, configuration steps completed, training docs delivered. Both CI and manual items must pass.

Automated ETA calculations show estimated completion dates. Dependency tracking surfaces cascading impacts when upstream items slip. Proactive alerts to downstream owners.

For multi-developer bounties: compare implementations side-by-side, score quality and approach, assign rankings that feed into developer reputation.

Check Sync_Item__c queue depth across all connected orgs. Healthy queues drain within minutes. If items accumulate, investigate API limits, auth failures, or field mapping errors.

Salesforce Platform Events fire when work items, work logs, or documents change. The sync engine subscribes to these events for near-real-time cross-org propagation instead of polling. Reduces sync latency from minutes to seconds.

The reconciler compares record hashes across orgs and auto-detects drift (records that should match but do not). Corrections are queued automatically with full audit trail. No manual intervention unless a conflict cannot be auto-resolved.

Prevents infinite sync loops. GlobalSourceIdTxt__c tracks the originating org for every record. The kill-switch aborts routing when the target matches the source. X-Global-Source-Id HTTP header injected on every outbound callout.

Failed sync items retry up to 3 times with exponential backoff. After 3 failures, the item is flagged for manual review and appears in the Sync Retry Panel on the admin home page.

AI evaluates developer history, NTE reasonableness, approach quality, and completion probability. High-confidence recommendations can be auto-approved.

Compare proposed NTE against historical data for similar work items at the same difficulty level. Flag outliers for manual review.

When auto-promote rules trigger, AI evaluates whether promotion is likely to result in faster delivery based on current marketplace capacity and developer availability.

AI reviews every PR with full context (repo, ticket, client goals, acceptance criteria) and provides structured feedback beyond what CI checks can validate.

Configure percentage rake (per-project) or hourly markup (per-client). Example: Glen bills At Large at $90/hr, At Large bills MF at ~$125-135/hr.

Trigger invoice generation from Salesforce. The Document Engine pulls work logs from all lifecycle phases, calculates hours x rate, and generates a PDF with full line-item detail. Line items include clickable hyperlinks to Salesforce records (namespace-aware).

Mark invoices as Pending Approval. Client reviews in the portal and approves or disputes with line-item comments. Disputed invoices route back for correction. Regeneration creates a new version preserving the original for audit.

Currently manual: verify Melio payment sent, mark DeliveryTransaction__c as Completed. Future: Stripe auto-payment on acceptance.

Every document email (invoices, agreements) is CC'd to glen@cloudnimbusllc.com. This is a hard requirement configured in DeliverySettings.

Outstanding invoices, aging reports (Current / 30 / 60 / 90+ days), payment history. All data sourced from DeliveryDocument__c and DeliveryTransaction__c.