Honcho memory engine as the external-provider proof #13

Closed
opened 2026-10-27 13:34:35 +00:00 by sam · 0 comments
Owner

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 -> Peer -> Session -> 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.

Acceptance Criteria

The 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.

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.


Imported from beads archie-core-1786637492031-86-0fcaccc0 · GitHub #107 · type feature · priority P2 · created 2026-08-08 · closed 2026-09-01

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 -> Peer -> Session -> 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. ### Acceptance Criteria The 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. ### 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. --- _Imported from beads `archie-core-1786637492031-86-0fcaccc0` · GitHub #107 · type feature · priority P2 · created 2026-08-08 · closed 2026-09-01_
sam added the mediumfeature labels 2026-10-27 13:34:35 +00:00
sam self-assigned this 2026-10-27 13:34:35 +00:00
sam closed this issue 2026-10-27 13:34:35 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#13