DreamWeave engineering

War Room

DreamWeave engineering · source, dependencies, releases, and the supply line.

Blocked
1 plan
Campaigns
2 open
Releases
none planned

Everything here comes from a few TOML files and the workflow YAML. Nothing polls GitHub, so unknown means nobody wrote it down, not that it broke.

Looking for the mods and tools themselves? AsHyAmS indexes every published DreamWeave site: projects, releases with their digests, dependencies and every change. This war room is how they are built. How AsHyAmS works.

Attention required#

  • LLVM / Luau / L3i alignment: Prove the portable artifact on the intended device/runtime — Nobody has run an LLVM-built PortMaster binary on a handheld yet. Link the Actions run, the readelf output and the device test when somebody does.

Campaigns#

CampaignStateNext attention
LLVM / Luau / L3i alignmentblockedProve the portable artifact on the intended device/runtime
Make the engineering supply chain legibleactiveReview lifecycles and the projects without a public repository

Release pulse#

Applications and developer tools. A Cargo version is not a release plan; only war-room/plans.toml creates one.

ProjectNext releasePlan stateCI / docsDistribution
VFSToolnot plannedunknownunknowncrates-io, github-releases, aur
S3LightFixesnot plannedunknownunknowngithub-releases, aur
Morrobroomnot plannedunknownunknowngithub-releases, source
greenmotenot plannedunknownunknowngithub-releases, source
dream-ininot plannedunknownunknowngithub-releases, source
dream_archivetoolnot plannedunknownunknowngithub-releases, crates-io
CHIMERA managernot plannedunknownunknownsource

Release board · Plan a release

Toolchain and targets#

Reference measurement: rustc 1.98.1 (LLVM 22), clang/lld 22.1.8 and Luau 0.740, measured on Linux for L3i. A reference point, not an organization-wide pin.

PlatformTargetBaselineCompilerValidation
Linux x86_64x86_64-unknown-linux-gnuCentOS Stream 9 / EL9; glibc 2.34Stream clang/lld must match rustc LLVM majorunknown
PortMaster ARM64 (opt-in)aarch64-unknown-linux-gnuEL9 aarch64 sysroot; glibc 2.34clang/lld + cross-language thin LTOblocked
Android ARM64 (opt-in)aarch64-linux-androidNDK r27c / Android API 23NDK target clang; host LLVM setup also runsunknown
macOS ARM64aarch64-apple-darwinmacos-latest hosted runnerLLVM's official macOS ARM64 release, clang and lld matched to rustcunknown
macOS x86_64x86_64-apple-darwinmacos-26-intel hosted runnerconda-forge clang / lld matched to rustcunknown
Windows x86_64x86_64-pc-windows-msvcwindows-2025-vs2026 hosted runnerUpstream LLVM; clang-cl / lld-link for MSVCunknown

Platform matrix and intentional differences

System map#

Consumer → dependency. The full map adds which projects call StroggForge.

