Back to prompt library
Build a Local Service Registry Interoperability and Audit Pipeline — implementation
Linked challenge: Build a Local Service Registry Interoperability and Audit Pipeline
Prompt source
implementation81 lines11 sectionsNo variables1 code block
## Build
Reconcile service provider credential updates and catalog diffs across decentralized Beckn registry nodes. Identify conflicting registrations and audit participant compliance.
## User
Network Governance Analyst
## Workflow
1. Poll mock Beckn registry nodes for registered provider service capabilities and signing keys.
2. Detect registry diffs such as service radius changes, category alterations, and key rotations.
3. Audit cryptographic key formats and check for unauthorized category claims.
4. Publish synchronized participant directories with verifiable audit stamps.
## Interface
Registry network topology dashboard showing node sync status, key lifecycle, and policy alerts.
## Data
Construct synthetic Beckn registry snapshots containing provider registration records and key logs.
Starter examples below are synthetic. They are not downloaded records.
## Source
[Beckn protocol specifications](https://raw.githubusercontent.com/beckn/protocol-specifications/master/README.md)
Adopts Beckn network architecture specs for BAP, BPP, and Registry discovery interactions.
## Tools
ray-serve, cryptography, pydantic.
Distributes high-throughput batch validation of registry participant records across parallel workers.
Local embedding or lightweight classifier model to identify duplicate service provider listings.
## 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
- Identifies unauthorized modifications to participant service boundary radii.
- Validates public key format compliance according to Beckn network policy.
- Detects duplicate entity listings operating under conflicting network IDs.
- Generates synchronized directory snapshots with cryptographic audit hashes.
## Starter Examples
```json
[
{
"input": {
"node_id": "REG-NODE-01",
"entry": {
"participant_id": "bpp.kirana-fresh.net",
"role": "BPP",
"signing_key": "MCowBQYDK2VwAyEA9Y4X2s...mockedKey",
"categories": [
"retail:grocery"
],
"service_radius_km": 15
}
},
"expected_output": {
"validation_status": "VALID",
"key_compliant": true,
"discrepancies": [],
"sync_action": "UPSERT_ACTIVE_DIRECTORY"
}
},
{
"input": {
"node_id": "REG-NODE-02",
"entry": {
"participant_id": "bpp.kirana-fresh.net",
"role": "BPP",
"signing_key": "MALFORMED_HEADER_KEY",
"categories": [
"retail:grocery",
"financial:micro_loans"
],
"service_radius_km": 2500
}
},
"expected_output": {
"validation_status": "INVALID",
"key_compliant": false,
"discrepancies": [
"INVALID_KEY_FORMAT",
"UNLICENSED_CATEGORY_FINANCIAL",
"RADIUS_EXCEEDS_LOCAL_LIMIT"
],
"sync_action": "QUARANTINE_RECORD"
}
}
]
```
## Safety
Maintains mock registry state; performs simulated cryptographic checks without manipulating real network registries.
Use mock external writes. Require human review before any real deployment.