popoto.integrations.demo¶
popoto.integrations.demo
¶
The popoto-memory demo loop: assemble, inject, capture, report.
Runs the entire subconscious cycle against a local Redis or Valkey with no harness installed and no API keys, so a developer can see what the hook does before wiring it into anything. Every step prints what it did, including which extraction provider wrote the record -- the write path is the part most worth seeing, because it is where memory systems usually differ.
SEED_MEMORIES = [('Deploys use blue-green with automatic rollback on health-check failure', 0.9), ('The staging database is reset every night at 02:00 UTC', 0.6), ('Rate limits are enforced in the gateway, not in each service', 0.7), ('Frontend bundles are built with esbuild, not webpack', 0.5)]
module-attribute
¶
Fixture memories for the demo. Distinct topics, so the retrieval step visibly selects rather than returning everything.
run_demo(agent_id='popoto-memory-demo', keep=False, out=None)
¶
Seed, retrieve, capture, and report -- printing each step.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
agent_id
|
str
|
Partition to seed and query. Isolated from real memories by default so the demo cannot pollute a project's corpus. |
'popoto-memory-demo'
|
keep
|
bool
|
Leave the seeded records in Redis when finished. |
False
|
out
|
Optional[TextIO]
|
Stream to write the transcript to. Defaults to |
None
|
Returns:
| Type | Description |
|---|---|
int
|
|
int
|
not complete. |
Source code in src/popoto/integrations/demo.py
28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 | |