chore(beads): close Honcho engine proof as deprioritized

This commit is contained in:
sam committed 2026-09-02 02:52:02 +10:00
1 parent 3f1e4944ef
commit a94b68d39c
2 files changed
+2 -1

No files matched your search

+1
View File
@@ -161,3 +161,4 @@
{"id":"int-c7304b2101eb73c6404d8508da30e2be","kind":"field_change","created_at":"2026-09-01T16:44:37.765726853Z","actor":"Sam Catlow","issue_id":"archie-core-1786637490043-10-711c450a","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Complete, all four AC clauses:\n\n- config.MemoryConfig.Engine field added with toml/yaml/json tags;\n Provider/ProviderConfig/SessionTTL also gained the toml tags they were\n missing (repo convention, config.toml is the primary format).\n- validateMemory (internal/infrastructure/configuration/validate.go)\n rejects an engine name outside memoryEngines with\n \"%w: memory.engine %q (want %s)\", the same named-constant-list +\n oneOf/list shape forge.type already uses. TestValidateMemoryNames\n TheValidSet pins the exact message.\n- applyMemoryDefaults resolves an absent engine to \"builtin\"\n (memoryEngineBuiltin), verified by\n TestApplyMemoryDefaultsFillsAbsentEngineWithBuiltin, and an explicit\n value is left alone (TestApplyMemoryDefaultsLeavesExplicitValuesAlone).\n- config.example.toml documents [memory] engine alongside the existing\n provider field, distinguishing the two mechanisms.\n\nSince closing this, archie-core-1786637499480 (ship builtin as default)\nlanded the bootstrap wiring that actually consumes cfg.Memory.Engine, so\nthe field is not just parsed and validated but live end to end."}}
{"id":"int-432ac25baf4f85d1a9f04ff494d0bc62","kind":"field_change","created_at":"2026-09-01T16:47:57.576063469Z","actor":"Sam Catlow","issue_id":"archie-core-1786637499636-376-2f94082e","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Complete, all three AC clauses:\n\n- A curator declares its memory engine via Manifest.MemoryEngine and\n receives it as a typed dependency: curator.Registrar.MemoryEngines\n (Get(name) (domainmemory.MemoryEngine, bool)), same trust model as\n ToolBuilder.Build(ctx, declared) -- the curator calls Get with its own\n declared name, not handed a pre-resolved instance. Registration\n enforces presence exactly like Tools/Skills: declared with no\n MemoryEngineSource on the host is rejected at Register\n (TestRegistryDeclaredCapabilitiesRequireHostServices' two new cases),\n and filter() clears the field from a curator's view when undeclared\n (TestRegistryBindFiltersToDeclaredCapabilities).\n- Swapping the configured engine changes where memories land with no\n curator code change: nothing about a curator names a concrete engine,\n only the string it declared, resolved fresh through whichever registry\n it was bound to.\n- A curator with no declared engine stays valid (pre-existing behavior,\n now covered by table cases) and can only ever be affected by a memory\n operation it structurally cannot attempt, since MemoryEngines is nil\n in its view.\n\nWired end to end: internal/app/archied/bootstrap.go:setupCurators passes\nb.memEngines (*domainmemory.Registry, set by setupMemoryAll which Run()\ncalls before setupCurators) straight in -- it already satisfies\nMemoryEngineSource with no adapter.\n\ngo test ./... is green; task lint is 0 issues."}}
{"id":"int-8e36a6b86a595feaebaa50956eb01382","kind":"field_change","created_at":"2026-09-01T16:51:00.094507904Z","actor":"Sam Catlow","issue_id":"archie-core-1786637499161-356-e424e40d.1","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Fixed, but not as originally framed. Investigated wiring RegisterExternal\nfor real: there is no external MemoryProvider implementation anywhere in\nthe repo to construct and pass to it (only internal/memory/builtin.Provider\nexists) -- calling RegisterExternal would be dead plumbing to nothing, not\na fix.\n\nThe actual fix: configuration.validateMemory now rejects memory.provider\nbeing set at all, with a clear reason, instead of accepting it and doing\nnothing. Turns the silent no-op into a loud one. setupMemory's doc comment\nand config.example.toml updated to match; the now-pointless\nprovider_config example section removed.\n\ntoml struct tags (the other half of this bug) were already fixed in\narchie-core-1786637490043's commit.\n\nDrop the rejection once a real external provider (or the domain/memory\nengine family's Honcho proof, archie-core-1786637492031) gives the field\nan effect again.\n\nTestValidateMemoryRejectsProviderSetToAnything covers it. task check is\ngreen."}}
{"id":"int-9633d649a25f789b25865683d74755f7","kind":"field_change","created_at":"2026-09-01T16:51:58.124722776Z","actor":"Sam Catlow","issue_id":"archie-core-1786637492031-86-0fcaccc0","extra":{"field":"status","new_value":"closed","old_value":"open","reason":"Deprioritized by Sam (2026-09-02): not a current priority. Re-open when there's actual appetite to build against a live Honcho instance -- the engine contract it would implement against (domain/memory.MemoryEngine) is done and stable, so this is unblocked whenever picked back up, not superseded by anything."}}
+1 -1
View File
@@ -522,7 +522,7 @@
{"_type":"issue","id":"archie-core-1786637492113-89-a9c21168","title":"Multi-agent collaboration: many agents working together","description":"Support multiple agents working in combination — not just one agent per task in isolation, but agents coordinating with each other (e.g. on the same repo, the same task, or a decomposed set of related tasks). Scope, coordination model, and conflict-avoidance strategy are all undefined — this is exploratory. No implementation approach has been decided yet.\n\n### Acceptance Criteria\n\nA PRD exists (docs/prds/) covering: what 'multiple agents working in combination' means concretely for archie-core, how agents discover/hand off work to each other, how conflicts (same repo, same worktree, shared state) are avoided or resolved, and what changes to daemon/workflow/dispatch are implied. No code changes required to close this epic — the PRD is the deliverable.","status":"open","priority":2,"issue_type":"epic","created_at":"2026-08-08T14:34:48Z","updated_at":"2026-08-08T15:35:40Z","external_ref":"https://github.com/samcharles93/archie-core/issues/110","source_system":"github:https://github.com/samcharles93/archie-core/issues/110:110","metadata":null,"labels":["epic"],"dependency_count":0,"dependent_count":0,"comment_count":0}
{"_type":"issue","id":"archie-core-1786637492083-88-a3a3fbff","title":"Evaluate internal/workflow architecture and APIs","description":"Perform a read-only, repository-grounded evaluation of internal/workflow. Identify correctness, definition clarity, reuse, interface ownership, coupling, testability, and maintainability improvements, with concrete evidence and prioritized recommendations.\n\n### Acceptance Criteria\n\nAssessment covers package definitions, consumers, subpackages, tests, and architecture invariants; findings are prioritized with file references and actionable recommendations; no code or git changes are made.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:34:44Z","updated_at":"2026-08-08T15:35:18Z","closed_at":"2026-08-08T15:35:19Z","external_ref":"https://github.com/samcharles93/archie-core/issues/109","source_system":"github:https://github.com/samcharles93/archie-core/issues/109:109","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
{"_type":"issue","id":"archie-core-1786637492059-87-2f0e575d","title":"Regression tests: internal/gate — GateContext, Finding types, Yaegi evaluation","description":"internal/gate/gate.go has zero tests. GateContext and Finding are the runtime types that custom gate scripts receive. The Yaegi evaluation path (gateeval) has tests, but the gate package itself has none. Add tests for type construction, finding validation, and integration with the gate evaluation pipeline.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:34:40Z","updated_at":"2026-08-08T14:34:42Z","closed_at":"2026-08-08T14:34:43Z","external_ref":"https://github.com/samcharles93/archie-core/issues/108","source_system":"github:https://github.com/samcharles93/archie-core/issues/108:108","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
{"_type":"issue","id":"archie-core-1786637492031-86-0fcaccc0","title":"Honcho memory engine as the external-provider proof","description":"Implement an engine backed by Honcho (plastic-labs/honcho, cloned at /work/clones/honcho) to prove the seam holds for a real external backend. Honcho's model is Workspace -\u003e Peer -\u003e Session -\u003e Message with asynchronously derived conclusions queried back as representations; its dual-peer convention has the assistant observe others without self-modelling. Treat this as validation of the contract, not as a dependency of the default install.\n\n### Acceptance Criteria\n\nThe engine satisfies the contract with no changes to the agent loop or gateway. Archie runs unchanged when it is not configured. Its network calls carry timeouts and its failures degrade to reported errors rather than failing a turn. Any mapping decision between Archie sessions/identities and Honcho peers/sessions is documented. Unit tests use httptest and never require a live Honcho instance, per the repo testing rule.","status":"open","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:34:38Z","updated_at":"2026-08-08T14:34:38Z","external_ref":"https://github.com/samcharles93/archie-core/issues/107","source_system":"github:https://github.com/samcharles93/archie-core/issues/107:107","metadata":null,"labels":["enhancement"],"dependencies":[{"issue_id":"archie-core-1786637492031-86-0fcaccc0","depends_on_id":"archie-core-1786637499161-356-e424e40d","type":"parent-child","created_at":"2026-09-01T15:50:34Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
{"_type":"issue","id":"archie-core-1786637492031-86-0fcaccc0","title":"Honcho memory engine as the external-provider proof","description":"Implement an engine backed by Honcho (plastic-labs/honcho, cloned at /work/clones/honcho) to prove the seam holds for a real external backend. Honcho's model is Workspace -\u003e Peer -\u003e Session -\u003e Message with asynchronously derived conclusions queried back as representations; its dual-peer convention has the assistant observe others without self-modelling. Treat this as validation of the contract, not as a dependency of the default install.\n\n### Acceptance Criteria\n\nThe engine satisfies the contract with no changes to the agent loop or gateway. Archie runs unchanged when it is not configured. Its network calls carry timeouts and its failures degrade to reported errors rather than failing a turn. Any mapping decision between Archie sessions/identities and Honcho peers/sessions is documented. Unit tests use httptest and never require a live Honcho instance, per the repo testing rule.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:34:38Z","updated_at":"2026-09-01T16:51:58Z","closed_at":"2026-09-01T16:51:58Z","close_reason":"Deprioritized by Sam (2026-09-02): not a current priority. Re-open when there's actual appetite to build against a live Honcho instance -- the engine contract it would implement against (domain/memory.MemoryEngine) is done and stable, so this is unblocked whenever picked back up, not superseded by anything.","external_ref":"https://github.com/samcharles93/archie-core/issues/107","source_system":"github:https://github.com/samcharles93/archie-core/issues/107:107","metadata":null,"labels":["enhancement"],"dependencies":[{"issue_id":"archie-core-1786637492031-86-0fcaccc0","depends_on_id":"archie-core-1786637499161-356-e424e40d","type":"parent-child","created_at":"2026-09-01T15:50:34Z","created_by":"Sam Catlow","metadata":"{}"}],"dependency_count":0,"dependent_count":0,"comment_count":0}
{"_type":"issue","id":"archie-core-1786637492005-85-03c595e7","title":"feat(gateway): durable message deduplication via upstream IDs","description":"gateway.Message carries no upstream/channel-native message ID, so a re-delivered Telegram update appends a duplicate turn. Add Message.ID and derive the NellDB document ID from it (time-prefixed to preserve the ScanSince ID tie-break), making redelivery an idempotent LWW upsert.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:34:35Z","updated_at":"2026-08-08T15:34:01Z","closed_at":"2026-08-08T15:34:02Z","external_ref":"https://github.com/samcharles93/archie-core/issues/106","source_system":"github:https://github.com/samcharles93/archie-core/issues/106:106","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}
{"_type":"issue","id":"archie-core-1786637491986-84-5137df75","title":"feat(gateway): version the SQLite session schema before cutover","description":"OpenSQLiteSessionStore currently runs CREATE IF NOT EXISTS statements with no schema version or transactional migration record. Before production wiring, add the smallest deterministic schema-version mechanism so future upgrades cannot silently leave a partially evolved database.\n\n### Acceptance Criteria\n\nA fresh database records the current schema version; opening a supported older fixture migrates transactionally and preserves data; unsupported newer versions fail with an actionable error; migration failure leaves the prior schema/data usable; schema initialization and upgrades are covered by file-backed tests.","status":"closed","priority":2,"issue_type":"feature","created_at":"2026-08-08T14:34:33Z","updated_at":"2026-08-09T12:33:31Z","closed_at":"2026-08-09T12:33:32Z","external_ref":"https://github.com/samcharles93/archie-core/issues/105","source_system":"github:https://github.com/samcharles93/archie-core/issues/105:105","metadata":null,"labels":["enhancement"],"dependency_count":0,"dependent_count":0,"comment_count":0}
{"_type":"issue","id":"archie-core-1786637491959-83-a36ef6d7","title":"test(gateway): pin SQLite FTS lifecycle and literal-query semantics","description":"Trigger-driven FTS synchronization and hostile-query escaping were manually verified but are not retained by the trimmed SQLite-specific test suite. Preserve these SQLite-specific guarantees without duplicating the shared SessionStore contract.\n\n### Acceptance Criteria\n\nTable-driven tests show FTS search/count remains correct after message deletion, ReplaceMessages, and session deletion with no cross-session leak; hostile inputs including column syntax, unmatched quotes, NEAR, wildcard, and boolean operators return literal-match behavior without syntax errors; multi-term queries pin AND semantics; tests stay SQLite-specific and focused.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-08-08T14:34:29Z","updated_at":"2026-08-08T15:33:57Z","closed_at":"2026-08-08T15:33:58Z","external_ref":"https://github.com/samcharles93/archie-core/issues/104","source_system":"github:https://github.com/samcharles93/archie-core/issues/104:104","metadata":null,"labels":["task"],"dependency_count":0,"dependent_count":0,"comment_count":0}