shield_lock
JinDaGe
← Back to skills
extension
Category: Development & EngineeringNo API key required

Local ProofPack｜本地交付证据闸门

Local-first delivery evidence gate for competitions, campaigns, releases, and client handoffs. Produces READY/WARN/BLOCKED reports, hashes, and explicit allowlist bundles without uploading project content.

personAuthor: ppdbxdawjhubModelScope
downloadDownload package

Local ProofPack

Use this skill when a user must decide whether a local project, campaign, release, submission, or customer delivery is actually ready. Typical requests include “按规则检查是否可提交”, “找出最终版”, “核对素材/许可证/链接”, “生成可审计交付包”, and “audit this folder before release”.

Operating contract

  1. Ask for, or locate, a requirements file and a project directory. Supported requirements are structured YAML/JSON and conservative Markdown/TXT extraction.
  2. Run audit first. Explain every BLOCKED and WARN item using its rule ID, relative evidence path, actual value, and repair suggestion.
  3. Never call a cloud model, upload files, log in, or submit a form. All project content stays on localhost. --model-dir must point to a model already present on disk.
  4. Treat deterministic checks as authoritative. Local semantic matching only proposes evidence candidates; it cannot override a deterministic failure. For an unscoped rule, only the top-1 semantic candidate becomes evidence; remaining candidates are suggestions and are never checked or bundled. semantic=required must fail on model/inference errors; only auto may downgrade with an explicit report.
  5. After the user fixes items, run audit again. Only run bundle after the user explicitly names or approves an allowlist.
  6. A READY result means the supplied requirements matched the supplied local evidence. It is not a legal, platform, or copyright opinion.

Local commands

From this skill directory:

./scripts/run.sh audit --requirements examples/demo/requirements.yaml --project examples/demo/blocked_project --output .proofpack/blocked
./scripts/run.sh audit --requirements examples/demo/requirements.yaml --project examples/demo/ready_project --output .proofpack/ready --semantic auto
./scripts/run.sh bundle --project examples/demo/ready_project --output .proofpack/ready-bundle --allowlist deliverables/launch_final.mp4 docs/article.md legal/asset-ledger.csv docs/submission-links.txt

On Windows use scripts/run.ps1 with the same subcommands. Exit codes are 0 READY, 1 WARN, 2 BLOCKED, and 3 for invalid configuration/runtime errors. The wrappers select Python 3.12/3.11/3.10 before python3 and reject Python 3.9 or older. Set PROOFPACK_PYTHON to an explicit Python 3.10–3.12 executable when needed. Package details, architecture, and the demo recipe are in docs/README.md, docs/architecture.md, and docs/demo.md.

Agent response format

Return a short status first, then a table of rule ID, status, evidence, actual value, and next action. Mention the semantic mode and device. Link or quote only local relative paths. Do not include secret-like text from a scanned file.