PKG step 5 — edge ↔ cloud-twin sync (finishes the person-graph stack)#681
Merged
Conversation
…ph stack) Diagram-4: the per-person graph is edge-resident (HellGraph on TopoLVM flash, #675); a cloud twin holds canonical. This wires the sync. - deployment-profiles.yaml: + p-edge profile with an edge_twin_sync block (edge_to_twin, 30m cadence, reference_only privacy). - edge-twin-sync/base: rclone CronJob (every 30m, co-located on the HellGraph node via podAffinity, mounts the store PVC read-only, pushes a timestamped copy to the S3-compatible twin) + topolvm-snapshots VolumeSnapshotClass (crash- consistent PITR upgrade path) + ServiceAccount + ExternalSecret example for the twin creds. Hardened podSec (runtime-baseline kyverno). Privacy: only non-private projections cross — the ProviderProjection membrane governs export; private nodes stay on-device. kustomize renders 3 resources; profiles parse (p-edge present). Depends on #675 (StatefulSet PVC).
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
Finishes the Personal Knowledge Graph stack (diagram-4). The per-person graph is edge-resident (HellGraph on TopoLVM flash, #675); a cloud twin holds canonical. This wires the sync.
p-edgeprofile — added todeployment-profiles.yamlwith anedge_twin_syncblock (edge_to_twin, 30m cadence,reference_onlyprivacy).sync-cronjob.yaml— every 30m an rclone Job co-locates on the HellGraph node (TopoLVM volumes are node-local), mounts its RocksDB store read-only, and pushes a timestamped copy to the S3-compatible twin. Twin keeps PITR copies; edge stays authoritative.volumesnapshotclass.yaml—topolvm-snapshotsfor crash-consistent snapshots (the strict-consistency upgrade path).serviceaccount.yaml+ ExternalSecret example — sync identity + twin creds.Privacy
Only non-private projections cross the link — the
ProviderProjectionmembrane (workspacePersonalContextGraph, prophet-workspace#21) governs export; private nodes stay on-device.Verification
kubectl kustomizerenders 3 resources (SnapshotClass + SA + CronJob);deployment-profiles.yamlparses withp-edgepresent.Follow-ups (honest)
PKG stack now complete
contract (workspace#21) · substrate (#675) · runtime (memory-mesh#40) · UI (socioprophet#401) · edge/twin (this).