---
# System prepended metadata

title: Luke's Summer Internship

---

# Luke's Summer Internship

## Timeline
- ~12 weeks total
- 2 weeks alignment and planning
- 10 weeks design and implementation

## Area of Work
- Governance of Object Identity \[1\]
- Identity Module in KOI

\[1\]: Identity is a relation that holds between objects/referents which are "the same". Examples include a named function with several implementations or a document with different versions.

## Deliverables
- Identity module for governing identity relations \[2\]
- Identity governance interface via Slack
- Validating that an identity relation is the product of said governance processes. E.g. that a "these are the same" relation is the result of a vote, or a "these are 0.92 similar" relation is the outcome of a participatory process.
- w/ Orion: Presentation on Identity, identity governance and its application to knowledge organisation


\[2\]: We're calling these identity *relations* because we want an approach to identity that is decoupled from the objects themselves and we can achieve this by handling identity in a relational manner — this is in contrast to most implicit approaches to identity such as mutable files where the files identity is coupled to the filesystem, or a google doc where the doc identity is coupled to the google docs app. If identity were decoupled from google docs, many "versions" of the document might coexist and there would not be a single, authoritative "latest version" without agreement through some kind of governance process. This also means that objects can be part of *multiple* identities at the same time, which seems to be an obvious prerequisite for distributed identity.

### Use-cases for Identity Governance
- Mantaining continuity across migrations (e.g. new HackMD workspace)
- Representing concepts
- Organising different articulations of the same idea (e.g. ABCs at different levels of technicality)

### Questions
- legible statement of the field in which Lukes work will be done

### Scratch notes from calls
- Cyberinfrastructure framing
- Provenance of identity relations
- how wikipedia manages identity
- need for identity applies even more to content-addressed web
- identity relations between systems (e.g. between KMS references and IPFS)
- Which notions of “sameness” should be supported — the most obvious (and common) notion is “[object] is version of [identity]” but I think there may be lots of value in exploring at least one other notion to avoid falling into a false equivelance of identity management = versioning. For example fuzzy identity relations where objects can have degrees of membership/connection to an identity. Think identity of memes, or written expressions of an idea (some of which might be 10/10 for accuracy while others might be so reductive as to lose most of their connection to the identity of the idea that its meant to express)