Internal-Shaped Output Artifacts
Some public packages emit outputs that look like platform or backend contracts rather than polished end-user artifacts.
Package
Maker Experimental
A compiler-flavored V2 path layered on top of Maker state, exposing backend-oriented artifacts and shape generation.
- Imports Maker state instead of replacing it.
- Produces V2-style ontology output, shapes, and block-generation artifacts.
- Emits `BlockGeneratorResult` and block data directories that look like backend ingestion contracts.
- Feels more like an exposed backend contract than a polished end-user CLI.
- Compiler/backend rewrite path surfaced through block-oriented artifacts.
Relevant code
Most revealing source snippet
published: build/esm/cli/main.js
packages/maker-experimental/src/cli/main.ts
open source file ->consola.log("Generating BlockGeneratorResult for ontology...");
const ontologyJsonPath = path.join(blockDataDir, "ontology.json");
await fs.promises.writeFile(ontologyJsonPath, ontologyJson);
const blockGeneratorResult = {
block_identifier: "ontology",
block_data_directory: blockDataDir,
block_type: "ONTOLOGY"
};Notes
Why it matters
Maker Experimental is the strongest public sign that Palantir is rewriting or re-layering the backend/compiler side of ontology-as-code.
Its CLI writes ontology.json plus a BlockGeneratorResult with input and output shapes, which strongly suggests it is exposing a platform ingestion boundary rather than only a DX-facing workflow.
That is why this package matters more than a simple experimental label suggests: it makes backend-oriented compiler artifacts visible in public source alongside the authoring syntax.
Seams