When help-wanted says “apps are not ready,” cold readers sometimes hear “don’t bring real domain work.” That is the wrong hearing. Domain packs — related capabilities under one umbrella — are exactly in scope. The living example is the print-support pack: manufacturing-shaped rules as governed WASM, not a product shell PR.
+ +What the pack is
+ +Umbrella registry#596 tracks eight one-capability tickets. Announcement: Discussion #1540. Citeable Q&A: What is the print-support capability pack?.
+ +-
+
- #597
print.mesh-parse— STL/3MF bytes → mesh IR
+ - #598
print.mesh-write— mesh IR → STL/3MF bytes
+ - #599
print.overhangs-analyze— overhangs, bed reachability, fin-eligible features
+ - #600
print.orientation-score— load-aware orientation ranking
+ - #602
print.fins-generate— breakaway fin walls + tines
+ - #601
print.sway-braces-generate— tall-part sway braces + collision refuse
+ - #603
print.export-gate— allow/deny export before write
+ - #604
print.bed-pad-generate— bed pad under posed mesh
+
None of these print.* capabilities are published yet. The tickets are the door. That is honesty, not a stall story.
“Apps not ready” ≠ no domain packs
+ +The phrase blocks product UI and application-shell PRs into capability repos. It does not block codecs, scorers, generators, or export gates. Packaging is one concern per PR — not a ceiling on how rich the rule can be.
+ +Full phrasing: What does “apps are not ready” mean? Narrative companion: Where business logic lives (hosts stay thin).
+ +Hosts stay thin
+ +A browser, CLI, MCP client, or native shell can call the same capability once it exists. The host renders UI, holds session state, and supplies allowed I/O. It does not own the overhang score or the export gate forever.
+ +Today’s common execution boundary is stdin/stdout JSON through the embedder. That limits authority (no ambient filesystem). It does not limit whether the rule is manufacturing-shaped.
+ +How to contribute
+ +One capability per PR. Skill-first is welcome: plain English via traverse-capability-author → contract → WASM → human-reviewed registry PR. Under the hood that still compiles Rust to WASM; you do not need to write Rust for the usual path.
Pick a child of #596. Prefer good-first tickets when labeled. Keep mesh IR consistent across parse → analyze → generate → write. Do not open a product-shell PR.
+ +What this is not
+ +-
+
- Not a claim that any
print.*capability is published today.
+ - Not an affiliation with, or port of, any third-party print-support app. Domain inspiration (designed-in support fins as a technique class) is problem framing only. +
- Not permission to leave domain rules in the host “until apps are ready.” +
- Not a second runtime or a Python SDK. One shared
runtime.wasm; Python shells out to the CLI today.
+