Topological sort of every upstream node plus the target. Answers 'in what order should I build the inputs to produce this artifact?'.

Useful for engagement planning: given a target deliverable (e.g., category-strategy), return the dependency chain so the team builds prerequisites before dependents.

Group nodes by the missing input that blocks them, ranked by impact.

Each entry names the missing data source (e.g., 'Contract metadata') and lists the nodes it directly blocks plus the transitive downstream impact. Used to prioritize data acquisition: investing in the input at the top of the list unlocks the largest share of the graph.

Nodes whose declared inputs are all HAVE for a PO-line + entity-profile data set. Answers 'what analyses can I run today without acquiring new data?'.

The differentiated filter behind this whole spec. Most procurement libraries can list the analyses; this one tells you which ones are runnable against your data.

Full spec for a single analysis: source firms, inputs and their feasibility, method, primary outputs, decision enabled, watch-outs, and graph dependencies.

Fetch a filled-in example for a given parent node slug.

Returns the example artifact (as it would land on a stakeholder's desk), populated with concrete numbers, supplier names, and findings from the shared engagement. Useful as a few-shot reference for what a strong version of the artifact looks like in practice.

Full spec for a single deliverable: purpose, audience, inputs, components, output format, quality markers, and graph dependencies.

Direct upstream nodes for a given node. Answers 'what does this need?'.

Returns the immediate predecessors only. For full upstream closure, use build_order(slug), which returns every transitive ancestor in dependency order.

Direct downstream nodes for a given node. Answers 'what uses this?'.

Returns the immediate successors only. For full downstream impact, use what_breaks_if(slug), which returns every transitively-affected node.

The shared fictional engagement narrative that anchors every example. Read this first to see how examples thread together coherently.

Full spec for a single phase: purpose, included activities, source firms, and the layer focus of work performed in this phase.

List analyses from the procurement analytics catalog (Layer 2 nodes).

Filter by primary_phase (0-6), layer (1-5), or feasibility with PO-line data ('HIGH', 'MEDIUM', 'LOW'). Feasibility is the most useful filter: it tells you which analyses can be run today with PO-line + entity-profile data alone.

List filled-in artifact examples anchored to the shared engagement context.

Each example's slug matches a parent node slug, so a category-strategy example is at content/examples/category-strategy.md and threads with the spend-cube, rfx-package, and other examples through the TechnoFlex PSA resin narrative.

Use get_engagement_context() for the shared engagement first, then get_artifact_example(slug) to fetch a specific filled-in artifact.

List deliverables from the phase-by-phase taxonomy (Layer 3-5 nodes).

Deliverables are the formatted artifacts handed to stakeholders: strategy docs, RFx packages, contracts, scorecards. Each names which upstream analyses and deliverables it depends on.

List horizontal artifacts that span multiple phases: governance model, RAID log, benefits tracker, knowledge repository.

List the seven phases of the strategic sourcing process (Phase 0 through 6).

Phases are a navigational frame, not the structural spine. The spine is the dependency graph of nodes (analyses, deliverables, horizontal artifacts).

Transitive closure of downstream nodes. Every node that would become stale if this one changed materially (new data, redefined taxonomy, restated baseline).

Useful for impact analysis: 'if I restate the spend cube, what reviews do I need to redo?'