Define Quasar as a basic typed graph editor #35

Merged

lost-rob0t merged 10 commits from research/quasar-product-architecture into main

2026-07-23 18:38:07 +00:00

lost-rob0t commented

2026-07-23 17:59:15 +00:00

(Migrated from github.com)

What changed

add QUASAR-001 Basic Typed Graph Editor Architecture
correct QUASAR-RESEARCH-000, QUASAR-RESEARCH-001, and QUASAR-RESEARCH-002
update the fourth-generation index with the corrected product boundary
recenter Quasar on graph-document editing rather than domain-server orchestration
define the minimal node, edge, graph metadata, command, revision, undo, persistence, import/export, and live-update model
define Quasar's own optional action and transform extension API
define a Quasar-owned graph-document wire protocol and QuasarClient
keep advanced investigation views, evidence workflows, actors, remote workers, and distributed runtime infrastructure optional

Correct ownership boundary

Quasar owns

graph documents, typed nodes, and typed edges
graph commands, graph-operation batches, revisions, undo, and redo
graph rendering, layout, selection, and view state
context-menu actions and action discovery
transform declarations, invocation, progress, cancellation, and result application
Quasar protocol types, validators, reconnect behavior, and action events

Star-Lang owns

typed document and relation specifications
specification libraries, datasets, identifiers, and compatible data contracts
actors, programs, declarative playbooks, checkpoints, and resumable analysis-run semantics
generated bindings and lifecycle envelopes used only inside explicit interoperability adapters

Star-Lang does not provide Quasar transforms or context-menu actions. A Star-Lang playbook may invoke a registered Quasar action through an adapter, but the transform remains a Quasar extension or external integration.

Core architecture

React + Cytoscape client
        |
        | Quasar graph-document protocol
        v
thin Common Lisp Quasar service
        |
        +--> optional Quasar actions
        +--> optional Star-Lang adapter
        +--> optional StarIntel / actor / service adapters
        |
        v
graph-document storage

The core does not require StarIntel, a Star-Lang runtime, cl-gserver/Sento, domain servers, ZeroMQ, external workers, GraphQL, or Socket.IO.

MVP acceptance boundary

create, edit, connect, move, delete, save, reopen, import, export, undo, and redo typed graph elements
function with no Star-Lang runtime and no StarIntel server
function with no installed actions or domain servers
optionally load compatible Star-Lang type and relation definitions through an adapter
optionally invoke one local Quasar action and apply its validated Quasar graph batch

Validation

exactly five intended files are changed
all three prior Quasar research notes now carry the corrected ownership boundary
false Star-Lang transform, Star-Lang action, and Star-Lang graph batch ownership language was removed
temporary correction workflows self-deleted and are absent from the final diff
no runtime implementation is introduced in this pass

## What changed - add `QUASAR-001 Basic Typed Graph Editor Architecture` - correct `QUASAR-RESEARCH-000`, `QUASAR-RESEARCH-001`, and `QUASAR-RESEARCH-002` - update the fourth-generation index with the corrected product boundary - recenter Quasar on graph-document editing rather than domain-server orchestration - define the minimal node, edge, graph metadata, command, revision, undo, persistence, import/export, and live-update model - define Quasar's own optional action and transform extension API - define a Quasar-owned graph-document wire protocol and `QuasarClient` - keep advanced investigation views, evidence workflows, actors, remote workers, and distributed runtime infrastructure optional ## Correct ownership boundary ### Quasar owns - graph documents, typed nodes, and typed edges - graph commands, graph-operation batches, revisions, undo, and redo - graph rendering, layout, selection, and view state - context-menu actions and action discovery - transform declarations, invocation, progress, cancellation, and result application - Quasar protocol types, validators, reconnect behavior, and action events ### Star-Lang owns - typed document and relation specifications - specification libraries, datasets, identifiers, and compatible data contracts - actors, programs, declarative playbooks, checkpoints, and resumable analysis-run semantics - generated bindings and lifecycle envelopes used only inside explicit interoperability adapters Star-Lang does **not** provide Quasar transforms or context-menu actions. A Star-Lang playbook may invoke a registered Quasar action through an adapter, but the transform remains a Quasar extension or external integration. ## Core architecture ```text React + Cytoscape client | | Quasar graph-document protocol v thin Common Lisp Quasar service | +--> optional Quasar actions +--> optional Star-Lang adapter +--> optional StarIntel / actor / service adapters | v graph-document storage ``` The core does not require StarIntel, a Star-Lang runtime, cl-gserver/Sento, domain servers, ZeroMQ, external workers, GraphQL, or Socket.IO. ## MVP acceptance boundary - create, edit, connect, move, delete, save, reopen, import, export, undo, and redo typed graph elements - function with no Star-Lang runtime and no StarIntel server - function with no installed actions or domain servers - optionally load compatible Star-Lang type and relation definitions through an adapter - optionally invoke one local Quasar action and apply its validated Quasar graph batch ## Validation - exactly five intended files are changed - all three prior Quasar research notes now carry the corrected ownership boundary - false `Star-Lang transform`, `Star-Lang action`, and `Star-Lang graph batch` ownership language was removed - temporary correction workflows self-deleted and are absent from the final diff - no runtime implementation is introduced in this pass