cfgit 0.1.0__tar.gz → 0.1.1__tar.gz

{cfgit-0.1.0 → cfgit-0.1.1}/CREDITS.md

@@ -33,5 +33,5 @@ cfgit's framing (`SPEC_CORE.md` §3) is defined by contrast with the "git for da
 **Apache-2.0** (see `LICENSE`). Permissive + explicit patent grant, so the company
 and others can adopt freely. Apache-2.0 can depend on MIT/Apache libraries; it
 **cannot** link GPL-2.0 source into the core: a second reason the Git borrowing
-stays concept-only. The optional `cfg-impact` plugin keeps any model-provider SDK
+stays concept-only. The optional `cfgit-impact` plugin keeps any model-provider SDK
 out of the core package, so a differently-licensed SDK can't taint the core license.

{cfgit-0.1.0 → cfgit-0.1.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cfgit
-Version: 0.1.0
+Version: 0.1.1
 Summary: Git-style history, diff, drift detection, and rollback for live database records without migrating or owning your datastore
 Project-URL: Homepage, https://github.com/AusafMo/cfgit
 Project-URL: Repository, https://github.com/AusafMo/cfgit
@@ -243,13 +243,13 @@ same database. Your scripts and admin tools can still write it. cfgit sits besid
 the store, records what changed, and refuses to clobber changes it did not record.
 
 <p align="center">
-  <img src="docs/screenshots/01-diff.png" alt="Side-by-side line diff of a live agent config, with a sticky field header and collapsed context" width="32%" />
-  <img src="docs/screenshots/02-impact.png" alt="System-impact panel: deterministic facts plus opt-in LLM narration of what the change does downstream" width="32%" />
-  <img src="docs/screenshots/03-scoped-impact.png" alt="Scoped impact: select records on the left and reason the change against only those" width="32%" />
+  <img src="docs/screenshots/01-diff.png" alt="Production-shaped support agent drift with collection stats, branch workflow controls, history, and line-aligned diff" width="32%" />
+  <img src="docs/screenshots/02-impact.png" alt="High-risk system-impact panel for a refund-resolution agent change with provider-backed LLM narration" width="32%" />
+  <img src="docs/screenshots/03-scoped-impact.png" alt="Scoped impact analysis with selected policy, eval, and rollout records plus provider-backed narration" width="32%" />
 </p>
 
 <p align="center">
-  <sub>Line-aligned diff of a live record &nbsp;·&nbsp; system-impact panel &nbsp;·&nbsp; impact scoped to the records you select &nbsp;(demo data)</sub>
+  <sub>Production-shaped drift review &nbsp;·&nbsp; narrated whole-system impact &nbsp;·&nbsp; narrated impact scoped to selected policy, eval, and rollout records</sub>
 </p>
 
 ## Why cfgit exists
@@ -570,11 +570,14 @@ Refs:
 
 `cfg ui` starts a localhost-only web UI over the same action layer as the CLI and
 MCP server. It reads like a git client: a collection-and-record tree on the left,
-a commit-graph history rail, and a line-aligned side-by-side diff that collapses
-unchanged context (expandable in place) and keeps the field name pinned while you
-scroll. It can run status, diff, impact, commit, branch draft commits, PR open
-and merge, log, show, adopt, restore, tag, init, import, and fsck, and ships
-dark and light themes.
+a recent-activity rail before you select anything, per-record commit graphs, and
+a line-aligned side-by-side diff that collapses unchanged context (expandable in
+place) and keeps the field name pinned while you scroll. The recent activity view
+surfaces live drift and the latest cfgit commits across all configured records,
+so you can see what changed recently without opening records one by one. It can
+run status, diff, impact, commit, branch draft commits, PR open and merge, log,
+show, adopt, restore, tag, init, import, and fsck, and ships dark and light
+themes.
 
 By default it binds to `127.0.0.1:8765` and tries the next free ports if needed:
 
@@ -587,6 +590,39 @@ If you omit `--port`, cfgit will try the next free local ports. If you pass
 `--port` explicitly, cfgit treats that port as intentional and fails if it is
 already in use.
 
+## Production-shaped UI demo
+
+The repo includes a safe support-control-plane fixture for screenshots, demos,
+and UI testing. It creates synthetic records only in the database you pass; use a
+throwaway database name when you want the run contained.
+
+```bash
+python examples/seed_support_demo.py \
+  --uri 'mongodb://localhost:27017/?replicaSet=rs0' \
+  --db cfgit_ui_demo \
+  --reset
+
+cfg --config-file examples/cfgit-support-demo.toml --env dev init
+cfg --config-file examples/cfgit-support-demo.toml --env dev import --all -m "initial production-shaped demo import"
+
+python examples/seed_support_demo.py \
+  --uri 'mongodb://localhost:27017/?replicaSet=rs0' \
+  --db cfgit_ui_demo \
+  --drift
+
+cfg --config-file examples/cfgit-support-demo.toml --env dev status
+cfg --config-file examples/cfgit-support-demo.toml --env dev ui
+```
+
+The base seed creates a realistic support-agent runtime surface: orchestrator
+and specialist agent configs, model routing, policy rules, tool registry records,
+routing policies, escalation policies, eval suites, rollout controls, and
+knowledge-source allowlists. The `--drift` pass simulates admin-console edits to
+refund automation, refund policy, routing confidence, eval gates, rollout
+traffic, and a new loyalty-credit tool. That gives the UI useful drift, impact,
+scoped impact, adopt, branch, PR, merge, and restore-history paths without using
+proprietary data.
+
 ## MCP and agent usage
 
 The MCP server exposes the same operations with a uniform envelope:
@@ -618,6 +654,7 @@ Tools include:
 - `cfg_pr_show`
 - `cfg_pr_close`
 - `cfg_pr_merge`
+- `cfg_recent_history`
 - `cfg_log`
 - `cfg_show`
 - `cfg_adopt`

{cfgit-0.1.0 → cfgit-0.1.1}/README.md

@@ -10,13 +10,13 @@ same database. Your scripts and admin tools can still write it. cfgit sits besid
 the store, records what changed, and refuses to clobber changes it did not record.
 
 <p align="center">
-  <img src="docs/screenshots/01-diff.png" alt="Side-by-side line diff of a live agent config, with a sticky field header and collapsed context" width="32%" />
-  <img src="docs/screenshots/02-impact.png" alt="System-impact panel: deterministic facts plus opt-in LLM narration of what the change does downstream" width="32%" />
-  <img src="docs/screenshots/03-scoped-impact.png" alt="Scoped impact: select records on the left and reason the change against only those" width="32%" />
+  <img src="docs/screenshots/01-diff.png" alt="Production-shaped support agent drift with collection stats, branch workflow controls, history, and line-aligned diff" width="32%" />
+  <img src="docs/screenshots/02-impact.png" alt="High-risk system-impact panel for a refund-resolution agent change with provider-backed LLM narration" width="32%" />
+  <img src="docs/screenshots/03-scoped-impact.png" alt="Scoped impact analysis with selected policy, eval, and rollout records plus provider-backed narration" width="32%" />
 </p>
 
 <p align="center">
-  <sub>Line-aligned diff of a live record &nbsp;·&nbsp; system-impact panel &nbsp;·&nbsp; impact scoped to the records you select &nbsp;(demo data)</sub>
+  <sub>Production-shaped drift review &nbsp;·&nbsp; narrated whole-system impact &nbsp;·&nbsp; narrated impact scoped to selected policy, eval, and rollout records</sub>
 </p>
 
 ## Why cfgit exists
@@ -337,11 +337,14 @@ Refs:
 
 `cfg ui` starts a localhost-only web UI over the same action layer as the CLI and
 MCP server. It reads like a git client: a collection-and-record tree on the left,
-a commit-graph history rail, and a line-aligned side-by-side diff that collapses
-unchanged context (expandable in place) and keeps the field name pinned while you
-scroll. It can run status, diff, impact, commit, branch draft commits, PR open
-and merge, log, show, adopt, restore, tag, init, import, and fsck, and ships
-dark and light themes.
+a recent-activity rail before you select anything, per-record commit graphs, and
+a line-aligned side-by-side diff that collapses unchanged context (expandable in
+place) and keeps the field name pinned while you scroll. The recent activity view
+surfaces live drift and the latest cfgit commits across all configured records,
+so you can see what changed recently without opening records one by one. It can
+run status, diff, impact, commit, branch draft commits, PR open and merge, log,
+show, adopt, restore, tag, init, import, and fsck, and ships dark and light
+themes.
 
 By default it binds to `127.0.0.1:8765` and tries the next free ports if needed:
 
@@ -354,6 +357,39 @@ If you omit `--port`, cfgit will try the next free local ports. If you pass
 `--port` explicitly, cfgit treats that port as intentional and fails if it is
 already in use.
 
+## Production-shaped UI demo
+
+The repo includes a safe support-control-plane fixture for screenshots, demos,
+and UI testing. It creates synthetic records only in the database you pass; use a
+throwaway database name when you want the run contained.
+
+```bash
+python examples/seed_support_demo.py \
+  --uri 'mongodb://localhost:27017/?replicaSet=rs0' \
+  --db cfgit_ui_demo \
+  --reset
+
+cfg --config-file examples/cfgit-support-demo.toml --env dev init
+cfg --config-file examples/cfgit-support-demo.toml --env dev import --all -m "initial production-shaped demo import"
+
+python examples/seed_support_demo.py \
+  --uri 'mongodb://localhost:27017/?replicaSet=rs0' \
+  --db cfgit_ui_demo \
+  --drift
+
+cfg --config-file examples/cfgit-support-demo.toml --env dev status
+cfg --config-file examples/cfgit-support-demo.toml --env dev ui
+```
+
+The base seed creates a realistic support-agent runtime surface: orchestrator
+and specialist agent configs, model routing, policy rules, tool registry records,
+routing policies, escalation policies, eval suites, rollout controls, and
+knowledge-source allowlists. The `--drift` pass simulates admin-console edits to
+refund automation, refund policy, routing confidence, eval gates, rollout
+traffic, and a new loyalty-credit tool. That gives the UI useful drift, impact,
+scoped impact, adopt, branch, PR, merge, and restore-history paths without using
+proprietary data.
+
 ## MCP and agent usage
 
 The MCP server exposes the same operations with a uniform envelope:
@@ -385,6 +421,7 @@ Tools include:
 - `cfg_pr_show`
 - `cfg_pr_close`
 - `cfg_pr_merge`
+- `cfg_recent_history`
 - `cfg_log`
 - `cfg_show`
 - `cfg_adopt`

{cfgit-0.1.0 → cfgit-0.1.1}/docs/PUBLISHING.md

@@ -1,13 +1,13 @@
 # Publishing
 
-cfgit publishes two Python packages:
+cfgit publishes two Python distributions:
 
 - `cfgit`: Git-style history, diff, drift detection, branch/PR review, and
   rollback for live database records without migrating or owning the datastore.
 - `cfgit-impact`: optional plugin for deterministic system-impact summaries and
   opt-in LLM narration of database record diffs.
 
-Current first release version: `0.1.0`.
+Current release version: `0.1.1`.
 
 ## One-Time PyPI Setup
 
@@ -49,8 +49,8 @@ python -m twine check dist/*
 ```bash
 python -m venv /tmp/cfgit-publish-smoke
 /tmp/cfgit-publish-smoke/bin/python -m pip install \
-  'dist/cfgit-0.1.0-py3-none-any.whl[mcp]' \
-  plugins/cfg_impact/dist/cfgit_impact-0.1.0-py3-none-any.whl
+  'dist/cfgit-0.1.1-py3-none-any.whl[mcp]' \
+  plugins/cfg_impact/dist/cfgit_impact-0.1.1-py3-none-any.whl
 /tmp/cfgit-publish-smoke/bin/cfg --help
 /tmp/cfgit-publish-smoke/bin/python -c 'import cfg; import cfg.mcp.server; import cfg_impact; print("imports ok")'
 ```
@@ -63,9 +63,9 @@ release from a tag:
 ```bash
 git checkout main
 git pull origin main
-git tag v0.1.0
-git push origin v0.1.0
-gh release create v0.1.0 --title "v0.1.0" --notes "First public cfgit release."
+git tag v0.1.1
+git push origin v0.1.1
+gh release create v0.1.1 --title "v0.1.1" --notes "cfgit 0.1.1 package release."
 ```
 
 The release triggers `.github/workflows/publish.yml`, which publishes `cfgit`

{cfgit-0.1.0 → cfgit-0.1.1}/docs/SPEC.md

@@ -561,7 +561,7 @@ commit.pre_hook = "impact"         # on commit: print the report; WARN only (nev
 - The **graph extraction in §7.2 and the deterministic severity in §7.3C run locally with NO LLM**: only the natural-language *nature* classification (A) and the *why* narration (B/C) call a model. So even with the LLM fully disabled, `cfg impact` still reports blast radius, downstream consumers, cross-config conflicts, and orphan references (structural facts): you lose only the prose, not the consequence detection. **[V3.1-6] Severity (§7.3C) is keyed SOLELY off the LOCAL structural detection** (e.g. a `phase_contract` edge-field diff with ≥1 declared consumer ⇒ `breaking`); the LLM's nature label (A) is descriptive prose and is NEVER an input to severity: so severity is deterministic and reproducible even if the model is off or its prose varies. The LLM is the explainer, not the detector.
 
 ### 7.6 Implementation
-- Shipped as a `cfg-impact` plugin; **core has zero LLM dependency** (§1 boundary holds). The plugin provides the model client + the edge-extractors; the manifest (`[impact]`) wires field→edge semantics per project.
+- Shipped as a `cfgit-impact` plugin; **core has zero LLM dependency** (§1 boundary holds). The plugin provides the model client + the edge-extractors; the manifest (`[impact]`) wires field→edge semantics per project.
 - Provider-agnostic (Claude/OpenAI/local); default Claude. No model SDK in core.
 
 ---
@@ -805,7 +805,7 @@ Shipped as `CREDITS.md` + `NOTICE` + `LICENSE` in the repo; summarized here so t
 - **Semantic/behavioral-diff prior art** for §7: *llm-prompt-semantic-diff* (embedding-% CLI), *llm-behavior-diff* (model-execution + severity + MCP server), and the *"Prompting in the Wild"* method (arXiv:2412.17298, CoT read-old+new→find-changes→flag-inconsistency, which §7 adopts for the intra-config `self_inconsistency` dimension). **Obligation: cite the methods/papers; check each repo's LICENSE before reusing any code** (most are permissive MIT/Apache, but verify per-repo at vendor time; until then we reuse only *ideas*, which needs citation, not license grant).  → credit + per-repo license note in `CREDITS.md`.
 - **Standard building blocks** (sha256/canonical-JSON hashing à la git blob; bitemporal modeling from the data-warehousing literature; optimistic-concurrency/CAS) are **public concepts / common knowledge**: credited as influences, no license obligation.
 
-**`cfg`'s own license:** target **Apache-2.0** (permissive + explicit patent grant; lets the company and others adopt freely). Apache-2.0 is compatible with depending on MIT/Apache libraries; it is NOT compatible with *linking* GPL-2.0 code into the core: which is the second reason the Git borrowing stays concept-only. The optional `cfg-impact` plugin keeps any provider SDK out of core, so a differently-licensed model SDK can't taint the core license.
+**`cfg`'s own license:** target **Apache-2.0** (permissive + explicit patent grant; lets the company and others adopt freely). Apache-2.0 is compatible with depending on MIT/Apache libraries; it is NOT compatible with *linking* GPL-2.0 code into the core: which is the second reason the Git borrowing stays concept-only. The optional `cfgit-impact` plugin keeps any provider SDK out of core, so a differently-licensed model SDK can't taint the core license.
 
 **Process rule (so future borrowing stays honest):** whenever code or a non-obvious design is taken from an external project, add a `CREDITS.md` row (project, what was taken, its license, idea-vs-code) in the SAME change: actually open and read that project's LICENSE before reuse, and isolate anything copyleft. This is itself a `cfg` repo convention, enforced in review.
 

{cfgit-0.1.0 → cfgit-0.1.1}/docs/SPEC_CORE.md

@@ -142,7 +142,7 @@ Commands and surfaces (CLI + `--json`, localhost UI, MCP), each across **all con
 - `cfg tag <name>`: bookmark the current state of everything to return to by name.
 - `cfg adopt <record>` / `cfg adopt --all`: fold an out-of-band change into history with attribution (the reconciliation core). Cron-friendly.
 - `cfg fsck`: integrity + drift sweep.
-- `cfg impact <record> [a] [b]`: deterministic system-impact overview, with optional LLM narration from the `cfg-impact` plugin.
+- `cfg impact <record> [a] [b]`: deterministic system-impact overview, with optional LLM narration from the `cfgit-impact` plugin.
 - `cfg identity-hash`: hash a private human token for authenticated identity config without storing the raw token.
 - `cfg ui`: local web UI for the same operations.
 - `cfg-mcp`: MCP server exposing the same operation envelope to agents.
@@ -207,4 +207,4 @@ admin_actions = ["init", "restore_system"]
 
 **v1 implementation correction:** `oid` is a content hash, not a unique entry id. A restore can intentionally create a new history entry whose document content equals an older version, so `(env, collection, record_id, oid)` must be a non-unique lookup index. The unique history key is `(env, collection, record_id, seq)`. HEAD stores both `head_oid` for dirty checks and `head_seq` for exact entry resolution. Any older SPEC.md wording that says `(config_id, oid)` is unique is superseded for v1.
 
-**Build order for v1:** core engine + history schema + hashing + drift detect + mutation permissions → MongoAdapter → `init`/`status`/`diff`/`commit`/`log`/`adopt` → `restore` (single + system) + `tag` + `fsck` → PostgresAdapter (proves the seam) → localhost UI + MCP/skill over the same action layer → `cfg-impact` plugin boundary → point at the two origin collections and run the one-week usage test. Hosted product surfaces wait for signal.
+**Build order for v1:** core engine + history schema + hashing + drift detect + mutation permissions → MongoAdapter → `init`/`status`/`diff`/`commit`/`log`/`adopt` → `restore` (single + system) + `tag` + `fsck` → PostgresAdapter (proves the seam) → localhost UI + MCP/skill over the same action layer → `cfgit-impact` plugin boundary → point at the two origin collections and run the one-week usage test. Hosted product surfaces wait for signal.

{cfgit-0.1.0 → cfgit-0.1.1}/docs/USAGE.md

@@ -269,7 +269,10 @@ cfg ui
 ```
 
 The UI binds to `127.0.0.1`. It is a local operator surface over the same action
-layer as the CLI and MCP server.
+layer as the CLI and MCP server. Before a record is selected, the middle rail
+shows recent activity across all configured records: current live drift plus the
+latest cfgit history entries. Selecting one of those entries opens that record's
+normal history and diff view.
 
 ## JSON mode
 

{cfgit-0.1.0 → cfgit-0.1.1}/docs/project-notes/handoff.md

@@ -7,7 +7,7 @@
 > - **cfgit is NOT "config version control" and NOT "general database git."** It is **non-custodial version control for live datastores**: git for a database you already have and cannot migrate, versioning records *in place*, without owning the data/reads/writes. Tagline: "git that doesn't make you move in." This is the defensible niche; "general DB git" invites comparison to **Dolt** (which owns the store) and loses.
 > - **The differentiator is DRIFT RECONCILIATION** (`status` detects out-of-band writes, `adopt` folds them into history, `commit` refuses to clobber un-adopted drift), because the team writes the DB from many paths and will NOT lock down creds (flat, equally-accountable startup). Every existing tool avoids this because nothing bypasses them; cfgit needs it.
 > - **v1 is a NARROW feature set on a GENERAL engine, with TWO adapters (Mongo + Postgres)** to prove "any DB." Build: `init`/`status`/`diff`/`commit`/`log`/`adopt`/`restore` (single + system)/`tag`/`fsck`, plus optional engine-level mutation permissions for admin-only high-blast-radius actions. CLI + JSON are the base surface; UI/MCP/skill are thin wrappers over the same actions.
-> - **CURRENT IMPLEMENTATION UPDATE:** CLI + JSON now has a localhost UI, MCP server, portable skill, and an optional `cfg-impact` plugin. Out-of-band hosted approval remains deferred. The impact provider boundary lives only in `plugins/cfg_impact`, never in `src/cfg/core`.
+> - **CURRENT IMPLEMENTATION UPDATE:** CLI + JSON now has a localhost UI, MCP server, portable skill, and an optional `cfgit-impact` plugin. Out-of-band hosted approval remains deferred. The impact provider boundary lives only in `plugins/cfg_impact`, never in `src/cfg/core`.
 > - **`docs/SPEC_CORE.md` is now the authority on framing + v1 scope.** `docs/SPEC.md` (v0.3.2) is the deep engine reference for the parts v1 builds; where they differ on scope, SPEC_CORE wins. Sections of THIS handoff written before the reframe (esp. §1's "config" emphasis and §2's approval-centric decisions) are superseded by SPEC_CORE where they conflict; the backend facts, constraints, env gotchas, and scaffold notes below remain accurate.
 > - Commercial value is a **later discovery, not a reason to build**; assume internal-grade. The real gate is a **one-week usage test**: if the team reaches for `cfg` over raw writes, continue; if they route around it, stop and reassess.
 
@@ -100,7 +100,7 @@ docs/SPEC_v0.1.md       the original v0.1 (historical, shows what the teardown f
 README.md               project intro
 LICENSE                 Apache-2.0
 NOTICE, CREDITS.md      attribution (git=idea-only; semantic-diff prior art cited)
-pyproject.toml          cfg-vcs package; extras: mongo/cli/mcp/impact/dev; `cfg` entrypoint
+pyproject.toml          cfgit package; extras: mongo/cli/mcp/impact/dev; `cfg` entrypoint
 .gitignore
 src/cfg/__init__.py
 src/cfg/core/           engine (no DB driver / no LLM SDK): hashing/asof/engine/refs TO BUILD

cfgit-0.1.1/examples/cfgit-support-demo.toml

@@ -0,0 +1,123 @@
+[project]
+name = "cfgit-support-demo"
+
+[history]
+history_collection = "cfgit_demo_history"
+heads_collection = "cfgit_demo_heads"
+
+[branches]
+enabled = true
+refs_collection = "cfgit_demo_refs"
+default_branch = "main"
+
+[[collection]]
+name = "agent_configs"
+id_field = "config_id"
+live_when = { is_active = true }
+ignore_fields = ["_id", "is_active", "updated_at", "updated_by"]
+secret_fields = []
+
+[[collection]]
+name = "modelgarden_models"
+id_field = "model_path"
+live_when = {}
+ignore_fields = ["_id", "updated_at", "updated_by"]
+secret_fields = ["provider_config.api_key"]
+
+[[collection]]
+name = "policy_rules"
+id_field = "rule_id"
+live_when = { active = true }
+ignore_fields = ["_id", "active", "updated_at", "updated_by"]
+secret_fields = []
+
+[[collection]]
+name = "tool_registry"
+id_field = "tool_id"
+live_when = { enabled = true }
+ignore_fields = ["_id", "enabled", "updated_at", "updated_by"]
+secret_fields = ["credentials.api_key_ref", "oauth.client_secret_ref"]
+
+[[collection]]
+name = "routing_policies"
+id_field = "policy_id"
+live_when = { active = true }
+ignore_fields = ["_id", "active", "updated_at", "updated_by"]
+secret_fields = []
+
+[[collection]]
+name = "escalation_policies"
+id_field = "escalation_id"
+live_when = { active = true }
+ignore_fields = ["_id", "active", "updated_at", "updated_by"]
+secret_fields = []
+
+[[collection]]
+name = "eval_suites"
+id_field = "suite_id"
+live_when = { enabled = true }
+ignore_fields = ["_id", "enabled", "updated_at", "updated_by"]
+secret_fields = []
+
+[[collection]]
+name = "rollout_controls"
+id_field = "rollout_id"
+live_when = { enabled = true }
+ignore_fields = ["_id", "enabled", "updated_at", "updated_by"]
+secret_fields = []
+
+[[collection]]
+name = "knowledge_sources"
+id_field = "source_id"
+live_when = { enabled = true }
+ignore_fields = ["_id", "enabled", "updated_at", "updated_by"]
+secret_fields = []
+
+[secrets]
+block_fields = ["*_key", "*_secret", "*_token", "*api_key*", "*password*"]
+block_values = ["sk-[A-Za-z0-9]{20,}", "AKIA[0-9A-Z]{16}"]
+on_match = "refuse"
+
+[author]
+from = "git"
+
+[connections]
+enabled = true
+share_with_ai = []
+ai_provider = "openai"
+warn_level = "none"
+links = [
+  { field = "agent", means = "agent identifier" },
+  { field = "agents", means = "agent identifiers" },
+  { field = "applies_to", means = "policy-to-agent linkage" },
+  { field = "approval_policy", means = "human approval requirement" },
+  { field = "audience", means = "customer or segment targeting" },
+  { field = "escalation_policy", means = "human handoff policy" },
+  { field = "eval_suite", means = "quality gate for a config" },
+  { field = "fallback_models", means = "fallback model routing" },
+  { field = "guarded_by", means = "policy or guardrail dependency" },
+  { field = "handoffs", means = "agent handoff graph" },
+  { field = "knowledge_sources", means = "retrieval source allowlist" },
+  { field = "model", means = "model routing" },
+  { field = "model_path", means = "model identifier" },
+  { field = "policy_refs", means = "referenced policy rules" },
+  { field = "routing_policy", means = "orchestration routing policy" },
+  { field = "rollout_id", means = "rollout gate" },
+  { field = "tool_id", means = "tool identifier" },
+  { field = "tools", means = "shared tool list" },
+]
+
+[env.dev]
+database = "mongo"
+uri = "mongodb://localhost:27017/?replicaSet=rs0"
+db = "cfgit_ui_demo"
+needs_approval = false
+
+[env.dev.identity]
+mode = "open"
+
+[env.dev.permissions]
+mode = "open"
+admins = []
+writers = []
+admin_actions = ["restore_system"]