Back to Prompt Library
implementation
Build the application
Inspect the original prompt language first, then copy or adapt it once you know how it fits your workflow.
Linked challenge: Build a Supplier Credential Expiry and Re-Certification Coordinator
Format
Code-aware
Lines
85
Sections
11
Linked challenge
Build a Supplier Credential Expiry and Re-Certification Coordinator
Prompt source
Original prompt text with formatting preserved for inspection.
85 lines
11 sections
No variables
1 code block
## Build
Process supplier compliance certificates and track expiration dates using tabular Frictionless Data packages. Orchestrate automated re-certification alerts and verify renewed credential integrity.
## User
Vendor Risk Manager
## Workflow
1. Read supplier credential records and certification schedules encoded as Frictionless tabular resources.
2. Validate document validity periods against system renewal horizons and regulatory accreditation mandates.
3. Identify certificates with expired status or incomplete issuing jurisdiction data.
4. Generate prioritized re-certification outreach schedules with standardized document checklist attachments.
## Interface
Operational Kanban board organizing vendors by credential expiration urgency with tabular error logs.
## Data
Generate synthetic tabular CSVs describing supplier licenses and insurance policies along with Frictionless schema descriptors.
Starter examples below are synthetic. They are not downloaded records.
## Source
[Frictionless data validation](https://raw.githubusercontent.com/frictionlessdata/frictionless-py/main/README.md)
Employ Frictionless Data resource schema formats and type validation methods for vendor credential catalogs.
## Tools
mastra-ai, frictionless, typescript.
Mastra AI provides structured workflows to coordinate scheduled state transitions and alerting steps.
OpenAI-compatible LLM endpoint for drafting structured re-certification notices.
## Deliverables
Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.
## Acceptance
- Infers and validates supplier tabular schemas using Frictionless schema rules.
- Correctly partitions suppliers into thirty, sixty, and ninety day renewal tranches.
- Constructs automated request payloads listing only missing or expiring documentation.
- Outputs valid re-certification manifests suitable for vendor portal consumption.
## Starter Examples
```json
[
{
"input": {
"vendor_code": "VND-551",
"vendor_name": "Apex Security Logistics",
"evaluation_date": "2024-04-01",
"credentials": [
{
"name": "ISO27001_Certificate",
"expires_on": "2024-04-20",
"status": "active"
},
{
"name": "General_Liability_Policy",
"expires_on": "2024-11-30",
"status": "active"
}
]
},
"expected_output": {
"vendor_code": "VND-551",
"action_priority": "urgent",
"tranche": "0_to_30_days",
"documents_requiring_action": [
"ISO27001_Certificate"
],
"notification_draft": "Notice: ISO27001_Certificate for Apex Security Logistics expires on 2024-04-20. Submit renewal within 19 days."
}
},
{
"input": {
"vendor_code": "VND-702",
"vendor_name": "Northern Freight lines",
"evaluation_date": "2024-04-01",
"credentials": [
{
"name": "Hazardous_Materials_Permit",
"expires_on": "2024-08-15",
"status": "active"
}
]
},
"expected_output": {
"vendor_code": "VND-702",
"action_priority": "normal",
"tranche": "90_plus_days",
"documents_requiring_action": [],
"notification_draft": "No urgent renewal actions required. Next expiration on 2024-08-15."
}
}
]
```
## Safety
Simulates vendor documentation and communications in an isolated sandbox with mock company data.
Use mock external writes. Require human review before any real deployment.Adaptation plan
Keep the source stable, then change the prompt in a predictable order so the next run is easier to evaluate.
Keep stable
Hold the task contract and output shape stable so generated implementations remain comparable.
Tune next
Update libraries, interfaces, and environment assumptions to match the stack you actually run.
Verify after
Test failure handling, edge cases, and any code paths that depend on hidden context or secrets.