This commit is contained in:
+10
-1
@@ -48,6 +48,16 @@ They are shallow snapshots for study, not dependencies or vendored source.
|
||||
- `openclaw/openclaw`
|
||||
- `anomalyco/opencode`
|
||||
|
||||
DeepSeek Harness at the captured revision is MIT-licensed experimental software,
|
||||
but it is a large Node/TypeScript workspace with a React web client, Cordis
|
||||
plugin tree, native/platform payloads, and a broad third-party closure. Its own
|
||||
safety notice says it is unaudited and can access processes, files, credentials,
|
||||
and the network exposed to it. We will study its service seams, durable event
|
||||
log, approval flow, ACP profile, and agent lifecycle. We will not embed its web
|
||||
shell into Lumbridge or treat its sandbox as a security boundary. Any branded
|
||||
fork is a separate repository/process with preserved notices and an explicit
|
||||
dependency and payload review.
|
||||
|
||||
## Research questions
|
||||
|
||||
1. Which terminal core gives us correctness without inheriting a product-shaped
|
||||
@@ -60,4 +70,3 @@ They are shallow snapshots for study, not dependencies or vendored source.
|
||||
must remain measured or unavailable?
|
||||
6. Can one event model cover PTY, ACP, Git, usage, permissions, and recovery
|
||||
without turning into untyped JSON everywhere?
|
||||
|
||||
|
||||
Reference in New Issue
Block a user