@miadi/foundations

Programmatic and CLI access to every Miadi foundation packet — the academic grounding behind design and engineering decisions — plus the deep-research-foundations method that produces them.

The packets live in the repo at foundations/. This package bundles them at pack/publish time (scripts/bundle.mjs) so external consumers get the packets, their source ledgers, and the producing skill with zero runtime dependencies.

Install

npm i @miadi/foundations
# or, one-off browse:
npx -p @miadi/foundations miadi-foundations list

CLI

miadi-foundations list                 # packets + the fields they ground
miadi-foundations show <slug> [file]   # print a packet file (default README.md)
miadi-foundations skills               # bundled skills
miadi-foundations skill <slug>         # print a skill's SKILL.md
miadi-foundations manifest             # raw bundle manifest

API

import {
  listFoundations, getFoundation, readFoundation, readFoundationFile,
  listSkills, getSkill, loadManifest,
} from "@miadi/foundations";

listFoundations();
// [{ slug, files, fields, generated, hasLedger }, ...]

readFoundationFile("software-supply-chain-and-release-engineering", "synthesis.md");
// "# Synthesis — ..."

getSkill("deep-research-foundations"); // the SKILL.md text

What a packet is

A foundations/<topic>/ folder (skill: deep-research-foundations) with a context-layer.md, intent-understanding.md, synthesis.md, per-field files, and a source-ledger.yaml carrying sources with URLs/DOIs and a verification status. Packets answer "why this structure?" to academic, engineering, and narrative audiences at once.

Scope

Kept intentionally minimal (v0.1.2): read access + bundling. Downstream repos may layer @miadi/foundations-gaia (infra) and @miadi/foundations-orchestration-kit on top; those are out of scope here.

🌸: A small door onto the load-bearing beams — so anyone can see the fields a decision stands on, not just the decision.