PersonalContextGraph — the ego-scoped CSKG (default person-graph contract)#21
Merged
Conversation
…son-graph contract)
Step 3 of the person-graph substrate plan: re-home the default person-graph as a
first-class workspace contract, conforming to the existing CSKG rather than a
parallel vocabulary.
PersonalContextGraph = the person-scoped view of the CSKG. Where a ContextGraph
is workroom-bound, this is anchored on the individual (selfRef, single-Self
invariant). Nodes are CSKG nodes (contacts carry csKgNodeRef); edges are CSKGEdge
{node1,relation,node2,provenance_refs,source_evidence_refs}. sourceRefs are
WorkspaceSource ids (Layer-1 canonical objects) so every element is
provenance-bound and retention-actionable. External-KG links cross the membrane
ONLY as a ProviderProjection (reference-only; included/withheld) — nothing
private egresses. Carries the seed node-type + relation vocabulary as canonical
enums; governed by memoryScope, owned by the memory-steward.
- personal-context-graph.schema.json + .v0.1.example.json
- tools/validate_personal_context_graph.py (smoke: single-Self, person scope,
workspace-source provenance, vocabulary, membrane include/withhold) — passes
- docs/personal-knowledge-graph.md: design + record→CSKG mapping + the 3-repo
split (contract=workspace / runtime=memory-mesh / deploy=platform / consume=mesh)
Contract-only, as this repo requires; runtime + deployment land in memory-mesh +
prophet-platform (PR #675 already made HellGraph a durable managed service).
This was referenced Jul 1, 2026
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
1 participant
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.
What
Step 3 of the Personal Knowledge Graph substrate plan: re-home the default graph structure for a person as a first-class workspace contract — the person-scoped view of the CSKG, not a parallel vocabulary.
Where a
ContextGraphis anchored on a workroom, aPersonalContextGraphis anchored on the individual (selfRef).Changes (contract-only, as this repo requires)
context-fabric/personal-context-graph.schema.json— the contract. Single-Selfanchor; nodes are CSKG nodes (contacts carry theircsKgNodeRef); edges areCSKGEdge {node1,relation,node2,provenance_refs,source_evidence_refs};sourceRefsareWorkspaceSourceids (Layer-1 canonical objects) so every element is provenance-bound and retention-actionable; external-KG links cross the membrane only as aProviderProjection(reference-only). Carries the seed node-type + relation vocabulary as canonical enums; governed bymemoryScope, owned by memory-steward.personal-context-graph.v0.1.example.json— the demo person-graph (Self + Mom/Jamie/Acme/band-practice/setlist) with a reference-only social projection that withholds the private relationship.tools/validate_personal_context_graph.py— smoke validation (single-Self, person scope,workspace-source:provenance, vocabulary conformance, membrane include/withhold disjoint). Passes; existingvalidate_context_fabric.pystill passes.docs/personal-knowledge-graph.md— design + theWorkspaceSource → CSKGrecord mapping + the estate split.Ownership split
WorkspaceSource, resolvescsKgNodeRef, writes HellGraph viaHELLGRAPH_URL).The graph is a Layer-2 derived store — rebuildable from Layer-1 canonical objects, edge-first, never a source of truth.