@futurethesislab/kit-runtime

The kit's runtime assets — the reference-venture content tree (content/) and the artifacts render runtime (artifacts/) — packaged so a consumer can satisfy VENTURE_KIT_DIR without a kit checkout on disk.

The venture pipeline (ftlab-platform) is the consumer. It runs in a Railway container that has no kit checkout and cannot clone one, so it resolves the kit from node_modules:

VENTURE_KIT_DIR=node_modules/@futurethesislab/kit-runtime   # keep it RELATIVE

What's inside

| Path | What it is | |---|---| | content/mandavo/ | The reference venture's content tree — the shape every generated venture's content is projected against. | | artifacts/ | The .dc.html artifact templates plus the render runtime (brand-kit.js, deck-stage.js, …) that headless Chromium renders the venture PDFs from. |

Both are copies, assembled from the repo root by prepack.mjs at build and publish time. The repo root is the source of truth; the copies here are gitignored. Do not edit them — edit content/ and artifacts/ at the root.

Versioning

Versions in lockstep with registry, schemas and cli — the four describe one contract, and a consumer pins one known state of the kit across all of them. prepack.mjs refuses to publish if the versions have drifted apart, because they already did once: kit-runtime was left out of the release flow and sat at 0.3.0 while the rest went to 0.4.0, so the pipeline projected ventures from a reference tree that predated content/mandavo/apps.json.

See PUBLISHING.md at the repo root.