From 3c9c35c7c9548da8437eb1507fcce47fa02bf9e2 Mon Sep 17 00:00:00 2001 From: Sam Catlow Date: Thu, 30 Jul 2026 02:11:05 +1000 Subject: [PATCH] beads: file outstanding install/lint issues, SOUL epic, and session learnings --- .beads/issues.jsonl | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/.beads/issues.jsonl b/.beads/issues.jsonl index ebd8c5c08..35c266c1d 100644 --- a/.beads/issues.jsonl +++ b/.beads/issues.jsonl @@ -53,6 +53,13 @@ {"_type":"issue","id":"archie-core-abg.18","title":"[EPIC] Memory: pluggable provider architecture with file-backed persistence","description":"Pluggable memory system to match Hermes parity:\\n\\n1. **MemoryProvider interface**: Abstract interface with methods for initialize(), get_tool_schemas(), prefetch(), sync_turn(), and optional lifecycle hooks (on_session_end, on_session_switch, on_pre_compress, on_memory_write).\\n\\n2. **Built-in file-backed memory**: MEMORY.md and USER.md stored per-session/profile. LLM-callable memory tool with add/replace/remove actions. Frozen snapshot at session start (preserves prefix cache), immediate disk write on updates. Section-sign delimited entries with substring matching.\\n\\n3. **MemoryManager**: Orchestrates built-in + at most one external provider. Background serialized write executor. Prefetch with timeout (8s). Streaming context scrubber that strips injected memory spans from model output.\\n\\nRef: docs/prds/hermes-gap-analysis.md section 4","acceptance_criteria":"An external memory provider (e.g. Honcho, Mem0) can be plugged in via config. The built-in memory tool persists across sessions. Conversation context is recalled on session resume.","status":"closed","priority":0,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-07-25T14:02:22Z","created_by":"Sam Catlow","updated_at":"2026-07-28T17:04:41Z","closed_at":"2026-07-28T17:04:41Z","close_reason":"Superseded by merged work: all 32 children complete (32/32, bd flags it 'eligible for close'). MemoryProvider interface, built-in file-backed memory, MemoryManager, scrubber, drain and threat scanning all landed in internal/memory. Nothing left in scope.","dependencies":[{"issue_id":"archie-core-abg.18","depends_on_id":"archie-core-abg","type":"parent-child","created_at":"2026-07-26T00:02:22Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-abg.16","title":"[EPIC] Gateway: rich message model, adapter lifecycle, session management","description":"Foundational gateway infrastructure to match Hermes parity. Three interdependent pieces:\\n\\n1. **Message model**: Replace the 3-field Message struct with a rich MessageEvent (MessageType enum: text/photo/video/audio/voice/document/sticker/command, media_urls, reply_to context, metadata dict, source). This is the wire type every adapter produces.\\n\\n2. **Adapter lifecycle**: Replace the 3-method Gateway interface with a BasePlatformAdapter interface: connect()/disconnect()/send() as required methods, plus optional overrides for typing indicators, edit/delete, image/voice/video/document send, interactive UX (clarify buttons, approval dialogs). Capability flags (supports_code_blocks, splits_long_messages, supports_async_delivery).\\n\\n3. **Session management**: SessionSource struct (platform, chat_id, chat_type, user_id, thread_id, guild_id, profile), AsyncSessionStore for persistent session storage, SessionContext for system prompt injection.\\n\\nAll three blocks together enable adding new platforms as plugins without touching core gateway code.\\n\\nRef: docs/prds/hermes-gap-analysis.md sections 1-2","acceptance_criteria":"New adapters can be added by implementing a Go interface with connect/disconnect/send + optional media methods. Messages carry full metadata through the pipeline. Sessions persist across gateway restarts.","status":"open","priority":0,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-07-25T14:02:21Z","created_by":"Sam Catlow","updated_at":"2026-07-25T14:02:21Z","dependencies":[{"issue_id":"archie-core-abg.16","depends_on_id":"archie-core-abg","type":"parent-child","created_at":"2026-07-26T00:02:21Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-jfg","title":"Spawned archie-agent containers not on daemon's docker network — can't reach NATS","description":"Root cause of 'agent still failing on the server': archied's container.Pool.Acquire creates archie-agent containers via the Docker SDK with no NetworkMode set, so Docker attaches them to the default bridge network. archied and nats run on the compose-created 'archie-core_default' network instead, so the spawned container's hostname resolution for 'nats' (from NATS_URL=nats://nats:4222) fails and archie-agent can't connect. Confirmed on carina host logs: archied logs show repeating 'taskrun request failed err=\"nats: no responders available for request\"' for every task, containers created and destroyed within ~1.5s (consistent with archie-agent's NATS client failing fast). Fixed by detecting the daemon's own container's network in NewPool (selfNetwork, via ContainerInspect on os.Hostname()) and setting HostConfig.NetworkMode on spawned containers to match.","status":"closed","priority":0,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-07-24T03:10:26Z","created_by":"Sam Catlow","updated_at":"2026-07-25T13:04:34Z","closed_at":"2026-07-25T13:04:34Z","close_reason":"Fix already implemented and verified: selfNetwork() in internal/container/pool.go detects the daemon's own container network via ContainerInspect(os.Hostname()) and Acquire() sets HostConfig.NetworkMode to match, so spawned archie-agent containers join the same compose network as nats. Build and internal/container tests pass.","dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-1y6","title":"SOUL cannot override the prompt invariants","description":"Enforce the boundary that makes SOUL safe to hand to users: it supplies identity and style, and cannot reach the instruction hierarchy, core rules, tool inventory or env block.","acceptance_criteria":"A test renders a hostile SOUL that attempts to countermand core_rules and asserts the invariant sections are still present and intact. The boundary is documented where the layering rule already lives so the next person editing the template does not quietly relax it.","status":"open","priority":1,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-07-29T16:09:56Z","created_by":"Sam Catlow","updated_at":"2026-07-29T16:09:56Z","dependencies":[{"issue_id":"archie-core-1y6","depends_on_id":"archie-core-4gv","type":"parent-child","created_at":"2026-07-30T02:09:56Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-z8c","title":"SOUL loader with per-turn reload and default fallback","description":"Load the SOUL file from the config dir into the identity slot of the rendered prompt, re-reading it per turn so an edit takes effect on the next message with no restart.","acceptance_criteria":"SOUL content is rendered into the identity slot ahead of the invariant sections. An absent, empty or unreadable SOUL falls back to the shipped default identity rather than rendering nothing. Editing the file changes the next turn's prompt with no restart. A read error is logged once and degrades to the default; it never fails the turn. Size is bounded so an oversized SOUL cannot crowd out the rules.","status":"open","priority":1,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-07-29T16:09:56Z","created_by":"Sam Catlow","updated_at":"2026-07-29T16:09:56Z","dependencies":[{"issue_id":"archie-core-z8c","depends_on_id":"archie-core-4gv","type":"parent-child","created_at":"2026-07-30T02:09:55Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-4gv","title":"[EPIC] SOUL file: user-authored agent identity","description":"Move Archie's identity and tone out of compiled Go constants and into a user-editable SOUL file. Root cause of a real defect on 2026-07-29: heyarchie answered 'Hey are you there?' with 'I'm here. What do you need?', which reads as demanding the user justify getting in touch. The fix required editing DefaultPersonas() in internal/gateway/persona.go and rebuilding -- personality is not tunable without a compile. Modelled on Hermes (SOUL.md occupies the identity slot in the stable tier, DEFAULT_AGENT_IDENTITY is the fallback when absent, re-read per message so no restart is needed) and openclaw, which injects SOUL.md alongside AGENTS.md.","design":"THE BOUNDARY IS THE POINT. The existing layering rule (recorded in the chat-system-prompt-design memory) is that PersonaRegistry is the style layer only and rules live in the template, so switching persona cannot strip the agent's rules or tool inventory. SOUL inherits exactly that constraint: it owns identity, name, register and warmth, and must not be able to touch core_rules -- otherwise 'be terse' in a SOUL silently disarms the no-fabrication rules. Steal from Hermes: is_legacy_template_soul upgrades untouched scaffolding in place but never overwrites a SOUL the user actually edited. This is the first of the three identity layers agreed with Sam on 2026-07-30: invariants (template, nobody edits at runtime) / SOUL (user-authored) / representation (curator-derived, proposes only).","acceptance_criteria":"A user can name their agent and define its personality by editing a file, with no rebuild and no restart. An absent or empty SOUL falls back to the shipped default identity. SOUL cannot weaken the invariants: \u003cinstruction_precedence\u003e, \u003ccore_rules\u003e, the \u003ctools\u003e block and \u003cenv\u003e stay in the template and remain unreachable from SOUL, enforced by a test. A SOUL the user has customised is never overwritten by an upgrade.","status":"open","priority":1,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-07-29T16:09:37Z","created_by":"Sam Catlow","updated_at":"2026-07-29T16:09:37Z","dependencies":[{"issue_id":"archie-core-4gv","depends_on_id":"archie-core-ewk","type":"related","created_at":"2026-07-30T02:09:58Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-ifi","title":"Audit the remaining golangci-lint autofix changes in 6d4e0be","description":"Commit 6d4e0be applied a golangci-lint --fix batch across 8 files. One of the eight was a behaviour regression: the errorlint fix in internal/tools/builtin/grep.go rewrote 'if exitErr, ok := err.(*exec.ExitError); ok \u0026\u0026 exitErr.ExitCode() == 1' into 'errors.As(err, \u0026exitErr)' and dropped the exit-code check, so any ripgrep failure (bad pattern, unreadable path) was reported to the model as 'no matches found' -- the agent would state a file contains nothing on the strength of a search that never ran. Fixed in 782510d. The other seven changes were eyeballed as benign (naked return expanded, err != ctx.Err() -\u003e errors.Is) but were never verified individually. A one-in-eight regression rate does not justify trusting the remainder on inspection alone.","acceptance_criteria":"Each remaining changed hunk in 6d4e0be is reviewed against its pre-fix behaviour, specifically for predicates that were narrowed or widened. internal/channels/telegram/model.go, internal/infrastructure/configuration/discovery.go, internal/tools/builtin/find.go, internal/tools/builtin/shell.go and the touched test files are covered. Any behaviour change found gets a regression test in the style of TestGrepReportsSearchFailureRatherThanNoMatches.","status":"open","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-07-29T16:09:21Z","created_by":"Sam Catlow","updated_at":"2026-07-29T16:09:21Z","dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-cbk","title":"Setup steps: operator, provider, models, forge, chat channel","description":"The archie equivalent of tau's provider+model flow. Steps: (1) operator display name -\u003e [chat].operator; (2) LLM provider -\u003e [providers.\u003cname\u003e] class and api_key_env, with the key value stored via the secret engine; (3) models per role -\u003e [models] triage/planner/builder, plus the optional [chat].models catalog; (4) forge -\u003e github/gitea/none with host and a token reference, explicitly optional now that a missing forge credential only disables the forge; (5) chat channel -\u003e Telegram bot token, optional. bot_user must always be written because validation requires it when no [[identities]] exist.","acceptance_criteria":"Each step is skippable where the underlying setting is optional, and skipping leaves a valid config. Forge selection defaults to none rather than assuming a forge. The token key written into config matches the key the value was stored under, for every forge type -- the exact drift that broke the installer. Local model discovery (Ollama) is offered when available and degrades to free text when not.","status":"open","priority":1,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-07-29T16:02:50Z","created_by":"Sam Catlow","updated_at":"2026-07-29T16:02:50Z","dependencies":[{"issue_id":"archie-core-cbk","depends_on_id":"archie-core-rs9","type":"blocks","created_at":"2026-07-30T02:02:55Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-cbk","depends_on_id":"archie-core-ewk","type":"parent-child","created_at":"2026-07-30T02:02:50Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":1,"comment_count":0} +{"_type":"issue","id":"archie-core-via","title":"SetupPrompter interface and UI-agnostic setup flow","description":"Port tau's split: setup logic lives in a package that takes a SetupPrompter interface; the command layer supplies the terminal implementation. This is what makes setup testable without a TTY.","acceptance_criteria":"Setup logic has no direct terminal dependency and is driven end to end in tests by a fake prompter. The terminal implementation provides a numbered Select and a non-echoing ReadSecret via golang.org/x/term, both cancellable on Ctrl+C via context. No TUI framework is introduced.","status":"open","priority":1,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-07-29T16:02:50Z","created_by":"Sam Catlow","updated_at":"2026-07-29T16:02:50Z","dependencies":[{"issue_id":"archie-core-via","depends_on_id":"archie-core-ewk","type":"parent-child","created_at":"2026-07-30T02:02:49Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-rs9","title":"Decide and implement the TOML write strategy","description":"Settle how setup persists config before any prompting code is written; everything else depends on it. BurntSushi/toml loses comments on re-marshal, and config.example.toml carries substantial inline documentation users are meant to read and edit by hand. Options: (a) generate a fresh commented config from a template on first run and only line-patch specific keys on re-run; (b) full re-marshal and accept losing comments; (c) adopt a comment-preserving TOML editor.","acceptance_criteria":"The chosen strategy is documented with its trade-off. A first run produces a config a human can read and hand-edit afterwards. A second run changing one value leaves every other line, including comments, byte-identical -- asserted by a test. No strategy is adopted that silently discards user edits.","status":"in_progress","priority":1,"issue_type":"task","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-07-29T16:02:49Z","created_by":"Sam Catlow","updated_at":"2026-07-29T16:09:23Z","started_at":"2026-07-29T16:09:23Z","dependencies":[{"issue_id":"archie-core-rs9","depends_on_id":"archie-core-ewk","type":"parent-child","created_at":"2026-07-30T02:02:49Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":1,"comment_count":0} {"_type":"issue","id":"archie-core-ewk","title":"[EPIC] archied setup: interactive first-run configuration","description":"Move config generation out of install.sh and into the daemon as 'archied setup', so the thing that writes config.toml is the same code that reads it. install.sh currently hand-rolls TOML and has already drifted from the schema once: it hardcoded the GitHub token key and the Gitea host, so a Gitea install produced a config naming a token the installer never wrote. Modelled on tau's 'tau setup' (internal/cli/setup.go, internal/app/setup.go), adapted for archie's TOML config and existing secret-reference indirection.","design":"Port from tau: the CLI/app split behind a SetupPrompter interface so business logic is UI-agnostic and testable without a terminal; plain-stdio Select and hidden ReadSecret (golang.org/x/term) racing ctx.Done for Ctrl+C -- no TUI dependency; atomic temp+rename writes. DIVERGENCE FROM TAU: tau surgically patches YAML nodes to preserve comments. archie uses BurntSushi/toml, which does not preserve comments across a decode/encode round trip, so a full re-marshal would destroy config.example.toml's documentation. Decide this explicitly -- see the child issue. Secrets differ too: archie already has secret.SecretRef{engine,key} indirection, so setup writes the reference into TOML and the value into the env engine's store; that is archie's equivalent of tau's config.yaml/auth.yaml split and should be used rather than reinvented.","acceptance_criteria":"install.sh no longer generates config.toml; it invokes archied setup. Setup is idempotent and re-runnable against an existing config without clobbering unrelated settings. Every config it writes passes configuration.Validate, verified by a test that runs setup non-interactively and validates the output. Secrets never reach config.toml or argv: config holds a secret reference, the value goes to the env file at 0600 via atomic write. Prompts for secrets do not echo. A non-TTY invocation without sufficient input fails with a clear message rather than writing a partial config.","status":"open","priority":1,"issue_type":"epic","owner":"sam@catlow.tech","created_at":"2026-07-29T16:02:28Z","created_by":"Sam Catlow","updated_at":"2026-07-29T16:02:28Z","dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-035","title":"Trigger accounting: curator output must not feed its own trigger","description":"Establish the invariant that work a curator produces does not count toward the condition that schedules the next curator run. Honcho hit this directly: their dream scheduler explicitly excludes dreamer output from the observation threshold, noting that counting it would inflate the threshold and create a feedback loop.","acceptance_criteria":"Derived curator output is distinguishable from primary input at the point the trigger is evaluated. A curator that writes memories does not thereby schedule itself again. There is a regression test that would fail if derived output were counted, with the feedback-loop rationale recorded in the test so the guard is not removed as redundant.","status":"open","priority":1,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-07-29T15:47:44Z","created_by":"Sam Catlow","updated_at":"2026-07-29T15:47:44Z","dependencies":[{"issue_id":"archie-core-035","depends_on_id":"archie-core-yp9","type":"parent-child","created_at":"2026-07-30T01:47:43Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-89x","title":"Curator runtime: persistent loop with idle cooldown","description":"Implement the loop that runs a registered curator: continuous operation while work is available, backing off to a configured cooldown when there is nothing to do, waking on new input, and honouring per-curator check-in intervals.","acceptance_criteria":"A curator with pending input runs without waiting for its next interval; an idle curator consumes no meaningful CPU and wakes on new input. Cooldown and check-in interval are configurable per curator. Loop timing is tested with a fake clock, not wall-clock sleeps. Shutdown is clean and bounded: an in-flight curator pass is cancelled via context and the daemon does not block indefinitely on it. A panicking curator is recovered and isolated from other curators and from the agent loop.","status":"open","priority":1,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-07-29T15:47:43Z","created_by":"Sam Catlow","updated_at":"2026-07-29T15:47:43Z","dependencies":[{"issue_id":"archie-core-89x","depends_on_id":"archie-core-yp9","type":"parent-child","created_at":"2026-07-30T01:47:43Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} @@ -159,6 +166,13 @@ {"_type":"issue","id":"archie-core-s1r","title":"Test forge fakes missing LinkBranch method broke go vet/test for whole module","description":"forge.Forge gained LinkBranch(ctx, owner, repo, issueNumber, branch) error in the branch-linking feature (ff4c51e) but the hand-rolled test doubles (stubForge in cmd/archied/main_test.go, prCapturingForge in cmd/archie-agent/taskrun_test.go, testForge in internal/daemon/daemon_test.go, fakeForge in internal/forgerpc/forgerpc_test.go) never got the method added, so they stopped satisfying forge.Forge. This broke go vet ./... and go test ./... for the entire module, not just those 4 packages, since go vet type-checks all test files as part of module vet. Fixed by adding LinkBranch stubs to all four fakes.","status":"closed","priority":1,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-07-24T03:04:53Z","created_by":"Sam Catlow","updated_at":"2026-07-24T03:04:58Z","closed_at":"2026-07-24T03:04:58Z","close_reason":"Added LinkBranch stub methods to stubForge, prCapturingForge, testForge, and fakeForge. go build/vet/test ./... now clean across the whole module.","dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-633","title":"config.docker.toml missing required fields, no overlay merge implemented","description":"config.docker.toml was rewritten to be a docs-as-overlay file (comment says base+overlay merge) but internal/config.Load has no merge logic and docker-compose.yml mounts only config.docker.toml at /etc/archie/config.toml. It is missing bot_user, [forge], [dispatch], [models], [providers], [budgets] which Load requires -\u003e daemon fails to start in docker as currently configured. Implement real base+overlay config loading (or restore a full standalone docker config) so there is one source of truth.","status":"closed","priority":1,"issue_type":"bug","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-07-24T02:42:07Z","created_by":"Sam Catlow","updated_at":"2026-07-24T02:44:53Z","started_at":"2026-07-24T02:42:11Z","closed_at":"2026-07-24T02:44:53Z","close_reason":"Implemented config.LoadOverlay (base decode + overlay decode into same struct, then shared finalize/validate), wired -config-overlay flag in cmd/archied, fixed docker-compose.yml to mount both base config.toml and config.docker.toml overlay, minimized config.docker.toml to true diff-only overlay, added tests proving overlay-omitted required fields (bot_user, repos) still come from base.","dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-u64","title":"Daemon: process multiple tasks concurrently (max_concurrency enforcement)","description":"Daemon currently processes one task at a time (docs/prds/archie-core-v2-architecture.md Phase 2). This is the core blocker between current state and any multi-agent scaling mode — needed before container max_concurrency or same-repo concurrency can matter. Wire the daemon's dispatch loop to run N tasks in parallel, respecting a configurable max_concurrency.","design":"internal/container/pool.go already enforces max_concurrency for container lifecycle — reuse that limit/pattern in the daemon's task dispatch rather than inventing a second concurrency control.","acceptance_criteria":"Daemon dispatch loop runs multiple tasks concurrently up to a configured max_concurrency limit; single-task-at-a-time behavior is gone.","status":"closed","priority":1,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-07-23T19:36:31Z","created_by":"Sam Catlow","updated_at":"2026-07-23T21:37:42Z","started_at":"2026-07-23T21:29:41Z","closed_at":"2026-07-23T21:37:42Z","close_reason":"Implemented concurrent SQLite and NATS task dispatch using containers.max_concurrency, with default same-repo serialization and race-tested dispatcher coverage.","dependency_count":0,"dependent_count":2,"comment_count":0} +{"_type":"issue","id":"archie-core-60f","title":"Seed a default SOUL without clobbering user edits","description":"Write a starter SOUL on first run and allow upgrading untouched scaffolding in place, following Hermes' is_legacy_template_soul approach: compare normalised content against known-shipped templates, which carry zero user intent, and only replace on an exact match.","acceptance_criteria":"First run seeds a documented starter SOUL. A SOUL matching a known shipped template can be upgraded in place. A SOUL the user has edited in any way is never modified. Comparison normalises line endings and trailing whitespace so a CRLF checkout does not defeat it.","status":"open","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-07-29T16:09:58Z","created_by":"Sam Catlow","updated_at":"2026-07-29T16:09:58Z","dependencies":[{"issue_id":"archie-core-60f","depends_on_id":"archie-core-4gv","type":"parent-child","created_at":"2026-07-30T02:09:57Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-t08","title":"Reconcile SOUL with PersonaRegistry and the six built-in personas","description":"Decide what happens to DefaultPersonas() (archie, helpful, concise, technical, creative, teacher) and the /personality command once SOUL owns identity. Options: SOUL replaces the default archie persona and the rest remain selectable style modifiers; or personas become seed templates a user copies into their SOUL; or personas are retired. Currently GetActive composes the baseline archie prompt with the selected persona, so the interaction with SOUL must be explicit rather than emergent.","acceptance_criteria":"Precedence between SOUL and a selected persona is defined and documented. /personality either keeps working with stated semantics or is removed deliberately. No path lets a persona selection blank out the user's SOUL without them asking.","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-07-29T16:09:57Z","created_by":"Sam Catlow","updated_at":"2026-07-29T16:09:57Z","dependencies":[{"issue_id":"archie-core-t08","depends_on_id":"archie-core-4gv","type":"parent-child","created_at":"2026-07-30T02:09:57Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-3fb","title":"worktree.Manager gets an empty token when the forge degrades","description":"Since 518a1a0 a missing forge credential disables the forge instead of stopping archied. resolveForge returns an empty token in that case and cmd/archied/main.go still hands it to worktree.Manager{Token: token}. If repos are configured while the forge is disabled, clone/push fails at push time rather than at startup. This is the intended trade -- a deferred error beats a crash loop -- but the failure is currently discovered late and its message will not explain that the cause is an unconfigured forge.","acceptance_criteria":"A worktree operation attempted with no forge credential fails with a message naming the missing forge configuration as the cause, rather than a bare git transport error. Alternatively the manager refuses the operation up front. Either way the operator can tell why from the error alone.","status":"open","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-07-29T16:09:21Z","created_by":"Sam Catlow","updated_at":"2026-07-29T16:09:21Z","dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-bfw","title":"install.sh: --force is advertised but does nothing","description":"FORCE_BUILD is initialised at install.sh:42 and set at :67 by --force, then never read. --help advertises '--force Force rebuild binaries even if up to date', so the flag is documented, accepted, and inert. The build step always rebuilds unconditionally, which means the flag is either redundant (delete it and the help line) or the up-to-date check it implies was never written.","acceptance_criteria":"Either the flag and its help text are removed, or an up-to-date check exists that --force actually bypasses. No advertised flag is inert.","status":"open","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-07-29T16:09:02Z","created_by":"Sam Catlow","updated_at":"2026-07-29T16:09:02Z","dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-c6o","title":"install.sh: unknown flags are silently ignored","description":"The 'for arg in $@' case statement has no default branch, so a mistyped flag does nothing and the installer proceeds with defaults. '--no-systmd' installs the systemd service the user was trying to skip. Options discussed 2026-07-30: (a) reject unknown args with exit 1; (b) warn on stderr and continue; (c) reject unknown --flags but ignore bare words. Recommendation was (a) -- this is an interactive installer run by hand, typos dominate, and silent wrong behaviour is the worst outcome; the forward-compatibility argument for (b) does not apply while there is no ecosystem of wrapper scripts. Awaiting Sam's decision.","acceptance_criteria":"A mistyped flag produces a clear diagnostic rather than silently different behaviour. The chosen policy is applied consistently and reflected in --help.","status":"open","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-07-29T16:09:02Z","created_by":"Sam Catlow","updated_at":"2026-07-29T16:09:02Z","dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-utt","title":"install.sh: linger detection claims success it did not verify","description":"install.sh greps 'loginctl show-user $USER' for 'Linger=no'. When show-user fails or prints nothing -- no logind session, a container, USER unset -- the grep fails and control falls to the else branch, which prints '[OK] User linger is already enabled.' Nothing was verified and linger is never enabled, so systemd --user dies at logout. Worst for someone installing on a remote box over SSH: Archie works while they are connected and stops when they disconnect. Discussed 2026-07-30, fix agreed but not applied.","acceptance_criteria":"Detection tests for the positive (Linger=yes) and attempts enable-linger in every other case, including when show-user fails. Uses $(id -un) rather than $USER, which is unset in some container and cron contexts and would abort under set -u. enable-linger is idempotent so a redundant call is harmless. No branch claims linger is enabled without having observed it.","status":"open","priority":2,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-07-29T16:09:01Z","created_by":"Sam Catlow","updated_at":"2026-07-29T16:09:01Z","dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-547","title":"install.sh delegates config generation to archied setup","description":"Remove the TOML-generating branches from install.sh and call the binary it just built. Ends the class of bug where the installer's idea of the config schema drifts from the daemon's.","acceptance_criteria":"install.sh contains no TOML templates and no sed-patching of config files. It invokes archied setup for a fresh install and skips it when a config already exists. A non-interactive install still produces a valid config or fails loudly. The forge_block helper and its awk splice are deleted.","status":"open","priority":2,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-07-29T16:02:51Z","created_by":"Sam Catlow","updated_at":"2026-07-29T16:02:51Z","dependencies":[{"issue_id":"archie-core-547","depends_on_id":"archie-core-cbk","type":"blocks","created_at":"2026-07-30T02:02:56Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-547","depends_on_id":"archie-core-ewk","type":"parent-child","created_at":"2026-07-30T02:02:50Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-114","title":"Curator observability surface","description":"Give curator activity visibility: which curators are registered, when each last ran, what it changed, and why. Background agents mutating memory unobserved is the failure mode this epic most needs to avoid.","acceptance_criteria":"Registered curators, their schedule state, and their recent activity are inspectable at runtime. Each recorded action carries enough context to answer why it happened. Surfaced through the existing observability paths rather than a bespoke channel.","status":"open","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-07-29T15:48:01Z","created_by":"Sam Catlow","updated_at":"2026-07-29T15:48:01Z","dependencies":[{"issue_id":"archie-core-114","depends_on_id":"archie-core-yp9","type":"parent-child","created_at":"2026-07-30T01:48:01Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-pek","title":"Bind curators to memory engines","description":"Wire the attached-memory-engine part of a curator's declared shape once the memory engine family exists, so a curator reads and writes through the engine contract rather than a concrete store.","acceptance_criteria":"A curator declares which memory engine it uses and receives it as a typed dependency. Swapping the configured engine changes where a curator's memories land with no change to the curator. A curator with no declared memory engine is a valid configuration and is rejected only if it attempts a memory operation.","status":"open","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-07-29T15:48:01Z","created_by":"Sam Catlow","updated_at":"2026-07-29T15:48:01Z","dependencies":[{"issue_id":"archie-core-pek","depends_on_id":"archie-core-1x7","type":"blocks","created_at":"2026-07-30T01:48:14Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-pek","depends_on_id":"archie-core-yp9","type":"parent-child","created_at":"2026-07-30T01:48:00Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-gs8","title":"Persistent session-memory curator (reference implementation)","description":"Ship a curator that maintains durable memory across sessions -- extracting and consolidating what is worth keeping from conversation history into the attached memory engine. The second contract consumer, and the one that exercises the curator/memory-engine binding.","acceptance_criteria":"Registers and runs through the registry with no special-casing. Writes through the memory engine contract rather than any concrete store. Extraction runs off the hot path so a chat turn never waits on it. What it wrote and why is inspectable. Honours the trigger-accounting invariant so its own writes do not reschedule it.","status":"open","priority":2,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-07-29T15:48:00Z","created_by":"Sam Catlow","updated_at":"2026-07-29T15:48:00Z","dependencies":[{"issue_id":"archie-core-gs8","depends_on_id":"archie-core-yp9","type":"parent-child","created_at":"2026-07-30T01:48:00Z","created_by":"Sam Catlow","metadata":"{}"},{"issue_id":"archie-core-gs8","depends_on_id":"archie-core-1x7","type":"blocks","created_at":"2026-07-30T01:48:14Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0} @@ -293,6 +307,8 @@ {"_type":"issue","id":"archie-core-5zh","title":"Promote archie-agent to per-task process; move workflow routing out of archied","description":"cmd/archie-agent exists but only executes one workflow stage per invocation over the internal/agentexec stdin/stdout JSON protocol (v1). Phase 1 of the PRD requires promoting it to the PRD's per-task process model, moving workflow.Route/workflow.Run out of archied and into archie-agent.","acceptance_criteria":"workflow.Route and workflow.Run execute inside archie-agent, not archied; archie-agent handles a full task (not a single stage) per invocation.","status":"closed","priority":2,"issue_type":"task","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-07-23T19:36:32Z","created_by":"Sam Catlow","updated_at":"2026-07-23T23:15:04Z","started_at":"2026-07-23T21:51:46Z","closed_at":"2026-07-23T23:15:04Z","close_reason":"All sub-issues (5zh.1 Store RPC, 5zh.2 Forge RPC, 5zh.3 worktree Prepare/Push RPC, 5zh.5 curated TaskConfig payload, 5zh.6 TaskContext interface refactor, 5zh.7 archie-agent full-task handler, 5zh.9 register RPC servers, 5zh.8 daemon handoff) are closed. Original acceptance criterion met: workflow.Route and workflow.Run execute inside archie-agent, not archied, in sandboxed NATS+container mode; archie-agent handles a full task per invocation. inprocess/subprocess modes unaffected.","dependencies":[{"issue_id":"archie-core-5zh","depends_on_id":"archie-core-l1q","type":"blocks","created_at":"2026-07-24T05:36:36Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":1,"comment_count":0} {"_type":"issue","id":"archie-core-l1q","title":"NATS transport: JetStream task queue + request-reply between daemon and archie-agent","description":"Phase 1 of docs/prds/archie-core-v2-architecture.md. internal/events.Bus (in-process pub/sub, already feeding SQLite + SSE) is the natural seam to replace the transport under. Daemon publishes tasks, archie-agent consumes, results return via NATS. Preserve current inprocess mode via [agent] mode default for local dev.","design":"Add optional [nats] config block (url, token_env), default anonymous auth for single-node, credentials required for multi-node per PRD sec.9 open question 2.","acceptance_criteria":"Daemon can dispatch a task to archie-agent over NATS JetStream and receive results via request-reply; inprocess mode still works unchanged.","status":"closed","priority":2,"issue_type":"feature","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-07-23T19:36:31Z","created_by":"Sam Catlow","updated_at":"2026-07-23T21:49:40Z","started_at":"2026-07-23T21:43:05Z","closed_at":"2026-07-23T21:49:40Z","close_reason":"Completed JetStream task dispatch and NATS agent request/reply, including token_env authentication for archied and canonical NATS_URL/NATS_TOKEN propagation to container workers; anonymous local mode remains supported and race-tested.","dependencies":[{"issue_id":"archie-core-l1q","depends_on_id":"archie-core-u64","type":"blocks","created_at":"2026-07-24T05:36:36Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":1,"comment_count":0} {"_type":"issue","id":"archie-core-rig","title":"Audit archie-core repo for bugs/improvements, file as Gitea issues","description":"Fan out exploration subagents across internal/ subsystems to find bugs, tech debt, and enhancement opportunities. Each confirmed finding gets filed as a Gitea issue on git.catlow.cloud/sam/archie-core.","status":"closed","priority":2,"issue_type":"task","assignee":"Sam Catlow","owner":"sam@catlow.tech","created_at":"2026-07-22T16:24:07Z","created_by":"Sam Catlow","updated_at":"2026-07-22T16:37:16Z","started_at":"2026-07-22T16:24:09Z","closed_at":"2026-07-22T16:37:16Z","close_reason":"Audit complete: 58 Gitea issues (#3-#60) filed at git.catlow.cloud/sam/archie-core. 60 raw findings, 59 verified, 58 successfully filed. 8 agents hit session limit at end (webui/workflow/worktree file-phase).","dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-ahw","title":"isForgeDisabled is duplicated in cmd/archied","description":"resolveForge in cmd/archied/main.go needs the none/off/disabled predicate, but the identical helper in internal/infrastructure/configuration is unexported, so 518a1a0 copied it with a comment noting the duplication. Two copies of a validation predicate drift: adding a fourth disabled-alias in one place silently leaves the other accepting it.","acceptance_criteria":"One definition of the disabled-forge predicate, referenced by both the configuration package and cmd/archied. The comment noting the duplication is removed with it.","status":"open","priority":3,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-07-29T16:09:22Z","created_by":"Sam Catlow","updated_at":"2026-07-29T16:09:22Z","dependency_count":0,"dependent_count":0,"comment_count":0} +{"_type":"issue","id":"archie-core-cg9","title":"install.sh: REPO_URL points at a repository that does not exist","description":"install.sh:26 sets REPO_URL to https://github.com/samcharles93/archie-core.git, which is not reachable; origin is https://git.catlow.cloud/sam/archie-core.git. Only affects the path where the installer is not run from a local clone -- i.e. the curl-to-shell install this script exists to serve. Sam is working locally for now and deliberately deferred this on 2026-07-30; filed so it is not forgotten before any public install path is offered.","acceptance_criteria":"REPO_URL resolves to a repository the installer can actually clone, or the clone path is removed in favour of requiring a local checkout.","status":"open","priority":3,"issue_type":"bug","owner":"sam@catlow.tech","created_at":"2026-07-29T16:09:03Z","created_by":"Sam Catlow","updated_at":"2026-07-29T16:09:03Z","dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-abg.22.19","title":"ratelimit.Limiter: evict stale per-key entries to bound memory","description":"internal/ratelimit's Limiter.hits map never removes entries for (platform, userID) pairs that stop being used -- a user who fires once and never again leaves a permanent (eventually-empty-slice) map entry for the life of the process. Not a bug today since the package isn't wired into any caller yet, but flagged by adversarial review as needing an eviction/TTL story before it's wired into a long-running daemon path handling many distinct/cycling identities (otherwise an eventual memory leak / DoS vector).","status":"open","priority":3,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-07-26T06:53:13Z","created_by":"Sam Catlow","updated_at":"2026-07-26T06:53:13Z","dependencies":[{"issue_id":"archie-core-abg.22.19","depends_on_id":"archie-core-abg.22","type":"parent-child","created_at":"2026-07-26T16:53:12Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-abg.5.4","title":"Telegram voice message transcription","description":"Hermes has STT enabled (local whisper + OpenAI whisper). Sam doesn't need full STT, but wants Telegram voice messages transcribed to text for the agent. Telegram voice messages arrive as audio attachments (voice note type, OGG/Opus format).\n\nScope:\n- Detect voice message type from MessageEvent\n- Transcribe using OpenAI whisper API (or local whisper via Ollama)\n- Inject transcription into message text before routing to LLM\n- Cache transcriptions to avoid re-transcribing duplicate messages","status":"open","priority":3,"issue_type":"feature","owner":"sam@catlow.tech","created_at":"2026-07-26T00:16:16Z","created_by":"Sam Catlow","updated_at":"2026-07-26T00:16:16Z","dependencies":[{"issue_id":"archie-core-abg.5.4","depends_on_id":"archie-core-abg.5","type":"parent-child","created_at":"2026-07-26T10:16:16Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0} {"_type":"issue","id":"archie-core-abg.29v","title":"Verify: Scale-to-zero: idle detection and dormant quiesce","acceptance_criteria":"Independent adversarial review by fresh agent. Verify: no dead code paths, no lint issues (golangci-lint run clean), tests pass (go test ./...), code is formatted (gofmt), no hardcoded values in tests. Review the implementation against the original acceptance criteria. Report findings or confirm clean.","status":"closed","priority":3,"issue_type":"task","owner":"sam@catlow.tech","created_at":"2026-07-25T14:14:22Z","created_by":"Sam Catlow","updated_at":"2026-07-28T17:05:17Z","closed_at":"2026-07-28T17:05:17Z","close_reason":"Deliverable is a review, not code: the only acceptance criterion is 'Independent adversarial review by fresh agent ... Report findings or confirm clean'. CLAUDE.md's Development Protocol already makes an adversarial verification pass mandatory in the definition-of-done for the paired implementation bead, so tracking it as a separate ticket is a review campaign with no code output. Verification still happens - it is folded into the parent implementation issue.","dependencies":[{"issue_id":"archie-core-abg.29v","depends_on_id":"archie-core-abg.29","type":"blocks","created_at":"2026-07-26T00:20:37Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":1,"dependent_count":0,"comment_count":0}