Actionist Knowledge Graph
P13 · Assembly knowledge node

Preview, editor and change loop

Clients need to alter the assembled product through conversation and direct visual controls without dissolving the composition back into arbitrary generated code.

Problem boundary

What this subsystem owns and what it must hand to the rest of Actionist.

What it owns

  • Live preview
  • Chat and direct-manipulation edits
  • Module add/remove/replace
  • Text/content and layout changes
  • Change plan, diff and undo

What research already found

  • The client should be able to pick side-nav/component variants and revise them in chat
  • Bounded edits against known assets are safer than free generation
  • Taste selection should happen before expensive code loops where possible

Open first-principles questions

  • Which edits are parameter changes versus code changes?
  • How does the editor preserve block upgradeability?
  • What is the undo/version model?
  • How are unsupported requests explained?

Inputs

  • AssemblyPlan
  • Running preview
  • Client instructions

Outputs

  • ChangePlan
  • UpdatedBindings
  • BoundedDiff
  • Version

Scientific research protocol

Every research owner uses the same evidence funnel. No padding is allowed when a denominator is inapplicable or evidence is unavailable.

Prior evidence auditRead the canonical spine, all domain-linked artifacts, the 17-industry catalogue and existing contradictions before searching again.
Commercial 100 → 10Define a denominator, map approximately 100 companies/products, and produce first-party dossiers for the strongest 10.
GitHub 100 → 10Search and dedupe approximately 100 relevant OSS projects, then deeply inspect the strongest 10 at the capability and architecture level.
Local estate joinInspect AutoSaaS, Great Library, SISOCRM, 21st stores and other domain-specific precedents already on the laptop.
Innovation 100 → 10Generate a wide divergent idea register, score it against the problem and retain the 10 strongest falsifiable innovations.
First-principles synthesisDecompose the irreducible problem, challenge inherited assumptions, reconcile contradictions and state the minimum sufficient design.
Contracts and experimentsReturn the proposed contract, dependency edges, unknowns, falsifiers, experiments, stop rules and decisions.
Independent verificationA separate verifier checks counts, links, source claims, overlap, contradictions and unsupported conclusions before promotion.

Evidence and agent outputs

Existing research remains source evidence. New agent packets are written to one owned workstream directory and linked here after verification.

ArtifactLocationState
Platform deep divesresearch/actionmodel-builder-research-2026-08-26/phase-2/outputs/platform-deepdives.mdexisting
Builder ecosystem reportresearch/packs/source-files/builder-ecosystem-report.mdexisting
UI pack gallery UXresearch/ui-pack-gallery-ux-2026-08-27.mdexisting
Future verified agent packetresearch/workstreams/P13-preview-editor-and-change-loop/runs/<run-id>/planned

Agent-sized objective

Define the editable surface and change taxonomy; prototype replace/add/remove/theme/text operations without arbitrary repo edits.

See sprint assignment →