القائمة
Add a new rule to an edgesentry-rs safety profile. Use when implementing a new regulation-backed detection rule (PROXIMITY_ALERT, ZONE_ENTRY, etc.).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Deploy edgesentry-rs to a new server — TLS, PostgreSQL, S3/MinIO, systemd. Use when setting up a new deployment environment.
Build, test, and lint edgesentry-rs before committing. Use before every commit or when verifying the workspace is clean.
Scaffold a new crate in the edgesentry-rs Cargo workspace. Use when adding a new pipeline stage or utility crate.
Operate edgesentry-rs in production — check health, query metrics, run backups, restore from backup. Use when monitoring or maintaining a deployed instance.
Publish a new edgesentry-rs release to crates.io. Use when cutting a release after all tests pass.
Verify an edgesentry audit chain using the eds CLI. Use to confirm a chain is intact and a payload matches its AuditRecord.
| name | eds-add-profile-rule |
| description | Add a new rule to an edgesentry-rs safety profile. Use when implementing a new regulation-backed detection rule (PROXIMITY_ALERT, ZONE_ENTRY, etc.). |
| license | Apache-2.0 |
| compatibility | Requires Rust stable toolchain |
| metadata | {"repo":"edgesentry-rs"} |
1. Add the rule to rules.json
Open crates/edgesentry-profile/fixtures/<profile-name>/rules.json and add:
{
"id": "RULE_NAME",
"condition": "distance < threshold",
"params": { "threshold": 5.0 },
"regulation": "Exact regulation citation §X",
"severity": "HIGH"
}
2. Add a KB file
Create crates/edgesentry-profile/fixtures/<profile-name>/kb/RULE_NAME.md with the plain-language description used by edgesentry-explain.
3. Verify the profile loads
cargo test -p edgesentry-profile
4. Add an integration test
In crates/eds/tests/cli_integration.rs, add a test that:
eds ingest replay + eds evaluate run against a fixtureRiskEvent fires at the expected frameevidence_quality is CERTIFIEDid must be SCREAMING_SNAKE_CASE and unique within the profileregulation appears verbatim in AuditRecords — use the exact clause textid exactly (case-sensitive)