compact relationship diagram. Its textual ledger or workflow contract is on this page or linked below.
compact · Mermaid source · Full-size SVG
Read diagram source
flowchart LR
  subgraph domain_rust["RUST ECOSYSTEM"]
    subgraph kind_rust_foundation["foundation"]
      n_dream_path["dream_path / dream-path"]
      n_dream_archive["dream_archive"]
      n_vfstool_lib["vfstool_lib"]
      n_openmw_config["openmw-config"]
      n_dreamweave_core["dreamweave-core"]
      n_dream_net["dream-net"]
      n_soft_render["dream-soft-render"]
    end
    subgraph kind_rust_application["application"]
      n_vfstool["VFSTool"]
      n_s3lightfixes["S3LightFixes"]
      n_morrobroom["Morrobroom"]
      n_greenmote["greenmote"]
      n_dream_ini["dream-ini"]
    end
    subgraph kind_rust_developer_tool["developer tool"]
      n_archive_tool["dream_archivetool"]
      n_chimera["CHIMERA manager"]
    end
    subgraph kind_rust_runtime["runtime"]
      n_l3i["L3i / l3i"]
    end
    subgraph kind_rust_infrastructure["infrastructure"]
      n_stroggforge["StroggForge"]
    end
  end
  subgraph domain_openmw_lua["LUA(U) / OPENMW"]
    subgraph kind_openmw_lua_documentation["documentation"]
      n_cod3x["Cod3x"]
    end
    subgraph kind_openmw_lua_content["content"]
      n_stash["S3ctors-S3cret-St4sh / St4sh"]
    end
  end
  subgraph domain_web["WEB AND DOCUMENTATION SITES"]
    subgraph kind_web_infrastructure["infrastructure"]
      n_ashyams["AsHyAmS"]
    end
    subgraph kind_web_documentation["documentation"]
      n_mod_template["DreamWeave-Mod-Template"]
      n_dream_web["dreamweave-web"]
    end
  end
  n_stroggforge -.->|"documentation"| n_mod_template
  n_ashyams -.->|"documentation"| n_mod_template
  n_stash -.->|"documentation"| n_mod_template
  n_stash ==>|"contains"| n_cod3x
  n_dream_web ==>|"contains"| n_chimera
  n_archive_tool -->|"rust"| n_dream_archive
  n_chimera -->|"rust"| n_dreamweave_core
  n_dream_archive -->|"rust"| n_dream_path
  n_dream_ini -->|"rust"| n_openmw_config
  n_dream_ini -->|"rust"| n_soft_render
  n_greenmote -->|"rust"| n_openmw_config
  n_greenmote -->|"rust"| n_vfstool_lib
  n_l3i -->|"rust"| n_dream_net
  n_morrobroom -->|"rust"| n_openmw_config
  n_morrobroom -->|"rust"| n_vfstool_lib
  n_s3lightfixes -->|"rust"| n_openmw_config
  n_s3lightfixes -->|"rust"| n_vfstool_lib
  n_vfstool -->|"rust"| n_dream_archive
  n_vfstool -->|"rust"| n_openmw_config
  n_vfstool -->|"rust"| n_vfstool_lib
  n_vfstool_lib -->|"rust"| n_dream_archive
  n_vfstool_lib -->|"rust"| n_dream_path

Supply line#

From a commit to the people running it

Stages are ordered by the earliest point each can start; jobs overlap where the workflows' needs allow.

  1. source

    Source

  2. tool

    Toolchain

  3. boundary

    Verify

  4. component

    Build

  5. boundary

    Sign

  6. component

    Package

  7. service

    Publish

  8. component

    Document

  9. service

    Distribute and announce

  10. result

    Callers

    15 projects call StroggForge

How the pieces relate
  • Source Toolchain
  • Toolchain Verify
  • Verify Build
  • Build Sign
  • Sign Package
  • Package Publish
  • Publish Document
  • Document Distribute and announce
  • Distribute and announce Callers

Who calls it:

Paths outside the hosted runner matrix: Linux x86_64 (release-linux, CentOS Stream 9 / EL9; glibc 2.34); PortMaster ARM64 (opt-in) (release-portmaster, EL9 aarch64 sysroot; glibc 2.34); Android ARM64 (opt-in) (release-android, NDK r27c / Android API 23).

Supply-chain stages · Workflow contracts · Incident desk

Recent infrastructure changes#

DateChangeDetailCommits
2026-11-11The tests stop running the benchmarks, and Intel macOS moves to macos-26-intelThe test jobs ran cargo test with --all-targets, which runs every bench target as a test: a Criterion or harness = false bench does its whole measurement, and the doctests are left out. l3i's Intel macOS test step spent 22 of its 27 minutes benchmarking. The tests now run the default targets, doctests included, built and run as separate steps with a cargo --timings report; Clippy still lints the benches. Benchmarks run only through benchmarks.yml: on tags with generate_benchmarks, or by hand through benchmark_template.yaml. The test jobs build with line-table debug info, and the target caches are partitioned by runner image and Cargo build settings. Measured on l3i pull requests, test step against 2026-11-11 on v55: Intel macOS 26m58s to 5m38s, macOS ARM 10m13s to 2m56s; Windows stays near 8 minutes, its time all compiling.c12bf7e a4320f3 60cec0e ca6e4cd 8137124
2026-09-29Self-referential pins move to v54Templates and internal workflow/action calls reference v54, and the builder images are tagged v54. A consumer pinned to an older tag keeps that tag's behavior, including its toolchain and builder images.d2ac0a5
2026-09-29A program's muOS apps are recorded with its other buildsrustGlobalBuild stages the packed muOS apps as release artifacts beside the archives, so a Mod Template site that declares the muos platform records them in its manifest, with their digests, like any other build.e4d9c3a
2026-09-29Self-referential pins move to v53Templates and internal workflow/action calls reference v53, and the builder images are tagged v53. A consumer pinned to an older tag keeps that tag's behavior, including its toolchain and builder images.682991f

Full change log · Start contributing