Implement registry verification and consent version binding#292
Merged
Emeka000 merged 2 commits intoApr 29, 2026
Merged
Conversation
- Add actor verification with caching for domain contracts - Fix provider-registry and insurer-registry contracts - Bind clinical trial enrollment to current consent version - Prevent sensitive writes without registry verification Closes Healthy-Stellar#213, Healthy-Stellar#241
|
@oche2920 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Problem A: Structured evidence capture for severe incidents - Add incident tracking module with severity levels - Support multiple evidence types (error logs, state snapshots, stack traces, context) - Implement incident lifecycle: capture -> attach evidence -> resolve - Max 100 evidence entries per incident to prevent storage bloat - Integrate with allergy-management contract for troubleshooting - New contract methods: capture_incident, attach_incident_evidence, resolve_incident - Event: IncidentCaptured for monitoring Problem B: Report job resource management to prevent CPU/memory starvation - Add resource management module with job queuing - Implement resource quotas: CPU units, memory units, timeout - System-wide limits: concurrent job limit, total budget, throttle threshold - Job priority levels: Low, Normal, High, Critical - Throttling mechanism: defer jobs when 80% of budget consumed - Track actual resource usage per job completion - Integrate with healthcare-analytics contract - New contract methods: request_report, execute_next_report, complete_report - Admin controls: set_resource_limits for dynamic adjustment - Events: report_job, exec_job, job_done for monitoring Both features include: - Comprehensive documentation in INCIDENT_AND_RESOURCE_MANAGEMENT.md - Privacy-preserving evidence storage (hash-based) - Proper authorization checks via require_auth() - Storage-efficient indexed lookups
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #213
Closes #241