App ComposerLoftwah’s instance

Apps and shortcuts

Browse all apps

Diagram atlas

See the system.
Then edit the source.

These diagrams explain the parts that are easy to blur: the lifecycle, the human approval boundary, contribution visibility and environment isolation. Each is a native LDraw scene you can reopen and revise.

What these are for

They are working explanations, not decorative art or screenshots. Text, arrows and boxes stay editable. The SVG and PNG are rendered from the same scene you can download.

Rendered with @excalidraw/excalidraw@0.18.1 through LDraw’s existing renderer. The source scene, SVG and PNG are committed together; the page does not call a live diagram service.

Four App Composer stages: Get Ready prepares local tools, source and Cloudflare access; Init produces a validated brief, content model and source pins; EmDash supplies native admin, collections, typed fields and plugin contracts; the application lifecycle covers deploy, observe, update and recover. Owner decisions and evidence stay separate.
Get Ready → Init → EmDash → application lifecycleEach stage produces something the next can inspect. Owner authority and release evidence do not move into the happy path.Download editable sceneSVGPNGOpen LDrawGet Ready
Read this diagram as text
  1. Get ReadyChecks local tools, GitHub source, Cloudflare access and the exact HTTPS result. A local or provider pass stays scoped to that environment.
  2. InitTurns the owner’s brief into a validated specification, content model, app settings and exact source pins.
  3. EmDashProvides the native admin, collections, typed fields and plugin contracts used to run editable content.
  4. Application lifecycleCovers deploy, observe, update and recover. A local pass is not a deployed release; provider, device and owner acceptance stay separate.
A local agent inspects an authorised workspace and returns a reviewable proposal. A signed-in human accepts, sends back with notes or rejects it. Proposal review rechecks the submitted source and accepted proposal digest. A manual handoff leads to the existing release guard with clean pushed main, app scope, checks and live verification. The execution adapter is not connected. The agent grant cannot approve, deploy, merge, spend, read secrets or change access.
Local agent → human review → separate release handoffRevised through the local LDraw MCP by a Codex session, then curated for readable publication. Approval and execution remain separate actions.Download editable sceneSVGPNGOpen LDrawAgent entryArchitecture
Read this diagram as text
  1. Local agentUses the owner’s machine, model and selected workspace under a read-only scope.
  2. Scoped proposalRecords source identity, cited evidence, risk, unknowns and one bounded change.
  3. Human reviewAccept, send back with notes, or reject. Returning work preserves prior findings, links and versions.
  4. Execution boundaryApproval does not execute. The execution adapter is not connected; a separate manual handoff uses the existing clean pushed-main release path, scoped environment, checks and live verification.
Production has a Worker with exact pushed-main source and release identity, plus production D1, R2 and KV. Preview has a separate Worker selected at build time, distinct preview D1, R2 and KV, and no audience. Production service bindings are absent in Preview. A dashed boundary separates resources and secrets.
Production, Preview and resource isolationA missing Preview binding fails closed. It does not fall back to production.Download editable sceneSVGPNGOpen LDrawArchitecture
Read this diagram as text
  1. ProductionPublic routes plus an Access-protected admin. The exact pushed-main source and Worker release identity are recorded.
  2. PreviewSelects CLOUDFLARE_ENV at build time, uses distinct preview resources and remains closed without an audience.
  3. Separate resources and secretsPreview D1, R2 and KV do not inherit production. Production service bindings are absent rather than substituted.
  4. Fail closedWhen a Preview binding, secret or environment value is missing, the correct result is an explicit failure, not a production fallback.
Here / there receives a pending postcard. An owner approves it; Linkarooie features it only after an explicit selection. Hiding the source item removes its dependent public card and media. Approval and featuring remain separate actions.
A pending postcard, an approval and a separate featuring choiceA model-driven revision of the maintained journey preset. Composer orange and the documented Linkarooie lime family retain their distinct roles; this explains the implemented publication boundary.Download editable sceneSVGPNGOpen LDrawBuild story
Read this diagram as text
  1. PendingThe submission is private until the source owner approves it.
  2. ApprovedApproval makes the source item eligible; it does not feature it in Linkarooie.
  3. FeaturedThe owner selects the approved source item explicitly in Linkarooie.
  4. Hidden at sourceCurrent source visibility removes the dependent public card and media.

Revise one without starting again

  1. Download the .excalidraw scene.
  2. Open it in LDraw. The drawing keeps its element IDs, text and connections.
  3. Edit the source, export SVG and PNG, and replace all three files together.
  4. Inspect the result at phone and desktop widths before publishing. Automated tests cannot certify that a diagram is clear or technically true.

Read the full architecture · Point your agent at Composer