# Attempt Boundary v0.1.0

Attempt Boundary is a dependency-free local Node.js wrapper that records whether a configured execution command crossed the wrapper's attempt boundary or was stopped by a preflight first.

## Included

- strict duplicate-key-rejecting plan and receipt JSON;
- portable relative-path containment beneath an explicit workspace root;
- bounded recursive SHA-256 snapshots for explicitly protected files and directories;
- direct command execution with `shell: false`, time limits, and a combined output-byte limit;
- fail-closed execution when preflight fails, times out, exceeds the output limit, cannot spawn, or changes a protected path;
- conservative `attempt_consumed: true` once the wrapper invokes the execution command;
- output byte counts and SHA-256 digests without storing command output content;
- create-only receipt publication using a same-directory temporary file and atomic hard link;
- canonical receipt-content SHA-256 verification;
- Draft 2020-12 plan and receipt schemas plus a neutral example;
- 30 passing synthetic tests covering successful, denied, failed, bounded, tampered, and path-safety cases.

## Install

```bash
npm install https://kaldenframelabs.com/downloads/kaldenframe-labs-attempt-boundary-0.1.0.tgz
```

Node.js 20 or newer is required. The package has no runtime dependencies and is licensed under MIT.

## Verified source

- Source commit: `40260a1f43530d535c48eab735dee0081af2ff50`
- Package SHA-256: `756C2C244BDC91425C723235583AAA3E5178CC01ADEC41F4DEB3872F48FFB8E0`
- Source archive SHA-256: `7BAEDD2EE3D77D69DA7714B7E106B5D2CB9D1A9B17861829C92835EA28AA3F13`

## Boundary

The receipt proves only what this wrapper observed and controlled. It does not prove that unrelated processes avoided protected paths, that a command did not read a file, that command output was truthful, that the host was uncompromised, or that an executed job was correct, safe, reproducible, or fit for use.

The receipt hash detects alteration of one receipt. It is not a signature, trusted timestamp, remote attestation, sandbox, or tamper-proof ledger. Plans are executable configuration and must be reviewed before running; secrets must not be placed in command arguments.