docs: keep AnviLLM history professional
This commit is contained in:
parent
c8bc9cdbe8
commit
0a6fbe7f44
|
|
@ -27,12 +27,12 @@ State, recovery, cancellation, and message delivery must be explicit rather
|
|||
than inferred from terminal behavior. And orchestration belongs outside the
|
||||
agent core, where scripts and clients can evolve independently.
|
||||
|
||||
Ollie is the continuation of that research, not a repudiation of it. It keeps
|
||||
AnviLLM's strongest result—the 9P namespace as the API—while moving the agent
|
||||
loop, backends, tools, sandbox, persistence, and context management into a
|
||||
runtime designed for direct control. AnviLLM taught us what the filesystem
|
||||
surface could unlock; its dead ends taught us what the runtime must own. This
|
||||
log begins there, with gratitude.
|
||||
Ollie is the continuation of that research. It keeps AnviLLM's strongest
|
||||
result—the 9P namespace as the API—while moving the agent loop, backends,
|
||||
tools, sandbox, persistence, and context management into a runtime designed
|
||||
for direct control. AnviLLM established what the filesystem surface could
|
||||
unlock; its limitations clarified what the runtime must own. This log begins
|
||||
with that lineage.
|
||||
|
||||
How the Ollie system-of-systems emerged and evolved.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue