Skip to content

context build & context tier

The build command compiles all context files (.osi.yaml, .governance.yaml, etc.) into a single contextkit-manifest.json that MCP servers and other tools consume.

Terminal window
context build
OptionDescriptionDefault
--context-dir <path>Path to context files./context
--output-dir <path>Path to output directory./dist
--format <type>Output format: pretty, jsonpretty
Terminal window
# Build with defaults
context build
# Custom output directory
context build --output-dir dist
# JSON format for CI
context build --format json

The manifest contains all models, columns, relationships, and metadata in a single structured file:

{
"version": "1.0",
"generated_at": "2025-01-15T10:30:00Z",
"sources": {
"myapp": {
"models": [
{
"name": "users",
"schema": "public",
"description": "Registered user accounts.",
"columns": [ ... ],
"relationships": [ ... ]
}
]
}
}
}

The tier command evaluates your context files and displays an OSI tier scorecard.

Terminal window
context tier
OptionDescriptionDefault
--context-dir <path>Path to context files./context
--format <type>Output format: pretty, jsonpretty
OSI Tier Scorecard
==================
Source: myapp (23 models)
Overall Tier: Silver
Bronze (required) 23/23 ✓
Schema introspected 23/23
Primary keys defined 23/23
Column types present 23/23
Silver (required) 21/23 ✗
Descriptions 21/23 ← 2 models missing
Semantic types 19/23
Relationships 23/23
Gold (optional) 8/23
Business logic 8/23
PII classification 12/23
Usage examples 5/23
To reach Silver: add descriptions to orders_archive, tmp_imports
Run 'context enrich --target silver' for suggestions.
TierRequirements
BronzeSchema structure: table names, column names and types, primary keys
SilverBronze + descriptions, semantic types, relationship documentation
GoldSilver + business logic, data classification, usage examples, quality rules
Terminal window
# Fail CI if not at Silver tier
context tier --format json | jq -e '.overall_tier == "silver" or .overall_tier == "gold"'