domainforge 0.13.0

package/deny.toml

@@ -0,0 +1,42 @@
+[graph]
+targets = [
+  "x86_64-unknown-linux-gnu",
+  "aarch64-apple-darwin",
+  "x86_64-pc-windows-msvc",
+  "wasm32-unknown-unknown",
+]
+all-features = true
+
+[advisories]
+unmaintained = "workspace"
+unsound = "all"
+ignore = []
+
+[bans]
+multiple-versions = "warn"
+wildcards = "deny"
+
+[sources]
+unknown-registry = "deny"
+unknown-git = "deny"
+allow-registry = ["https://github.com/rust-lang/crates.io-index"]
+
+[licenses]
+confidence-threshold = 0.93
+allow = [
+  "Apache-2.0",
+  "MIT",
+  "BSD-2-Clause",
+  "BSD-3-Clause",
+  "ISC",
+  "Unicode-DFS-2016",
+  "Unicode-3.0",
+  "BSL-1.0",
+  "CC0-1.0",
+  "MPL-2.0",
+  "Apache-2.0 WITH LLVM-exception",
+]
+exceptions = [
+  # oxrocksdb-sys is dual-licensed GPL-2.0 OR Apache-2.0; we use it under Apache-2.0
+  { allow = ["GPL-2.0"], crate = "oxrocksdb-sys" },
+]

package/devbox.json

@@ -0,0 +1,14 @@
+{
+  "$schema": "https://raw.githubusercontent.com/jetpack-io/devbox/main/.schema/devbox.schema.json",
+  "packages": [
+    "rustup@1.29.0",
+    "just",
+    "bun",
+    "nodejs",
+    "python3"
+  ],
+  "env": {
+    "RUSTUP_TOOLCHAIN": "1.92.0",
+    "VENV_DIR": ".devbox/virtenv/python/.venv"
+  }
+}

package/devbox.lock

@@ -0,0 +1,76 @@
+{
+  "lockfile_version": "1",
+  "packages": {
+    "bun": {
+      "resolved": "github:NixOS/nixpkgs/cbb5cf358f50aa6acc9efd6113b7bcfbc352cd73?narHash=sha256-IX7G1dlKrOqPOImfbo7ADDfV5yU1%2Bj%2BMRChI3TL4tAA%3D#bun",
+      "source": "nixpkg"
+    },
+    "github:NixOS/nixpkgs/nixpkgs-unstable": {
+      "last_modified": "2026-06-06T12:12:42Z",
+      "resolved": "github:NixOS/nixpkgs/cbb5cf358f50aa6acc9efd6113b7bcfbc352cd73?lastModified=1780747962&narHash=sha256-IX7G1dlKrOqPOImfbo7ADDfV5yU1%2Bj%2BMRChI3TL4tAA%3D"
+    },
+    "just": {
+      "resolved": "github:NixOS/nixpkgs/cbb5cf358f50aa6acc9efd6113b7bcfbc352cd73?narHash=sha256-IX7G1dlKrOqPOImfbo7ADDfV5yU1%2Bj%2BMRChI3TL4tAA%3D#just",
+      "source": "nixpkg"
+    },
+    "nodejs": {
+      "plugin_version": "0.0.2",
+      "resolved": "github:NixOS/nixpkgs/cbb5cf358f50aa6acc9efd6113b7bcfbc352cd73?narHash=sha256-IX7G1dlKrOqPOImfbo7ADDfV5yU1%2Bj%2BMRChI3TL4tAA%3D#nodejs",
+      "source": "nixpkg"
+    },
+    "python3": {
+      "plugin_version": "0.0.4",
+      "resolved": "github:NixOS/nixpkgs/cbb5cf358f50aa6acc9efd6113b7bcfbc352cd73?narHash=sha256-IX7G1dlKrOqPOImfbo7ADDfV5yU1%2Bj%2BMRChI3TL4tAA%3D#python3",
+      "source": "nixpkg"
+    },
+    "rustup@1.29.0": {
+      "last_modified": "2026-05-21T08:15:18Z",
+      "plugin_version": "0.0.1",
+      "resolved": "github:NixOS/nixpkgs/4a29d733e8a7d5b824c3d8c958a946a9867b3eb2#rustup",
+      "source": "devbox-search",
+      "version": "1.29.0",
+      "systems": {
+        "aarch64-darwin": {
+          "outputs": [
+            {
+              "name": "out",
+              "path": "/nix/store/nl70ay30nl2szm2g03xa0d7ai69dgbln-rustup-1.29.0",
+              "default": true
+            }
+          ],
+          "store_path": "/nix/store/nl70ay30nl2szm2g03xa0d7ai69dgbln-rustup-1.29.0"
+        },
+        "aarch64-linux": {
+          "outputs": [
+            {
+              "name": "out",
+              "path": "/nix/store/684175m8xqfisacqw9rdc97fn2vpp0fj-rustup-1.29.0",
+              "default": true
+            }
+          ],
+          "store_path": "/nix/store/684175m8xqfisacqw9rdc97fn2vpp0fj-rustup-1.29.0"
+        },
+        "x86_64-darwin": {
+          "outputs": [
+            {
+              "name": "out",
+              "path": "/nix/store/4hqncs7jnqc64z49r1w09b235074li9q-rustup-1.29.0",
+              "default": true
+            }
+          ],
+          "store_path": "/nix/store/4hqncs7jnqc64z49r1w09b235074li9q-rustup-1.29.0"
+        },
+        "x86_64-linux": {
+          "outputs": [
+            {
+              "name": "out",
+              "path": "/nix/store/dpqx1vygrisrvnnwgym1226x317vqp4a-rustup-1.29.0",
+              "default": true
+            }
+          ],
+          "store_path": "/nix/store/dpqx1vygrisrvnnwgym1226x317vqp4a-rustup-1.29.0"
+        }
+      }
+    }
+  }
+}

