wiki: sync 2026-10-23 03:04 UTC — 6 file(s) updated
This commit is contained in:
1 parent
016681b6f8
commit
de3bb86459
6 files changed
+73
-4
No files matched your search
@@ -11,6 +11,7 @@ Historical general-purpose channel for Jarvis conversations and voice-operation
|
||||
- Current Hermes activity-based voice behavior may supersede this historical instruction only where explicitly configured and approved; preserve the distinction between predecessor history and current behavior.
|
||||
|
||||
## Current State
|
||||
- **Conduit access (2026-10-22):** User approved an additional dashboard password login alongside Keycloak SSO at `https://jarvis-jr-v1.lego-cloud.eu`. Username `conduit`; only a scrypt password hash is stored in dashboard config. Both providers verified live and password login returned HTTP 200. Connection QR delivered privately to the requesting user's Discord DM; temporary plaintext provisioning file removed. iPhone/Conduit end-to-end connection remains user verification. No credentials or QR belong in this wiki or public channel.
|
||||
- Included in wiki monitoring for any renewed general or voice-operation decisions.
|
||||
- **CONFIRMED (2026-09-07):** RootAtSkic directed Hermes to remove large embedded channel-wiki bodies from `config.yaml`, create one repository-backed skill per configured channel, and replace each channel prompt with a short `skill_view` directive. Twenty dedicated private skill repositories were created and remotely verified across `home-v1-skills-code-agent`, `vssa-v1-skills-code-agent`, `corp-v1-dpvp-skills-code-agent`, and `cognitive-architect-v1-skills-code-agent`.
|
||||
- `discord.channel_prompts` now contains 20 directives of 220–262 characters; `config.yaml` decreased from 395,337 to 22,834 bytes. `/opt/data/scripts/channel-wiki-sync.py` now preserves this routing idempotently instead of copying wiki bodies back into config.
|
||||
@@ -21,5 +22,9 @@ Historical general-purpose channel for Jarvis conversations and voice-operation
|
||||
- **Open evaluation (2026-09-19):** RootAtSkic asked Hermes to investigate Jev (referencing the LangChain article “Building a harness with Jev”), identify practical uses in the Home v1 environment, determine whether it is available or deployable as a TrueNAS app, and assess likely impact. No deployment decision or authorization was made in the request; findings and ownership remain pending.
|
||||
- **Operator communication preference (2026-09-19):** RootAtSkic wants Hermes to retain and use knowledge of his character and principles, and explicitly reported that Hermes is giving him too much material to read. Responses should prioritize concise, decision-oriented summaries and avoid shifting unnecessary reading burden to him.
|
||||
|
||||
## Conduit follow-up — 2026-10-23 daily sync
|
||||
- RootAtSkic requested Conduit onboarding using an iPhone-reachable full dashboard URL (never localhost), percent-encoded connection fields, omitted password if unknown, and authentication kept enabled (`1562745377524809751`). Subsequently required a QR code rather than only a link (`1562745994146353175`) and approved the preceding proposal (`1562746347344625706`); existing channel-workflow record above describes password login alongside SSO and private QR delivery. Daily sync did not retest authentication or user device connectivity.
|
||||
- Open governance question: user challenged the newly created skill's compliance with agreed Gitea organization/repository/naming conventions and asked where to find the QR (`1562747828982521897`). Exact skill identity and remediation are not established by these human messages. Do not persist connection credentials or QR payloads in the wiki/mirror.
|
||||
|
||||
## Source anchor
|
||||
- Latest processed human message: `1550958850335576217` (2026-09-19 19:56 UTC; asked where Hermes learns his character/principles and objected to being given too much material to read).
|
||||
- Latest processed human message: `1562747828982521897` (2026-10-22; skill-governance and private QR retrieval follow-up).
|
||||
Reference in new issue
Block a user