Skip to content

docs: add AI workflow safety overview #211

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ProfRandom92 merged 1 commit into from
May 22, 2026
+15 −0
Merged

docs: add AI workflow safety overview #211

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,6 +139,21 @@ flowchart LR

---

## AI workflow safety evidence

CompText V7 includes a local-only, deterministic evidence chain for AI-assisted repository work. The chain is intended to make review evidence inspectable and artifact-backed without adding external services or runtime orchestration.

- `scripts/safe_pr_gate.py` checks the current branch, working-tree state, changed-file scope, and minimal privacy boundaries.
- `scripts/agent_artifact_bundle.py` records branch, changed files, safe-gate output, validation evidence, and optional MCP context output references.
- `scripts/validate_agent_artifact_bundle.py` validates committed or generated bundle shape and deterministic status fields.
- `scripts/pr_body_from_agent_bundle.py` renders PR body Markdown from bundle data without inventing claims.
- `scripts/ai_workflow_snapshot.py` emits a compact JSON snapshot that combines safe-gate and bundle evidence.
- MCP context output references point to repo-relative artifacts, such as `artifacts/mcp_context_layer_example.json`, rather than embedding full replay payloads in every bundle.

This chain is local-only and uses deterministic JSON/Markdown outputs. It does not call external APIs, contact GitHub APIs, add timestamps or random IDs, execute runtime tools, or perform semantic scoring. It is not an autonomous agent framework, workflow orchestrator, vector memory system, or runtime tool executor.

---

## Minimal deterministic example

```json
Expand Down
Loading