package/docs/RELEASE_PROCESS.md

@@ -0,0 +1,360 @@
+# Release Process Documentation
+
+This document describes how to create releases for DomainForge.
+
+## Quick Start
+
+Run the full release from `main` after the release commit has been merged into `main`.
+
+```bash
+# Patch release (e.g., 0.6.2 -> 0.6.3)
+./scripts/release.sh
+
+# Minor release (e.g., 0.6.2 -> 0.7.0)
+./scripts/release.sh minor
+
+# Major release (e.g., 0.6.2 -> 1.0.0)
+./scripts/release.sh major
+
+# Preview what would happen (dry run)
+./scripts/release.sh --dry-run
+```
+
+## Release Methods
+
+### Method 1: Local Scripts (Recommended for maintainers)
+
+Use the shell scripts for full control over the release process:
+
+1. Prepare the release changes on a `release/*` branch off `main`.
+2. Merge those changes into `main`.
+3. Run `./scripts/release.sh ...` from `main`.
+
+```bash
+# Full release with all steps
+./scripts/release.sh patch
+
+# Or run individual steps
+./scripts/pre-release-check.sh
+./scripts/bump-version.sh patch
+./scripts/generate-changelog.sh 0.7.0
+./scripts/generate-release-notes.sh 0.7.0
+./scripts/create-tag.sh 0.7.0
+./scripts/build-release.sh
+./scripts/create-github-release.sh 0.7.0
+```
+
+### Method 2: GitHub Actions (Recommended for CI-driven releases)
+
+1. Go to **Actions** → **Prepare Release** → **Run workflow**
+2. Select version bump type (patch/minor/major)
+3. Review and merge the created PR
+4. Merge or fast-forward the approved release commit onto `main`
+5. Create and push tag from `main`: `git tag v<version> && git push origin main && git push --tags`
+6. Create a GitHub Release from the tag
+7. Publishing workflows trigger automatically
+
+### Pre-Release Validation Commands (Justfile)
+
+These recipes validate the build before cutting a release. They are not release-execution commands.
+
+```bash
+# Run all tests (validates before release)
+just all-tests
+
+# Per-language tests
+just rust-test
+just python-test
+just ts-test
+
+# Full CI validation
+just ai-validate
+```
+
+## Script Reference
+
+### pre-release-check.sh
+
+Validates the repository is ready for release.
+
+```bash
+./scripts/pre-release-check.sh [OPTIONS]
+
+Options:
+  --dry-run       Preview checks without running tests
+  --skip-tests    Skip test suites (faster)
+  --verbose       Verbose output
+
+Checks:
+  ✓ No uncommitted changes
+  ✓ On valid branch (main, release/*)
+  ✓ Up to date with remote
+  ✓ All tests pass
+  ✓ Version sync across files
+  ✓ CHANGELOG.md is up to date
+```
+
+### bump-version.sh
+
+Updates version across all package files.
+
+```bash
+./scripts/bump-version.sh [VERSION_TYPE] [OPTIONS]
+
+Types:
+  major           Bump major (X.0.0)
+  minor           Bump minor (x.Y.0)
+  patch           Bump patch (x.y.Z)
+  X.Y.Z           Explicit version
+  X.Y.Z-suffix    Pre-release version
+
+Options:
+  --dry-run       Preview changes
+  --no-commit     Update files without committing
+
+Files updated:
+  - domainforge-core/Cargo.toml
+  - pyproject.toml
+  - package.json
+```
+
+### generate-changelog.sh
+
+Generates changelog entries from conventional commits.
+
+```bash
+./scripts/generate-changelog.sh [VERSION] [OPTIONS]
+
+Options:
+  --dry-run       Preview without modifying
+  --no-commit     Update file without committing
+
+Categories:
+  feat:      → 🎉 Added
+  fix:       → 🐛 Fixed
+  docs:      → 📚 Documentation
+  refactor:  → ✨ Changed
+```
+
+### generate-release-notes.sh
+
+Creates GitHub release notes from CHANGELOG.md.
+
+```bash
+./scripts/generate-release-notes.sh [VERSION] [OPTIONS]
+
+Options:
+  --dry-run       Preview content
+
+Output:
+  Creates RELEASE_NOTES.md with:
+  - Version header
+  - What's Changed section
+  - Breaking Changes (if any)
+  - Contributors list
+```
+
+### create-tag.sh
+
+Creates an annotated git tag.
+
+```bash
+./scripts/create-tag.sh [VERSION] [OPTIONS]
+
+Options:
+  --dry-run       Preview without creating
+  --force         Overwrite existing tag
+
+Features:
+  - Uses RELEASE_NOTES.md for tag message
+  - Supports GPG signing if configured
+```
+
+### build-release.sh
+
+Builds release artifacts for the current platform.
+
+```bash
+./scripts/build-release.sh [OPTIONS]
+
+Options:
+  --dry-run       Preview build commands
+  --skip-cli      Skip CLI binary
+  --skip-python   Skip Python wheel
+  --skip-wasm     Skip WASM bundle
+
+Output:
+  dist/
+  ├── sea-0.7.0-linux-x86_64.tar.gz
+  ├── domainforge-0.7.0-cp312-*.whl
+  ├── domainforge-core-wasm-0.7.0.tar.gz
+  └── SHA256SUMS.txt
+```
+
+### create-github-release.sh
+
+Creates a GitHub release using the gh CLI.
+
+```bash
+./scripts/create-github-release.sh [VERSION] [OPTIONS]
+
+Options:
+  --dry-run       Preview without creating
+  --draft         Create as draft
+
+Requirements:
+  - GitHub CLI (gh) installed and authenticated
+  - Tag must exist
+```
+
+### release.sh
+
+Master orchestration script that runs all steps.
+
+```bash
+./scripts/release.sh [VERSION_TYPE] [OPTIONS]
+
+Options:
+  --dry-run       Full dry run of all steps
+  --skip-tests    Skip test suites
+  --skip-build    Skip building artifacts
+  --yes, -y       Auto-confirm push
+
+Steps:
+  1. Pre-release checks
+  2. Version bump
+  3. Changelog generation
+  4. Release notes generation
+  5. Commit changes
+  6. Create git tag
+  7. Build artifacts
+  8. Push to remote
+  9. Create GitHub release
+```
+
+## Prerequisites
+
+### Required Tools
+
+| Tool      | Purpose         | Installation                             |
+| --------- | --------------- | ---------------------------------------- |
+| git       | Version control | System package manager                   |
+| cargo     | Rust toolchain  | [rustup.rs](https://rustup.rs)           |
+| just      | Task runner     | `cargo install just`                     |
+| maturin   | Python wheels   | `pip install maturin`                    |
+| wasm-pack | WASM bundle     | `cargo install wasm-pack`                |
+| gh        | GitHub CLI      | [cli.github.com](https://cli.github.com) |
+
+### GitHub Authentication
+
+```bash
+# Authenticate with GitHub CLI
+gh auth login
+
+# Verify authentication
+gh auth status
+```
+
+## Troubleshooting
+
+### "Uncommitted changes detected"
+
+```bash
+# Check what's modified
+git status
+
+# Stage and commit or stash
+git add -A && git commit -m "wip"
+# OR
+git stash
+```
+
+### "Version mismatch across files"
+
+```bash
+# Check versions
+grep '^version' domainforge-core/Cargo.toml pyproject.toml
+grep '"version"' package.json
+
+# Sync manually or run bump-version
+./scripts/bump-version.sh 0.7.0
+```
+
+### "Tag already exists"
+
+```bash
+# Delete local tag
+git tag -d v0.7.0
+
+# Delete remote tag
+git push origin --delete v0.7.0
+
+# Or use --force
+./scripts/create-tag.sh --force
+```
+
+### "GitHub CLI not authenticated"
+
+```bash
+gh auth login
+# Follow prompts to authenticate
+```
+
+## Rollback Procedures
+
+### Before Push
+
+If release failed before pushing:
+
+```bash
+# Reset to previous commit
+git reset --hard HEAD~1
+
+# Delete local tag
+git tag -d v0.7.0
+```
+
+### After Push (Breaking Release)
+
+```bash
+# Delete remote tag (stops CI publishing)
+git push origin --delete v0.7.0
+
+# Delete GitHub release via web UI or CLI
+gh release delete v0.7.0
+
+# Revert commit
+git revert HEAD
+git push origin main
+```
+
+### Emergency Hotfix
+
+```bash
+# Create hotfix branch from main
+git checkout main
+git pull
+git checkout -b hotfix/0.7.1
+
+# Apply fix, commit, then release
+./scripts/release.sh patch
+```
+
+## Version Numbering
+
+DomainForge follows [Semantic Versioning](https://semver.org/):
+
+- **Major (X.0.0)**: Breaking API changes
+- **Minor (x.Y.0)**: New features, backward compatible
+- **Patch (x.y.Z)**: Bug fixes, backward compatible
+- **Pre-release (x.y.z-alpha)**: Development versions
+
+## Files Updated During Release
+
+| File                  | Field                | Example                   |
+| --------------------- | -------------------- | ------------------------- |
+| `domainforge-core/Cargo.toml` | `version = "X.Y.Z"`  | `version = "0.7.0"`       |
+| `pyproject.toml`      | `version = "X.Y.Z"`  | `version = "0.7.0"`       |
+| `package.json`        | `"version": "X.Y.Z"` | `"version": "0.7.0"`      |
+| `CHANGELOG.md`        | New version section  | `## [0.7.0] - 2025-12-23` |
+| `RELEASE_NOTES.md`    | Generated content    | GitHub release body       |

package/docs/diagnostics.md

@@ -0,0 +1,161 @@
+# Semantic Diagnostic Codes
+
+DomainForge emits structured diagnostics when validating .sea source files against semantic packs. Each diagnostic carries a code, a three-valued semantic truth, a severity, and contextual information. This reference documents all 30 diagnostic codes, their truth values, and how they behave in different validation modes.
+
+## Three-Valued Semantic Truth
+
+Every diagnostic has a `semantic_truth` field that captures the resolution outcome independently of severity:
+
+| Truth      | Meaning                                                          |
+|------------|------------------------------------------------------------------|
+| `valid`    | The concept resolved successfully. No semantic issue.            |
+| `invalid`  | The concept is definitively wrong (rejected, blocked).           |
+| `unknown`  | Insufficient information to confirm or deny (missing, ambiguous, proposed). |
+
+`semantic_truth` is **independent** of `DiagnosticSeverity`. An `unknown` truth can map to `Error` severity in strict mode, but the truth value stays `unknown`---not `invalid`. This distinction matters for tooling that uses the truth value for control flow (e.g., the LSP uses `unknown` to offer "add to pack" suggestions, while `invalid` triggers error highlighting).
+
+## Complete Diagnostic Code Table
+
+### Concept Resolution
+
+| Code                    | Semantic Truth | LSP Warn Severity | CI Strict Severity | Description                                    |
+|-------------------------|----------------|-------------------|--------------------|------------------------------------------------|
+| `unknown_concept`       | unknown        | Warning           | Error              | Term does not match any concept, alias, or mapping rule. |
+| `deprecated_concept`    | valid          | Warning           | Varies (policy)    | Concept resolved but has `deprecated` status.  |
+| `ambiguous_concept`     | unknown        | Warning           | Error              | Term matches multiple active concepts.          |
+| `ambiguous_alias`       | unknown        | Warning           | Error              | Alias matches only `ambiguous`-status entries across multiple targets. |
+| `alias_conflict`        | invalid        | Error             | Error              | Alias is `blocked` or has conflicting approved/deprecated entries targeting different concepts. |
+| `rejected_concept`      | invalid        | Error             | Error              | Concept resolved but has `rejected` status.    |
+| `proposed_concept`      | unknown        | Warning           | Error              | Concept resolved but has `proposed` status.    |
+
+### Alias Resolution
+
+| Code                    | Semantic Truth | LSP Warn Severity | CI Strict Severity | Description                                    |
+|-------------------------|----------------|-------------------|--------------------|------------------------------------------------|
+| `ambiguous_alias_group` | unknown        | Warning           | Error              | Multiple aliases for the same key are all in `ambiguous` status. |
+
+### Pack Integrity
+
+| Code                        | Semantic Truth | LSP Warn Severity | CI Strict Severity | Description                                    |
+|-----------------------------|----------------|-------------------|--------------------|------------------------------------------------|
+| `pack_unavailable`          | unknown        | Error             | Error              | No pack could be loaded for validation.         |
+| `pack_schema_mismatch`      | invalid        | Error             | Error              | Pack `schema_version` is not `0.3`.             |
+| `pack_version_mismatch`     | invalid        | Warning           | Error              | Pack version is incompatible with tooling.      |
+| `pack_hash_mismatch`        | invalid        | Error             | Error              | Pack content hash does not match expected hash.  |
+| `pack_unsigned`             | invalid        | Warning           | Error              | Pack is unsigned but signature is required.      |
+| `pack_signature_invalid`    | invalid        | Error             | Error              | Pack signature verification failed.              |
+| `pack_set_conflict`         | invalid        | Error             | Error              | Multiple packs have conflicting definitions.     |
+
+### Relation and Metric Validation
+
+| Code                    | Semantic Truth | LSP Warn Severity | CI Strict Severity | Description                                    |
+|-------------------------|----------------|-------------------|--------------------|------------------------------------------------|
+| `invalid_relation`      | invalid        | Error             | Error              | Relation references a concept that does not exist in the pack. |
+| `invalid_predicate`     | invalid        | Error             | Error              | Predicate is not in the concept's `allowed_predicates` list. |
+| `unknown_metric`        | unknown        | Warning           | Error              | Metric ID is not defined in the pack.           |
+| `unknown_dimension`     | unknown        | Warning           | Error              | Dimension ID referenced by a metric is not defined. |
+| `unknown_unit`          | unknown        | Warning           | Error              | Unit ID referenced by a metric is not defined.  |
+| `unit_mismatch`         | invalid        | Error             | Error              | Unit is incompatible with the dimension.        |
+| `dimension_mismatch`    | invalid        | Error             | Error              | Dimension does not match the expected dimension. |
+
+### Governance
+
+| Code                                | Semantic Truth | LSP Warn Severity | CI Strict Severity | Description                                    |
+|-------------------------------------|----------------|-------------------|--------------------|------------------------------------------------|
+| `missing_definition`                | unknown        | Warning           | Warning            | Active concept has no definition text.          |
+| `missing_owner`                     | unknown        | Warning           | Warning            | Active concept has no owner assigned.           |
+| `duplicate_canonical_name`          | invalid        | Error             | Error              | Two concepts share the same canonical name.     |
+| `duplicate_concept_id`              | invalid        | Error             | Error              | Two concepts share the same ID.                 |
+| `unreviewed_concept`                | unknown        | Error             | Error              | Active concept lacks a passing review record or has a definition hash mismatch. |
+| `meaning_version_not_bumped`        | invalid        | Error             | Error              | `meaning_fingerprint` changed but `meaning_version` was not increased. |
+| `meaning_version_baseline_missing`  | unknown        | Error             | Error              | Approved build has no previous pack for version comparison. |
+| `mapping_required`                  | unknown        | Warning           | Error              | Term must be mapped to an approved concept.     |
+
+## DeprecatedPolicy Behavior
+
+The `deprecated_concept` diagnostic severity is controlled by the `DeprecatedPolicy` setting:
+
+| Policy            | Warn Mode Severity | Strict Mode Severity | Description                                 |
+|-------------------|--------------------|----------------------|---------------------------------------------|
+| `Allow`           | Hint               | Hint                 | Deprecated concepts are silently accepted.  |
+| `Warn`            | Warning            | Warning              | Deprecated concepts produce warnings in all modes. |
+| `ErrorInStrict`   | Warning            | Error                | Warnings in warn mode, errors in strict mode. |
+| `ErrorAlways`     | Error              | Error                | Deprecated concepts always produce errors.  |
+
+This policy is orthogonal to the `semantic_truth` value---a deprecated concept always has truth `valid` because it resolved successfully. The severity controls whether the resolution result is treated as actionable.
+
+## How semantic_truth Is Independent of DiagnosticSeverity
+
+The separation between truth and severity serves distinct consumers:
+
+- **LSP**: Uses `semantic_truth` to decide what quick-fix actions to offer. `unknown` suggests "add to pack." `invalid` suggests "remove or fix reference." `valid` with `deprecated` suggests "update to replacement."
+- **CI**: Uses `severity` to decide pass/fail. A `Warning` in strict mode is still a failure if the policy maps it to `Error`.
+- **Code generators**: Use `semantic_truth` to decide whether to include a concept in generated output. `invalid` concepts are excluded. `unknown` concepts may be included with a TODO comment.
+
+Example: A term that resolves to a `proposed` concept has truth `unknown` and severity `Warning` in warn mode. In strict mode, the severity becomes `Error`, but the truth stays `unknown`. The CI fails (severity = Error), but the code generator can still include the concept with a caveat (truth = unknown).
+
+## LSP Diagnostic Data Payload
+
+The DomainForge LSP attaches structured data to each diagnostic via the LSP `data` field:
+
+```json
+{
+  "domainforge.semantic_code": "unknown_concept",
+  "domainforge.semantic_truth": "unknown",
+  "domainforge.pack_id": "acme/logistics/1.1.0",
+  "domainforge.pack_content_hash": "sha256:abc123...",
+  "domainforge.recoverability_hint": "Add the concept to the semantic pack",
+  "domainforge.suggestions": [
+    { "label": "supplier", "rank": 10 },
+    { "label": "warehouse", "rank": 5 }
+  ]
+}
+```
+
+### Payload Fields
+
+| Field                              | Type     | Description                                              |
+|------------------------------------|----------|----------------------------------------------------------|
+| `domainforge.semantic_code`        | string   | The `SemanticDiagnosticCode` value.                      |
+| `domainforge.semantic_truth`       | string   | The three-valued truth (`valid`, `invalid`, `unknown`).  |
+| `domainforge.pack_id`              | string   | The pack that produced this diagnostic.                  |
+| `domainforge.pack_content_hash`    | string   | Content hash of the pack at validation time.             |
+| `domainforge.recoverability_hint`  | string   | Human-readable suggestion for fixing the issue.          |
+| `domainforge.suggestions`          | array    | Ranked list of concept suggestions (for `unknown` results). |
+
+## Validation Modes
+
+| Mode      | Behavior                                                                 |
+|-----------|--------------------------------------------------------------------------|
+| `off`     | No semantic validation is performed. Pack is not loaded.                 |
+| `warn`    | Diagnostics are reported as warnings. Unknown concepts produce warnings. |
+| `strict`  | Unknown concepts are errors. Deprecated concepts may be errors (per policy). Unsigned packs are errors if `require_signed_pack` is true. |
+
+## Validation Options
+
+The `ValidationOptions` structure controls validation behavior:
+
+```json
+{
+  "mode": "strict",
+  "unknown_concept_policy": "error",
+  "deprecated_policy": "error_in_strict",
+  "require_signed_pack": true,
+  "allow_unsigned_test_fixtures": false
+}
+```
+
+| Field                          | Type     | Default   | Description                                          |
+|--------------------------------|----------|-----------|------------------------------------------------------|
+| `mode`                         | string   | `warn`    | Validation mode (`off`, `warn`, `strict`).           |
+| `unknown_concept_policy`       | string   | `warning` | How to handle unknown concepts (`ignore`, `warning`, `error`). |
+| `deprecated_policy`            | string   | `warn`    | How to handle deprecated concepts. See table above.  |
+| `require_signed_pack`          | boolean  | `false`   | Whether to require a signed pack.                    |
+| `allow_unsigned_test_fixtures` | boolean  | `false`   | Bypass signature requirement for test fixture packs. |
+
+## See Also
+
+- [Semantic Packs](semantic-packs.md) for the overall pack system.
+- [Semantic Pack Review Process](semantic-pack-review.md) for governance codes.
+- [Semantic Pack Signing and Verification](semantic-pack-signing.md) for signature-related codes.
+- [Three-Valued Logic](explanations/three-valued-logic.md) for the theoretical background.