Your KV is your private, user-controlled store for information StegVerse can use only through governed access when a capability needs it.
Open a private KnowledgeVault directory to browse its files. Directory listings come only from your connected KV; this public page does not contain your private files.
Check this browser context for an existing StegVerse Node before creating Receipt #1.
Registration creates the local Node continuity root used to restore these steps when this device returns. If registration fails, open device-registration troubleshooting and history.
Not done
View in device chainEstablish a KnowledgeVault relationship for this Node, or reconnect an existing KnowledgeVault deliberately.
My KV first asks DEVICE_KV whether this Node already has a KnowledgeVault relationship. A fresh Node remains KV_RELATIONSHIP_NOT_ESTABLISHED; registration alone never implies a KV. Installation-receipt recovery is offered only after an existing-KV path is selected or relationship evidence is already present.
Existing-KV recovery path: Browse → that KnowledgeVault folder → _System → installation.receipt.json. This path is for an already-existing KV relationship you deliberately chose to connect; it does not create a KV relationship merely because a file exists.
The current registered Node asks DEVICE_KV for bounded relationship and installation status. If no relationship exists, choose whether to initialize browser-local KV data or connect an existing KV. A canonical installation receipt is recovery evidence for the existing-KV path, not evidence that a fresh Node already had a KV.
Not done
View in device chainEverything here is optional.
More relevant information can improve StegVerse's ability to understand your context and provide useful assistance when you permit a capability to use it. How KV improves comprehension.
These fields are optional and stay in your Personal KnowledgeVault. They do not grant identity, credential, provider, or execution authority.
Canonical Personal Information file: _Entities/Self/Personal_Contact_Profile.json inside your KnowledgeVault.
Live Personal KV access is unavailable on this device. You can still use an owner-mediated Files fallback without making the browser your canonical KV.
Optional private values used to prefill business and government forms. These values are written only to _Entities/Self/Personal_Form_Profile.json in your KV. Reusable e-signature material is not stored here; only its SKAP Vault reference is retained.
Email addresses are profile information until you explicitly connect one. Connection credentials belong in SKAP Vault, never in this form.
You may leave every field empty. If you add information, it should be persisted only through the connected KV profile bridge. The Node chain records completion state, never the personal values.
Not done
View in device chainSet up protected service connections and Vault references.
Not done
View in device chainVerify that your KV exists in your cloud storage and that the current installation evidence is valid.
Cloud/storage fallback path: Browse → your KnowledgeVault folder → _System → installation.receipt.json. This revalidates installation evidence from owner-selected storage; it does not grant the browser provider credentials.
Verification must come from the canonical KV/cloud bridge. If the bridge cannot inspect your configured cloud destination, the page reports failure instead of guessing.
Not done
View in device chainKV can give an admitted StegVerse capability relevant context without requiring you to repeat the same information. More data is not automatically better: pertinence, minimization, your permission, and the capability's governance still determine what may be used.