Reliability Evidence Pack (REP)

# Reliability Evidence Pack (REP)

A comprehensive runtime system for documenting and verifying agent operational reliability through structured artifact recording, validation, and compliance reporting.

What's Included

Core Scripts (`/scripts`)

CLI Package (`/cli`)

GitHub Action (`/github-action`)

Schemas (`/schemas`)

- `decision_rejection_log.json`

- `handoff_acceptance_packet.json`

- `memory_reconstruction_audit.json`

- `near_miss_reliability_trailer.json`

- `signed_divergence_violation_record.json`

Examples (`/examples`)

Required Binaries

No other system binaries required.

Installation

Option 1: Direct Scripts

# Clone or copy this bundle to your project
cp -r rep-bundle-v2 /path/to/your/project/rep
cd rep

# Make scripts executable
chmod +x scripts/*.mjs

# Test
node scripts/rep.mjs --help

Option 2: CLI Package

cd cli
npm install -g
rep --help

Option 3: GitHub Action

- uses: ./github-action
  with:
    bundle-path: ./rep

Configuration

Set environment variables to configure behavior:

# Path to artifacts directory (default: ./artifacts)
REP_ARTIFACTS_PATH=./artifacts

# Path to schemas directory (default: ./schemas)  
REP_SCHEMAS_PATH=./schemas

# Log file path (optional)
REP_LOG_FILE=/var/log/rep.log

Usage

Initialize a new REP

node scripts/rep.mjs init --name "my-agent"

Validate artifacts

node scripts/rep-validate.mjs ./artifacts --strict

Run heartbeat recording (cron)

REP_ARTIFACTS_PATH=./artifacts node scripts/rep-heartbeat-cron.mjs

Set up cron (example for crontab)

# Add to crontab - run heartbeat every 5 minutes
*/5 * * * * cd /path/to/rep && REP_ARTIFACTS_PATH=./artifacts node scripts/rep-heartbeat-cron.mjs >> /var/log/rep-heartbeat.log 2>&1

Artifact Types

| Artifact | Purpose |

|----------|---------|

| `agent_heartbeat_record` | Agent lifecycle events |

| `decision_rejection_log` | Decisions and their outcomes |

| `context_snapshot` | Memory/context state |

| `handoff_acceptance_packet` | Inter-agent handoff validation |

| `near_miss_reliability_trailer` | Near-miss events |

| `memory_reconstruction_audit` | Memory integrity checks |

| `signed_divergence_violation_record` | Policy violations |

Security Considerations

License

MIT

Support

Security Considerations

Sensitive Data

REP captures context snapshots, decision logs, and memory-like artifacts that may contain sensitive information.

Signing Keys

The SPEC includes signature fields for artifact integrity, but key management is operator-defined:

CI Usage

The GitHub Action is local to your repository:

Network Behavior

All scripts operate locally:

Best Practices

1. Keep artifacts directory separate from source code

2. Add artifact paths to `.gitignore`

3. Rotate logs regularly

4. Audit artifacts before external sharing