The workflow needed a visible path from candidate intake through job discovery and recruiter judgment.
Delivery record
Abundance nurse staffing system.
The NP Group now has a live concierge app, a repo-backed database, hardened Abundance API routes, production-smoked Staff and Jobs MCPs, an NPG scoped hub, Braintrust/Langfuse eval evidence for the Dify agent path, walkthrough artifacts, and a clear agent boundary for recruiter-led review.
The pilot is now legible as an operating path.
A buyer can see what changed, what is safer, and which decisions still gate the next phase without reading private evidence.
The delivery page compresses the working surfaces, safe artifacts, and operator boundary into a client-readable status surface.
Public job discovery is read-only here, funnel writes require confirmation, and write-capable automation stays blocked until owners reauthorize accounts.
The open decisions are explicit, attributable, and separated from private token-bearing evidence.
Review packet
What can be shared.
These links are client-safe. Token-bearing tool URLs, employee rows, and private Notion details are intentionally excluded.
Abundance Jobs Agent
Search public roles through the job agent.
This panel calls the production-smoked Abundance Hub agent from the server. It can list and search public nursing jobs while keeping credentials and funnel writes out of the page.
Read-only job discovery Server-side job search path No exposed keys
Ask for public nursing and healthcare roles. This panel can read public jobs; funnel writes stay outside the delivery page.
Delivery agent
Ask against sanitized evidence.
This bounded agent answers only from the sanitized delivery context. Use it to explain the work, identify decisions, and turn client replies into structured notes.
Ask about what changed, what is private, what needs a decision, or how the database, MCP, and agent pieces fit together.
Database / Automation / Judgment
Organized by operating layer.
Created DB
Created
The Abundance data layer captures profile context, intake history, matching state, and private source artifacts for the next staff/operator integration pass.
Staff, Jobs, and NPG Hub
Production-smoked
Staff MCP, Jobs MCP, the NPG scoped hub, and Dify Abundance Hub have passed production smoke checks. The Abundance Dify agent also has a published Braintrust eval suite with Langfuse trace join keys. Credentials stay in secret storage and are not published in the delivery surface.
Agent Boundary
Ready for review
The agent supports intake, shortlist, missing-information flags, and recruiter review. It does not autonomously make staffing decisions.
Private Source Materials
Held outside the public page.
Received for private staff/operator context. Raw employee rows are not part of this public delivery surface.
Tracked as an external operational artifact and production-smoked through the Service API.
Published under create-something-dify-agents / abundance_hub: verifies Dify API health, Jobs MCP tool routing, forbidden writes, secret refusal, latency, and trace IDs for Langfuse inspection.
Staff MCP, Jobs MCP, and the NPG scoped hub were smoked without exposing token values.
Provider-independent D1 contract and Bright Data adapter path exist; the deployed Jobs MCP remains the serving surface until its backing source points at the normalized table.
Cloudflare Pages production has AGENCY_INTERNAL_API_KEY, but WHATSAPP_VERIFY_TOKEN and WHATSAPP_APP_SECRET still need provisioning before enabling the Meta webhook.
Hub status calls are reachable, but Jotform, Mailchimp, and WhatsApp report connected=false and need account-owner authorization before write-capable automation.
Next Review
Decisions still open.
Provision WhatsApp webhook secrets in Cloudflare Pages production.
Promote the secured Abundance API build from a clean release branch or clean deployment workspace.
Have NPG account owners review or reauthorize Jotform, Mailchimp, and WhatsApp before write-capable automation.
Confirm how Paylocity fields map into staff/operator records.
Point the Abundance Jobs MCP backing source at the normalized public jobs table after Bright Data credentials and dataset IDs are provisioned.
Decide which operator roster receives MCP/database access.