Skip to content
This repository was archived by the owner on Aug 25, 2024. It is now read-only.

Commit 54916ce

Browse files
John Andersenpdxjohnny
John Andersen
authored andcommitted
CONTRIBUTING: Fix link to #1287
1 parent 249eb84 commit 54916ce

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

CONTRIBUTING.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -243,7 +243,7 @@ This section covers call outs on specific behavior or expectations or boundries
243243

244244
Boundries: I will federate changes from you and forward changes to others I am federating with if the analysis of the graph of thoughts leading to the send of the new data event is within acceptable risk tolerence. If we notice actions in the network unaligned to the defaults outlined in this document we we will begin enforcing these boundries. Additional boundries can be overlayed
245245

246-
- [github.com/intel/dffml#1287: docs: examples: innersource: Org health and issue prioritization]()
246+
- [github.com/intel/dffml#1287: docs: examples: innersource: Org health and issue prioritization](https://github.com/intel/dffml/issues/1287)
247247

248248
Virtual branch - shared context dependent trains of thought within a poly-repo environment. If the overlays of an entity currently federating with. The N+1 federation new data event is always determined by a KERI duplicity detection protected channel (this is critical because or else we are not able to see who is being duplictus over time, which we need for the relying parties analysis of ClearForTakeoff for AI agent (workload) identity (OIDC, sould based auth). The tcb for trust evaluation is also party of relying party inputs.
249249

0 commit comments

Comments
 (0)