-
-
Notifications
You must be signed in to change notification settings - Fork 1
Fix DHT synchronization workarounds in capability-based sharing #36
Copy link
Copy link
Open
Labels
P2-highHigh priority - important for milestone completionHigh priority - important for milestone completionbugSomething isn't workingSomething isn't workingphase-2-governancePhase 2 - Enhanced governance & process integration (current)Phase 2 - Enhanced governance & process integration (current)zome-personPerson zome - agent identity, profiles, rolesPerson zome - agent identity, profiles, roles
Milestone
Metadata
Metadata
Assignees
Labels
P2-highHigh priority - important for milestone completionHigh priority - important for milestone completionbugSomething isn't workingSomething isn't workingphase-2-governancePhase 2 - Enhanced governance & process integration (current)Phase 2 - Enhanced governance & process integration (current)zome-personPerson zome - agent identity, profiles, rolesPerson zome - agent identity, profiles, roles
Type
Projects
Status
Backlog
Overview
The capability-based private data sharing system (
capability_based_sharing.rs) contains two temporary test workarounds for DHT synchronization issues that need to be resolved for production reliability.Problem
Capability metadata link discovery fails intermittently during cross-agent operations, causing:
get_private_data_with_capability()to fall back to test workaround (line ~296)revoke_private_data_access()to useRevokedGrantMarkerentries instead of proper link deletion verification (line ~440)Both locations are marked with:
Expected Behavior
AgentToCapabilityMetadata) should be reliably discoverable across agents afterdhtSyncFiles
dnas/nondominium/zomes/coordinator/zome_person/src/capability_based_sharing.rs(lines ~296, ~440)Acceptance Criteria
RevokedGrantMarker(or document why markers are the correct pattern)Related